Important: This skill assists with journal entry workflows but does not provide financial advice. All entries should be reviewed by qualified financial professionals before posting.
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionjournal-entry-prepExecute the skills CLI command in your project's root directory to begin installation:
Fetches journal-entry-prep 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-prep. Access via /journal-entry-prep 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
Important: This skill assists with journal entry workflows but does not provide financial advice. All entries should be reviewed by qualified financial professionals before posting.
Best practices, standard entry types, documentation requirements, and review workflows for journal entry preparation.
Accrue for goods or services received but not yet invoiced at period end.
Typical entry:
Sources for calculation:
Key considerations:
Book periodic depreciation expense for tangible and intangible assets.
Typical entry:
Depreciation methods:
Key considerations:
Amortize prepaid expenses over their benefit period.
Typical entry:
Common prepaid categories:
Key considerations:
Accrue compensation and related costs for the period.
Typical entries:
Salary accrual (for pay periods not aligned with month-end):
Bonus accrual:
Benefits accrual:
Payroll tax accrual:
Key considerations:
Recognize revenue based on performance obligations and delivery.
Typical entries:
Recognize previously deferred revenue:
Recognize revenue with new receivable:
Defer revenue received in advance:
Key considerations:
Every journal entry should have:
| Entry Type | Amount Threshold | Approver |
|---|---|---|
| Standard recurring | Any amount | Accounting manager |
| Non-recurring / manual | < $50K | Accounting manager |
| Non-recurring / manual | $50K - $250K | Controller |
| Non-recurring / manual | > $250K | CFO / VP Finance |
| Top-side / consolidation | Any amount | Controller or above |
| Out-of-period adjustments | Any amount | Controller or above |
Note: Thresholds should be set based on your organization's materiality and risk tolerance.
Before approving a journal entry, the reviewer should verify:
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
We added journal-entry-prep from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
journal-entry-prep has been reliable in day-to-day use. Documentation quality is above average for community skills.
journal-entry-prep fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
journal-entry-prep fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
journal-entry-prep has been reliable in day-to-day use. Documentation quality is above average for community skills.
Solid pick for teams standardizing on skills: journal-entry-prep is focused, and the summary matches what you get after install.
We added journal-entry-prep from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
Solid pick for teams standardizing on skills: journal-entry-prep is focused, and the summary matches what you get after install.
journal-entry-prep has been reliable in day-to-day use. Documentation quality is above average for community skills.
Keeps context tight: journal-entry-prep is the kind of skill you can hand to a new teammate without a long onboarding doc.
showing 1-10 of 72