Token导航 LogoToken导航

Agent Skill · 开发

journal-entry-prep(日记帐分录准备)

journal-entry-prep 用于处理 GitHub 仓库、Issue、Pull Request 和代码协作信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要围绕仓库状态、代码变更或协作事项进行整理时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

journal-entry-prep 是开发类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为需要联网;许可证信息还不明确,第三方扫描已通过,按安装量在开发类的 21,746 个 Skill 里排第 1,873。

总安装 22,861周安装 982GitHub Stars 11,730下载 8,013核验 2026-05-01

安装说明

本站只整理中文说明,不托管安装包,也不代用户安装。
GitHub
许可证
unknown

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:journal-entry-prep(日记帐分录准备)
来源仓库:https://github.com/anthropics/knowledge-work-plugins
仓库路径:skills/journal-entry-prep
安装命令:
npx skills add https://github.com/anthropics/knowledge-work-plugins --skill journal-entry-prep
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

skills.shnpx skills
npx skills add https://github.com/anthropics/knowledge-work-plugins --skill journal-entry-prep

这个 Skill 是做什么的

开发类 Skill 面向写代码、改代码和排查问题,一般会读写仓库文件,部分还会执行构建或测试命令。

用于处理 GitHub 仓库、Issue、Pull Request 和代码协作信息。适合在 Codex、Claude、Cursor、Gemini CLI 中围绕仓库状态、代码变更或协作事项进行整理。通过 npx skills add 命令从指定仓库安装并使用。

安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。journal-entry-prep 属于开发类 Skill,可作为该场景下的辅助能力补充。

来源仓库内路径:skills/journal-entry-prep

上手步骤

4 步
  1. 1

    确认自己的宿主工具

    公开资料标注支持 Codex、Claude、Cursor、Gemini CLI;先确认自己用的是其中之一,再按对应工具的 Skills 目录放置。

  2. 2

    拿到安装命令

    可以直接复制的命令是 npx skills add https://github.com/anthropics/knowledge-work-plugins --skill jour…;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

    命令执行完要完全退出宿主工具再打开,让新装的 Skill 被重新扫描到,否则列表里可能看不到。

  4. 4

    按最小权限试用

    它需要需要联网,先在测试目录或测试账号里跑,确认没问题再放到正式项目。

常见问题

6 条

journal-entry-prep 怎么安装?

在终端执行 npx skills add https://github.com/anthropics/knowledge-work-plugins --skill journal-entry-…。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

journal-entry-prep 支持哪些 AI 工具?

公开资料标注支持 Codex、Claude、Cursor、Gemini CLI。其他工具只要能读取本地 Skill 目录,一般也能手动放进去,但要自己确认触发方式是否一致。

journal-entry-prep 需要什么权限?

权限级别是需要联网。该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

journal-entry-prep 是免费的吗?

公开资料没有标注明确许可证,收费和商用限制都无法确认。正式使用前请到来源仓库核对授权说明。

journal-entry-prep 用的人多吗?

公开数据是累计安装 22,861 次,近一周安装 982 次,下载 8,013 次,GitHub 11,730 星。这些数字来自第三方目录统计,只能当作热度参考,不代表质量或安全性。

journal-entry-prep 安全吗?

第三方扫描结果为通过,但这只覆盖已知的静态检查项,不能替代自己读一遍源码和安装命令。

值得选的地方和要先想清楚的地方

值得选的地方

  • 同时适配 4 种工具,换客户端不用重新找替代品。
  • 第三方扫描已通过,常见的高风险行为没有命中。
  • 来源仓库有 11,730 星,维护活跃度相对可查。

先想清楚的地方

  • 许可证没有明确标注,能不能商用、能不能再分发都不确定。
  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 Codex,想直接扩展它能力的人。
  • 需要处理开发类任务、又不想每次都手写提示词的人。

不太适合

  • 需要明确授权才能用到公司项目里的场景。
  • 需要厂商级技术支持和 SLA 的生产系统。

开发类 Skill 对比

6 个同类
Skill总安装GitHub 星权限许可证扫描
skill-vetter

技能审查员 · OpenClaw

8,779,018986操作浏览器MIT-0通过
ontology

本体论 · OpenClaw

6,636,960576只读MIT-0通过
entra-app-registration

内部应用程序注册 · Codex、Claude

6,631,872764接触敏感数据未明确通过
entra-app-registration

内部应用程序注册 · Codex、Claude

3,757,680201接触敏感数据未明确通过
nano-banana-pro

纳米香蕉专业版 · OpenClaw

3,526,898364接触敏感数据MIT-0有提醒
journal-entry-prep

日记帐分录准备 · 本页

22,86111,730需要联网未明确通过

按安装量取同分类前几名;数字来自第三方目录统计,只作热度参考,不代表质量结论。

SKILL.md 原文

Journal Entry Preparation

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.

Standard Accrual Types and Their Entries

Accounts Payable Accruals

Accrue for goods or services received but not yet invoiced at period end.

Typical entry:

  • Debit: Expense account (or capitalize if asset-qualifying)
  • Credit: Accrued liabilities

Sources for calculation:

  • Open purchase orders with confirmed receipts
  • Contracts with services rendered but unbilled
  • Recurring vendor arrangements (utilities, subscriptions, professional services)
  • Employee expense reports submitted but not yet processed

Key considerations:

  • Reverse in the following period (auto-reversal recommended)
  • Use consistent estimation methodology period over period
  • Document basis for estimates (PO amount, contract terms, historical run-rate)
  • Track actual vs accrual to refine future estimates

Fixed Asset Depreciation

Book periodic depreciation expense for tangible and intangible assets.

Typical entry:

  • Debit: Depreciation/amortization expense (by department or cost center)
  • Credit: Accumulated depreciation/amortization

