[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71N02W8VYQJ2EAB2ERN6C3B":3,"skill-same:01M71N02W8VYQJ2EAB2ERN6C3B":71},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":22,"publishedAt":41,"linkOnly":42,"markdownContent":43,"markdownBody":44,"frontMatter":45,"refName":49,"commitSha":50,"skillDirectory":51,"forksCount":52,"repositoryHtmlUrl":48,"repositoryHomepageUrl":53,"ownerHtmlUrl":54,"ownerBlogUrl":55,"ownerDescription":6,"updatedAt":56,"install":57,"resources":70},"01M71N02W8VYQJ2EAB2ERN6C3B","finance-tracker",null,"Use when an org role acts as finance tracker and must keep expenses, budgets, budget-vs-actual variance, burn and cash runway current and auditable.","monoes\u002Fmonomind","monoes","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F276744696?v=4","01M71KWF37AJ2NJBP3KWBVSDGT","01M71KWF4CSF8ADH0M6HA09VD2",23,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Ffinance-tracker\u002FSKILL.md",[17],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000040","财务","PROFESSION","适用职业",[23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40],"tracker","finance","finance tracker","burn","org","role","analytics","expenses","Budget","https","github","monomind","runway","keep","sales","when","use","as","2026-11-10 10:56:23",false,"---\nname: finance-tracker\ndescription: \"Use when an org role acts as finance tracker and must keep expenses, budgets, budget-vs-actual variance, burn and cash runway current and auditable.\"\ntags: [\"sales\",\"finance\",\"analytics\"]\ntools: []\nlicense: Apache-2.0\nsource: https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\n---\n# Finance Tracker — Best Practices\n\n## Focus\nKeeps ongoing visibility into money in and out — expenses, budgets, and core financial KPIs — so decisions are made on current, accurate data rather than stale or informal impressions.\n\n## Best practices\n- Record transactions and expenses in real time (or as close to it as possible) rather than batching reconciliation — delayed entry is the single biggest source of inaccurate financial pictures.\n- Separate expense categories clearly (fixed vs. variable, department, project) so spend trends are analyzable, not just a lump total.\n- Track a small set of core KPIs consistently rather than a sprawling dashboard: profitability (margin, burn), liquidity (cash runway, current ratio), and efficiency (cost per unit of output) at minimum.\n- Reconcile budget-to-actual on a fixed cadence (weekly\u002Fmonthly) and flag variances early rather than discovering drift at quarter-end.\n- Keep an audit trail on every entry — source document, approver, category — so figures can be traced and trusted, not just totals.\n- Flag anomalies (unexpected spend spikes, missing categorization, duplicate entries) proactively rather than waiting for a periodic review to surface them.\n- Present financial status in terms decision-makers act on — runway remaining, budget variance, trend direction — not raw ledger dumps.\n- Keep personal\u002Funrelated spend and business finances strictly separated to avoid muddying every downstream metric.\n\n## Common pitfalls\n- Batching data entry infrequently, which produces a financial picture that's always weeks stale by the time anyone looks at it.\n- Tracking too many KPIs at once, diluting attention from the few that actually predict trouble (cash runway, margin trend).\n- Reporting totals without variance context — a number alone doesn't tell anyone whether it's good, bad, or expected.\n- Letting miscategorized or duplicate entries accumulate uncorrected, silently corrupting trend analysis over time.\n\n## Tools & techniques\n- Budget-vs-actual variance reports on a fixed cadence, with variance thresholds that trigger explicit flags.\n- Core KPI set: gross\u002Fnet margin, cash runway, burn rate, cost per unit — tracked as a trend line, not a single snapshot.\n- Categorized expense tracking (fixed\u002Fvariable, by department\u002Fproject) to support cohort-style analysis of where spend is concentrated.\n- Anomaly checks (spend spikes, duplicate\u002Fmissing entries) run automatically before data is reported as final.\n","# Finance Tracker — Best Practices\n\n## Focus\nKeeps ongoing visibility into money in and out — expenses, budgets, and core financial KPIs — so decisions are made on current, accurate data rather than stale or informal impressions.\n\n## Best practices\n- Record transactions and expenses in real time (or as close to it as possible) rather than batching reconciliation — delayed entry is the single biggest source of inaccurate financial pictures.\n- Separate expense categories clearly (fixed vs. variable, department, project) so spend trends are analyzable, not just a lump total.\n- Track a small set of core KPIs consistently rather than a sprawling dashboard: profitability (margin, burn), liquidity (cash runway, current ratio), and efficiency (cost per unit of output) at minimum.\n- Reconcile budget-to-actual on a fixed cadence (weekly\u002Fmonthly) and flag variances early rather than discovering drift at quarter-end.\n- Keep an audit trail on every entry — source document, approver, category — so figures can be traced and trusted, not just totals.\n- Flag anomalies (unexpected spend spikes, missing categorization, duplicate entries) proactively rather than waiting for a periodic review to surface them.\n- Present financial status in terms decision-makers act on — runway remaining, budget variance, trend direction — not raw ledger dumps.\n- Keep personal\u002Funrelated spend and business finances strictly separated to avoid muddying every downstream metric.\n\n## Common pitfalls\n- Batching data entry infrequently, which produces a financial picture that's always weeks stale by the time anyone looks at it.\n- Tracking too many KPIs at once, diluting attention from the few that actually predict trouble (cash runway, margin trend).\n- Reporting totals without variance context — a number alone doesn't tell anyone whether it's good, bad, or expected.\n- Letting miscategorized or duplicate entries accumulate uncorrected, silently corrupting trend analysis over time.\n\n## Tools & techniques\n- Budget-vs-actual variance reports on a fixed cadence, with variance thresholds that trigger explicit flags.\n- Core KPI set: gross\u002Fnet margin, cash runway, burn rate, cost per unit — tracked as a trend line, not a single snapshot.\n- Categorized expense tracking (fixed\u002Fvariable, by department\u002Fproject) to support cohort-style analysis of where spend is concentrated.\n- Anomaly checks (spend spikes, duplicate\u002Fmissing entries) run automatically before data is reported as final.\n",{"name":5,"tags":46,"tools":47,"source":48,"license":14,"description":7},[37,24,29],[],"https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind","main","f7cd4595d0f8959822163e14f9787117765c931a","packages\u002F@monomind\u002Fcli\u002Forg-skills\u002Ffinance-tracker",2,"https:\u002F\u002Fmonoes.github.io\u002Fmonomind\u002F","https:\u002F\u002Fgithub.com\u002Fmonoes","https:\u002F\u002Fmonoes.me","2026-11-10 01:53:48",{"source":8,"skillName":5,"commands":58,"prompt":68,"zipAvailable":69},[59,62,65],{"tool":60,"command":61},"npx","npx skills add monoes\u002Fmonomind --skill finance-tracker",{"tool":63,"command":64},"bunx","bunx skills add monoes\u002Fmonomind --skill finance-tracker",{"tool":66,"command":67},"pnpm","pnpm dlx skills add monoes\u002Fmonomind --skill finance-tracker","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Ffinance-tracker\u002FSKILL.md",true,[],[72,98,132,158,181,208],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":97},"01M71PB3SHWKMNJM6MD65VX8D6","zk-steward","Org role guidance for a ZK steward: engineer zero-knowledge proof systems with circuit design, SNARK vs STARK choice and security review. This is zero-knowledge cryptography, not Zettelkasten note-taking.","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fzk-steward\u002FSKILL.md",[],[79,80,81,82,83,84,85,86,87,88,89,90,34,91,92,93,94,95,27,96],"zk","zk steward","steward","zero-knowledge","engineer","choice","design","knowledge","impact","query","snark","review","security review","stark","zettelkasten","cryptography","security","blockchain","2026-11-10 13:02:02",{"skillNo":99,"name":100,"nameZh":6,"description":101,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":102,"licenseFileUrl":103,"sourceHtmlUrl":104,"categories":105,"keywords":114,"publishedAt":97},"01M71PB18SDG28WBKPKJNB814K","writing-plans","Use when you have a spec or requirements for a multi-step coding task and must write an implementation plan before touching code. Produces bite-sized TDD tasks with exact file paths, code and commands for an engineer with zero context.","MIT","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fwriting-plans\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fwriting-plans\u002FSKILL.md",[106,111],{"categoryNo":107,"categoryName":108,"taxonomyType":109,"taxonomyTypeDesc":110},"01JBSEEDCAT000000000000018","写作与文案","SCENARIO","使用场景",{"categoryNo":112,"categoryName":113,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000036","内容创作者",[115,116,117,83,118,119,38,120,88,121,122,123,124,125,126,127,128,129,130,131],"writing","writing plans","plans","superpowers","implementation plan","you","code","tasks","plan","product","write","commands","paths","suggest","coding","context","ZeRO",{"skillNo":133,"name":134,"nameZh":6,"description":135,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":136,"sourceHtmlUrl":137,"categories":138,"keywords":142,"publishedAt":97},"01M71PAXFM488X9ARXK0T04TF5","write-spec","Write a feature spec or PRD from a problem statement or feature idea. Use when turning a vague idea or user request into a structured document, scoping a feature with goals and non-goals, defining success metrics and acceptance criteria, or breaking a big ask into a phased spec.","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fwrite-spec\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fwrite-spec\u002FSKILL.md",[139],{"categoryNo":140,"categoryName":141,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000031","产品经理",[125,143,144,145,146,86,147,38,148,149,150,124,151,152,153,154,155,156,39,157],"write spec","spec","user request","problem","acceptance","ask","vague","work","request","scoping","idea","metrics","feature","problem statement","document",{"skillNo":159,"name":160,"nameZh":6,"description":161,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":162,"sourceHtmlUrl":163,"categories":164,"keywords":168,"publishedAt":97},"01M71PASSZY800C0RPEARBS918","write-query","Write optimized SQL for your dialect with best practices. Use when translating a natural-language data need into SQL, building a multi-CTE query with joins and aggregations, optimizing a query against a large partitioned table, or getting dialect-specific syntax for Snowflake, BigQuery, Postgres, etc.","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fwrite-query\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fwrite-query\u002FSKILL.md",[165],{"categoryNo":166,"categoryName":167,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000033","数据分析师",[88,125,169,170,171,172,86,39,38,173,174,175,176,150,33,177,32,178,179,180],"write query","postgres","for","snowflake","best practices","natural-language","with","multi","sql","syntax","plugins","data",{"skillNo":182,"name":183,"nameZh":6,"description":184,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":185,"categories":186,"keywords":193,"publishedAt":97},"01M71PAPTX0T3PF6ETFVR96SJJ","workflow-automation","Org role guidance for workflow automation: build and maintain CI\u002FCD definitions in GitHub Actions or equivalent: triggers, jobs, matrices, caching. Covers path filters, dependency caching, parallel jobs, timeouts and fail-fast ordering.","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fworkflow-automation\u002FSKILL.md",[187,190],{"categoryNo":188,"categoryName":189,"taxonomyType":109,"taxonomyTypeDesc":110},"01JBSEEDCAT000000000000011","运维与部署",{"categoryNo":191,"categoryName":192,"taxonomyType":109,"taxonomyTypeDesc":110},"01JBSEEDCAT000000000000023","Skill与智能体开发",[194,195,196,197,171,198,199,200,201,87,202,203,204,88,34,33,205,206,207,32],"Workflow Automation","automation","workflow","parallel","actions","ci","triggers","github actions","maintain","filters","caching","build","dependency","devops",{"skillNo":209,"name":210,"nameZh":6,"description":211,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":212,"categories":213,"keywords":215,"publishedAt":97},"01M71PAM19Z1XTV9NPCFSE2MY8","workflow-architect","Org role guidance for a workflow architect: map full workflow trees for systems, user journeys and agents, covering every branch and failure. Covers discovering workflows from code, handoff contracts, timeouts, recovery paths and observable state.","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fworkflow-architect\u002FSKILL.md",[214],{"categoryNo":191,"categoryName":192,"taxonomyType":109,"taxonomyTypeDesc":110},[196,216,217,218,219,220,221,171,222,223,121,224,225,226,34,33,227,228,32,229],"workflow architect","architect","trees","user journeys","branch","planning","map","workflows","architecture","state","leadership","recovery","operations","systems"]