journal-entry▌
anthropics/knowledge-work-plugins · updated Apr 8, 2026
MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.
If you see unfamiliar placeholders or need to check which tools are connected, see CONNECTORS.md.
Journal Entry Preparation
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.
Usage
/je <type> <period>
Arguments
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 adjustments
period— The accounting period (e.g.,2024-12,2024-Q4,2024)
Workflow
1. Gather Source Data
If ~~erp or ~~data warehouse is connected:
- Pull the trial balance for the specified period
- Pull subledger detail for the relevant accounts
- Pull prior period entries of the same type for reference
- Identify the current GL balances for affected accounts
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:
- Trial balance or GL balances for affected accounts
- Subledger detail or supporting schedules
- Prior period entries for reference (optional)
2. Calculate the Entry
Based on the JE type:
AP Accrual:
- Identify goods/services received but not invoiced by period end
- Calculate accrual amounts from PO receipts, contracts, or estimates
- Debit: Expense accounts (or asset accounts for capitalizable items)
- Credit: Accrued liabilities
Fixed Assets:
- Pull the fixed asset register or depreciation schedule
- Calculate period depreciation by asset class and method (straight-line, declining balance, units of production)
- Debit: Depreciation expense (by department/cost center)
- Credit: Accumulated depreciation
Prepaid:
- Pull the prepaid amortization schedule
- Calculate the period amortization for each prepaid item
- Debit: Expense accounts (by type — insurance, software, rent, etc.)
- Credit: Prepaid expense accounts
Payroll:
- Calculate accrued salaries for days worked but not yet paid
- Calculate accrued benefits (health, retirement contributions, PTO)
- Calculate employer payroll tax accruals
- Calculate bonus accruals (if applicable, based on plan terms)
- Debit: Salary expense, benefits expense, payroll tax expense
- Credit: Accrued payroll, accrued benefits, accrued payroll taxes
Revenue:
- Review contracts and performance obligations
- Calculate revenue to recognize based on delivery/performance
- Adjust deferred revenue balances
- Debit: Deferred revenue (or accounts receivable)
- Credit: Revenue accounts (by stream/category)
3. Generate the Journal Entry
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]
4. Review Checklist
Before finalizing, verify:
- Debits equal credits
- Correct accounting period
- Account codes are valid and map to the right GL accounts
- Amounts are calculated correctly with supporting detail
- Memo/description is clear and specific enough for audit
- Department/cost center coding is correct
- Entry is consistent with prior period treatment
- Reversal flag is set appropriately (accruals should auto-reverse)
- Supporting documentation is referenced or attached
- Entry is within the user's approval authority
- No unusual or out-of-pattern amounts that need investigation
5. Output
Provide:
- The formatted journal entry
- Supporting calculations
- Comparison to prior period entry of the same type (if available)
- Any items flagged for review or follow-up
- Instructions for posting (manual entry or upload format for the user's ERP)
How to use journal-entry on Cursor
AI-first code editor with Composer
Prerequisites
Before installing skills in Cursor, ensure your development environment meets these requirements:
- ›Cursor installed and configured on your development machine
- ›Node.js version 16.0+ with npm package manager (verify with
node --version) - ›Active project directory or workspace where you want to add journal-entry
Execute installation command
Execute the skills CLI command in your project's root directory to begin installation:
The skills CLI fetches journal-entry from GitHub repository anthropics/knowledge-work-plugins and configures it for Cursor.
Select Cursor when prompted
The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:
Verify installation
Confirm successful installation by checking the skill directory location:
Reload or restart Cursor to activate journal-entry. Access the skill through slash commands (e.g., /journal-entry) or your agent's skill management interface.
Security & Verification Notice
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 development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.
List & Monetize Your Skill
Submit your Claude Code skill and start earning
Use Cases▌
User Story & Requirements Generation
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
Competitive Analysis
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
Roadmap Prioritization
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
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
Installation Steps
- 1.Install product management skill
- 2.Start with user story generation for known feature
- 3.Progress to competitive analysis: research 2-3 competitors
- 4.Use for roadmap prioritization: apply RICE/ICE scoring
- 5.Draft stakeholder communications and refine based on feedback
- 6.Build template library for recurring PM tasks
- 7.Share 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
Discussion
Product Hunt–style comments (not star reviews)- No comments yet — start the thread.
Ratings
4.8★★★★★40 reviews- ★★★★★Hana Choi· Dec 28, 2024
Useful defaults in journal-entry — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- ★★★★★Olivia Thompson· Dec 16, 2024
Registry listing for journal-entry matched our evaluation — installs cleanly and behaves as described in the markdown.
- ★★★★★Ganesh Mohane· Dec 12, 2024
journal-entry fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
- ★★★★★Omar Huang· Dec 12, 2024
I recommend journal-entry for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
- ★★★★★Nia Rahman· Dec 4, 2024
journal-entry fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
- ★★★★★Noah Patel· Nov 11, 2024
Useful defaults in journal-entry — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- ★★★★★Henry Malhotra· Nov 7, 2024
journal-entry fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
- ★★★★★Sakshi Patil· Nov 3, 2024
Registry listing for journal-entry matched our evaluation — installs cleanly and behaves as described in the markdown.
- ★★★★★Mia Srinivasan· Oct 26, 2024
We added journal-entry from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- ★★★★★Chaitanya Patil· Oct 22, 2024
journal-entry reduced setup friction for our internal harness; good balance of opinion and flexibility.
showing 1-10 of 40