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 --versionjournal-entryExecute the skills CLI command in your project's root directory to begin installation:
Fetches journal-entry 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 journal-entry. Access via /journal-entry 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.
Important: This command assists with journal entry workflows but does not provide financial advice. All entries should be reviewed by qualified financial professionals before posting.
Prepare journal entries with proper debits, credits, supporting detail, and review documentation.
/je <type> <period>
type — The journal entry type. One of:
ap-accrual — Accounts payable accruals for goods/services received but not yet invoicedfixed-assets — Depreciation and amortization entries for fixed assets and intangiblesprepaid — Amortization of prepaid expenses (insurance, software, rent, etc.)payroll — Payroll accruals including salaries, benefits, taxes, and bonus accrualsrevenue — Revenue recognition entries including deferred revenue adjustmentsperiod — The accounting period (e.g., 2024-12, 2024-Q4, 2024)If ~~erp or ~~data warehouse is connected:
If no data source is connected:
Connect ~~erp or ~~data warehouse to pull GL data automatically. You can also paste trial balance data or upload a spreadsheet.
Prompt the user to provide:
Based on the JE type:
AP Accrual:
Fixed Assets:
Prepaid:
Payroll:
Revenue:
Present the entry in standard format:
Journal Entry: [Type] — [Period]
Prepared by: [User]
Date: [Period end date]
| Line | Account Code | Account Name | Debit | Credit | Department | Memo |
|------|-------------|--------------|-------|--------|------------|------|
| 1 | XXXX | [Name] | X,XXX | | [Dept] | [Detail] |
| 2 | XXXX | [Name] | | X,XXX | [Dept] | [Detail] |
| | | **Total** | X,XXX | X,XXX | | |
Supporting Detail:
- [Calculation basis and assumptions]
- [Reference to supporting schedule or documentation]
Reversal: [Yes/No — if yes, specify reversal date]
Before finalizing, verify:
Provide:
Make 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
Useful defaults in journal-entry — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
Registry listing for journal-entry matched our evaluation — installs cleanly and behaves as described in the markdown.
journal-entry fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
I recommend journal-entry for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
journal-entry fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
Useful defaults in journal-entry — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
journal-entry fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
Registry listing for journal-entry matched our evaluation — installs cleanly and behaves as described in the markdown.
We added journal-entry from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
journal-entry reduced setup friction for our internal harness; good balance of opinion and flexibility.
showing 1-10 of 40