Depreciation methods:

  • Straight-line: (Cost - Salvage) / Useful life — most common for financial reporting
  • Declining balance: Accelerated method applying fixed rate to net book value
  • Units of production: Based on actual usage or output vs total expected

Key considerations:

  • Run depreciation from the fixed asset register or schedule
  • Verify new additions are set up with correct useful life and method
  • Check for disposals or impairments requiring write-off
  • Ensure consistency between book and tax depreciation tracking

Prepaid Expense Amortization

Amortize prepaid expenses over their benefit period.

Typical entry:

  • Debit: Expense account (insurance, software, rent, etc.)
  • Credit: Prepaid expense

Common prepaid categories:

  • Insurance premiums (typically 12-month policies)
  • Software licenses and subscriptions
  • Prepaid rent (if applicable under lease terms)
  • Prepaid maintenance contracts
  • Conference and event deposits

Key considerations:

  • Maintain an amortization schedule with start/end dates and monthly amounts
  • Review for any prepaid items that should be fully expensed (immaterial amounts)
  • Check for cancelled or terminated contracts requiring accelerated amortization
  • Verify new prepaids are added to the schedule promptly

Payroll Accruals

Accrue compensation and related costs for the period.

Typical entries:

*Salary accrual (for pay periods not aligned with month-end):*

  • Debit: Salary expense (by department)
  • Credit: Accrued payroll

*Bonus accrual:*

  • Debit: Bonus expense (by department)
  • Credit: Accrued bonus

*Benefits accrual:*

  • Debit: Benefits expense
  • Credit: Accrued benefits

*Payroll tax accrual:*

  • Debit: Payroll tax expense
  • Credit: Accrued payroll taxes

Key considerations:

  • Calculate salary accrual based on working days in the period vs pay period
  • Bonus accruals should reflect plan terms (target amounts, performance metrics, payout timing)
  • Include employer-side taxes and benefits (FICA, FUTA, health, 401k match)
  • Track PTO/vacation accrual liability if required by policy or jurisdiction

Revenue Recognition

Recognize revenue based on performance obligations and delivery.

Typical entries:

*Recognize previously deferred revenue:*

  • Debit: Deferred revenue
  • Credit: Revenue

*Recognize revenue with new receivable:*

  • Debit: Accounts receivable
  • Credit: Revenue

*Defer revenue received in advance:*

  • Debit: Cash / Accounts receivable
  • Credit: Deferred revenue

Key considerations:

  • Follow ASC 606 five-step framework for contracts with customers
  • Identify distinct performance obligations in each contract
  • Determine transaction price (including variable consideration)
  • Allocate transaction price to performance obligations
  • Recognize revenue as/when performance obligations are satisfied
  • Maintain contract-level detail for audit support

Supporting Documentation Requirements

Every journal entry should have:

  1. Entry description/memo: Clear, specific description of what the entry records and why
  2. Calculation support: How amounts were derived (formula, schedule, source data reference)
  3. Source documents: Reference to the underlying transactions or events (PO numbers, invoice numbers, contract references, payroll register)
  4. Period: The accounting period the entry applies to
  5. Preparer identification: Who prepared the entry and when
  6. Approval: Evidence of review and approval per the authorization matrix
  7. Reversal indicator: Whether the entry auto-reverses and the reversal date

Review and Approval Workflows

Typical Approval Matrix

Entry TypeAmount ThresholdApprover
Standard recurringAny amountAccounting manager
Non-recurring / manual< $50KAccounting manager
Non-recurring / manual$50K - $250KController
Non-recurring / manual> $250KCFO / VP Finance
Top-side / consolidationAny amountController or above
Out-of-period adjustmentsAny amountController or above

*Note: Thresholds should be set based on your organization's materiality and risk tolerance.*

Review Checklist

Before approving a journal entry, the reviewer should verify:

  • Debits equal credits (entry is balanced)
  • Correct accounting period (not posting to a closed period)
  • Account codes exist and are appropriate for the transaction
  • Amounts are mathematically accurate and supported by calculations
  • Description is clear, specific, and sufficient for audit purposes
  • Department/cost center/project coding is correct
  • Treatment is consistent with prior periods and accounting policies
  • Auto-reversal is set appropriately (accruals should reverse)
  • Supporting documentation is complete and referenced
  • Entry amount is within the preparer's authority level
  • No duplicate of an existing entry
  • Unusual or large amounts are explained and justified

Common Errors to Check For

  1. Unbalanced entries: Debits do not equal credits (system should prevent, but check manual entries)
  2. Wrong period: Entry posted to an incorrect or already-closed period
  3. Wrong sign: Debit entered as credit or vice versa
  4. Duplicate entries: Same transaction recorded twice (check for duplicates before posting)
  5. Wrong account: Entry posted to incorrect GL account (especially similar account codes)
  6. Missing reversal: Accrual entry not set to auto-reverse, causing double-counting
  7. Stale accruals: Recurring accruals not updated for changed circumstances
  8. Round-number estimates: Suspiciously round amounts that may not reflect actual calculations
  9. Incorrect FX rates: Foreign currency entries using wrong exchange rate or date
  10. Missing intercompany elimination: Entries between entities without corresponding elimination
  11. Capitalization errors: Expenses that should be capitalized, or capitalized items that should be expensed
  12. Cut-off errors: Transactions recorded in the wrong period based on delivery or service date

平台分布

Codex

34.84%
按下载量换算2,792

Claude

28.26%
按下载量换算2,264

Cursor

19.4%
按下载量换算1,555

Gemini CLI

10.13%
按下载量换算812

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

需要联网

该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。目前只有一个公开来源,建议同时核对源仓库。

继续浏览同类 Skills