If you see unfamiliar placeholders or need to check which tools are connected, see CONNECTORS.md.
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versiondigestExecute the skills CLI command in your project's root directory to begin installation:
Fetches digest from anthropics/knowledge-work-plugins 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 digest. Access via /digest 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
11.0K
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
11.0K
stars
If you see unfamiliar placeholders or need to check which tools are connected, see CONNECTORS.md.
Scan recent activity across all connected sources and generate a structured digest highlighting what matters.
Determine the time window from the user's input:
--daily — Last 24 hours (default if no flag specified)--weekly — Last 7 daysThe user may also specify a custom range:
--since yesterday--since Monday--since 2025-01-20Identify which MCP sources are connected (same approach as the search command):
If no sources are connected, guide the user:
To generate a digest, you'll need at least one source connected.
Check your MCP settings to add ~~chat, ~~email, ~~cloud storage, or other tools.
~~chat:
to:me)~~email:
~~cloud storage:
~~project tracker:
~~CRM:
~~knowledge base:
From all gathered activity, extract and categorize:
Action Items:
Decisions:
Mentions:
Updates:
Organize the digest by topic, project, or theme rather than by source. Merge related activity across sources:
## Project Aurora
- ~~chat: Design review thread concluded — team chose Option B (#design, Tuesday)
- ~~email: Sarah sent updated spec incorporating feedback (Wednesday)
- ~~cloud storage: "Aurora API Spec v3" updated by Sarah (Wednesday)
- ~~project tracker: 3 tasks moved to In Progress, 2 completed
## Budget Planning
- ~~email: Finance team requesting Q2 projections by Friday
- ~~chat: Todd shared template in #finance (Monday)
- ~~cloud storage: "Q2 Budget Template" shared with you (Monday)
Structure the output clearly:
# [Daily/Weekly] Digest — [Date or Date Range]
Sources scanned: ~~chat, ~~email, ~~cloud storage, [others]
## Action Items (X items)
- [ ] [Action item 1] — from [person], [source] ([date])
- [ ] [Action item 2] — from [person], [source] ([date])
## Decisions Made
- [Decision 1] — [context] ([source], [date])
- [Decision 2] — [context] ([source], [date])
## [Topic/Project Group 1]
[Activity summary with source attribution]
## [Topic/Project Group 2]
[Activity summary with source attribution]
## Mentions
- [Mention context] — [source] ([date])
## Documents Updated
- [Doc name] — [who modified, what changed] ([date])
If any source fails or is unreachable:
Note: Could not reach [source name] for this digest.
The following sources were included: [list of successful sources].
Do not let one failed source prevent the digest from being generated. Produce the best digest possible from available sources.
End with a quick summary:
---
[X] action items · [Y] decisions · [Z] mentions · [W] doc updates
Across [N] sources · Covering [time range]
--daily if no flag is specifiedMake data-driven prioritization decisions faster
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
Prerequisites
Time Estimate
30-60 minutes to see productivity improvements
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ 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.
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
ailabs-393/ai-labs-claude-skills
pproenca/dot-skills
mattpocock/skills
digest is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
Registry listing for digest matched our evaluation — installs cleanly and behaves as described in the markdown.
I recommend digest for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
Useful defaults in digest — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
We added digest from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
Keeps context tight: digest is the kind of skill you can hand to a new teammate without a long onboarding doc.
digest fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
Solid pick for teams standardizing on skills: digest is focused, and the summary matches what you get after install.
Useful defaults in digest — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
digest reduced setup friction for our internal harness; good balance of opinion and flexibility.
showing 1-10 of 60