You are an elite Celery engineer with deep expertise in:
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versioncelery-expertExecute the skills CLI command in your project's root directory to begin installation:
Fetches celery-expert from martinholovsky/claude-skills-generator and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate celery-expert. Access via /celery-expert in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
0
total installs
0
this week
33
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
33
stars
You are an elite Celery engineer with deep expertise in:
Risk Level: MEDIUM
# tests/test_tasks.py
import pytest
from celery.contrib.testing.tasks import ping
from celery.result import EagerResult
@pytest.fixture
def celery_config():
return {
'broker_url': 'memory://',
'result_backend': 'cache+memory://',
'task_always_eager': True,
'task_eager_propagates': True,
}
class TestProcessOrder:
def test_process_order_success(self, celery_app, celery_worker):
"""Test order processing returns correct result"""
from myapp.tasks import process_order
# Execute task
result = process_order.delay(order_id=123)
# Assert expected behavior
assert result.get(timeout=10) == {
'order_id': 123,
'status': 'success'
}
def test_process_order_idempotent(self, celery_app, celery_worker):
"""Test task is idempotent - safe to retry"""
from myapp.tasks import process_order
# Run twice
result1 = process_order.delay(order_id=123).get(timeout=10)
result2 = process_order.delay(order_id=123).get(timeout=10)
# Should be safe to retry
assert result1['status'] in ['success', 'already_processed']
assert result2['status'] in ['success', 'already_processed']
def test_process_order_retry_on_failure(self, celery_app, celery_worker, mocker):
"""Test task retries on temporary failure"""
from myapp.tasks import process_order
# Mock to fail first, succeed second
mock_process = mocker.patch('myapp.tasks.perform_order_processing')
mock_process.side_effect = [TemporaryError("Timeout"), {'result': 'ok'}]
result = process_order.delay(order_id=123)
assert result.get(timeout=10)['status'] == 'success'
assert mock_process.call_count == 2
# myapp/tasks.py
from celery import Celery
app = Celery('tasks', broker='redis://localhost:6379/0')
@app.task(bind=True, max_retries=3)
def process_order(self, order_id: int):
try:
order = get_order(order_id)
if order.status == 'processed':
return {'order_id': order_id, 'status': 'already_processed'}
result = perform_order_processing(order)
return {'order_id': order_id, 'status': 'success'}
except TemporaryError as exc:
raise self.retry(exc=exc, countdown=2 ** self.request.retries)
Add proper error handling, time limits, and observability.
# Run all Celery tests
pytest tests/test_tasks.py -v
# Run with coverage
pytest tests/test_tasks.py --cov=myapp.tasks --cov-report=term-missing
# Test workflow patterns
pytest tests/test_workflows.py -v
# Integration test with real broker
pytest tests/integration/ --broker=redis://localhost:6379/0
# Bad - Individual tasks for each item
for item_id in item_ids: # 10,000 items = 10,000 tasks
process_item.delay(item_id)
# Good - Process in batches
@app.task
def process_batch(item_ids: list):
"""Process items in chunks for efficiency"""
results = []
for chunk in chunks(item_ids, size=100):
items = fetch_items_bulk(chunk) # Single DB query
results.extend([process(item) for item in items])
return results
# Dispatch in chunks
for chunk in chunks(item_ids, size=100):
process_batch.delay(chunk) # 100 tasks instead of 10,000
# Bad - Default prefetch for I/O-bound tasks
app.conf.worker_prefetch_multiplier = 4 # Too many reserved
# Good - Tune based on task type
# CPU-bound: Higher prefetch, fewer workers
app.conf.worker_prefetch_multiplier = 4
# celery -A app worker --concurrency=4
# I/O-bound: Lower prefetch, more workers
app.conf.worker_prefetch_multiplier = 1
# celery -A app worker --pool=gevent --concurrency=100
# Long tasks: Disable prefetch
app.conf.worker_prefetch_multiplier = 1
app.conf.task_acks_late = True
# Bad - Storing results for fire-and-forget tasks
@app.task
def send_email(to, subject, body)✓Make data-driven prioritization decisions faster
Stakeholder Communication
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
✓Save 3-5 hours/week on communication overhead
Implementation Guide
Prerequisites
- ›Claude Desktop or compatible AI client
- ›Access to product documentation and roadmap tools (Jira, Notion, etc.)
- ›Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
- ›Stakeholder contact information and communication channels
Time Estimate
30-60 minutes to see productivity improvements
Steps
- 1Install product management skill
- 2Start with user story generation for known feature
- 3Progress to competitive analysis: research 2-3 competitors
- 4Use for roadmap prioritization: apply RICE/ICE scoring
- 5Draft stakeholder communications and refine based on feedback
- 6Build template library for recurring PM tasks
- 7Share effective prompts with product team
Common Pitfalls
- ⚠Not validating competitive research—verify facts before sharing
- ⚠Accepting user stories without involving engineering team
- ⚠Over-relying on frameworks without qualitative judgment
- ⚠Not customizing outputs to company culture and communication style
- ⚠Skipping stakeholder validation of generated requirements
Best Practices
✓ Do
- +Validate research and competitive analysis with real data
- +Collaborate with engineering when generating technical requirements
- +Customize frameworks and templates to your company context
- +Use skill for first drafts, refine with stakeholder input
- +Document successful prompt patterns for PM tasks
- +Combine AI efficiency with human judgment and intuition
✗ Don't
- −Don't publish competitive analysis without fact-checking
- −Don't finalize user stories without engineering review
- −Don't make prioritization decisions solely on AI scoring
- −Don't skip customer validation of generated requirements
- −Don't ignore company-specific context and culture
💡 Pro Tips
- ★Provide context: company goals, constraints, customer feedback
- ★Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
- ★Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
- ★Use skill for 70% generation + 30% customization to company needs
When to Use This
✓ Use when
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid when
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
Learning Path
- 1Basic: user stories, feature specs, status updates
- 2Intermediate: competitive analysis, prioritization frameworks, PRDs
- 3Advanced: product strategy, go-to-market planning, OKR setting
- 4Expert: product vision, market positioning, business model innovation
Related Skills
pwa-expert
58erichowens/some_claude_skills
Productivitytag: expertantigravity-design-expert
199sickn33/antigravity-awesome-skills
Frontendtag: expertinterior-design-expert
143erichowens/some_claude_skills
Frontendtag: expertgrill-me
689mattpocock/skills
Productivitysame categorypremortem
217parcadei/continuous-claude-v3
Productivitysame categorydeslop
162cursor/plugins
Productivitysame categoryReviews
4.7★★★★★44 reviews- DDaniel Liu★★★★★Dec 24, 2024
Solid pick for teams standardizing on skills: celery-expert is focused, and the summary matches what you get after install.
- KKwame Abbas★★★★★Dec 8, 2024
Registry listing for celery-expert matched our evaluation — installs cleanly and behaves as described in the markdown.
- KKwame Ramirez★★★★★Nov 27, 2024
Useful defaults in celery-expert — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- IIsabella Verma★★★★★Nov 27, 2024
Keeps context tight: celery-expert is the kind of skill you can hand to a new teammate without a long onboarding doc.
- KKwame Rahman★★★★★Nov 15, 2024
We added celery-expert from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- AAva Huang★★★★★Oct 18, 2024
I recommend celery-expert for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
- IIsabella Menon★★★★★Oct 18, 2024
celery-expert is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- AAma Martinez★★★★★Oct 6, 2024
celery-expert fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
- AAnika Park★★★★★Sep 25, 2024
celery-expert is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- NNia Mensah★★★★★Sep 9, 2024
Solid pick for teams standardizing on skills: celery-expert is focused, and the summary matches what you get after install.
showing 1-10 of 44
1 / 5Discussion
Comments — not star reviews- No comments yet — start the thread.