[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7F06S5RMFSSKZH6E4PXZKZD":3,"skill-same:01M7F06S5RMFSSKZH6E4PXZKZD":107},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":41,"commitSha":42,"skillDirectory":43,"forksCount":14,"repositoryHtmlUrl":44,"repositoryHomepageUrl":6,"ownerHtmlUrl":45,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":46,"install":47,"resources":60},"01M7F06S5RMFSSKZH6E4PXZKZD","research-finance",null,"Use when managing the money for an internal R&D program or portfolio — building a multi-period program budget with the F&A (indirect) split, tracking burn rate and runway against value-inflection milestones, or routing R&D cost items to a capitalize-vs-expense determination. Every budget output surfaces its assumptions block; capitalize-vs-expense is decision-support only and routes to a named finance owner — it never books an entry or decides accounting treatment. Distinct from finance\u002Ffinancial-analysis (corporate DCF, close, valuation) and research\u002Fgrants (funding discovery — this manages money already won).","ibada0410\u002FCLAUDE-SKILLS","ibada0410","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F237597776?v=4","01M7EQWAZNCZV6Y4AGVBXWV5CD","Ibad Ahmed","01M7EQWB08BHXD7VT182EBQDCF",0,"MIT","https:\u002F\u002Fgithub.com\u002Fibada0410\u002FCLAUDE-SKILLS\u002Fblob\u002Fmain\u002FResearch-and-Productivity\u002Fresearch-finance\u002FSKILL.md",[],[],"2026-11-16 10:05:34",false,"---\nname: research-finance\ndescription: Use when managing the money for an internal R&D program or portfolio — building a multi-period program budget with the F&A (indirect) split, tracking burn rate and runway against value-inflection milestones, or routing R&D cost items to a capitalize-vs-expense determination. Every budget output surfaces its assumptions block; capitalize-vs-expense is decision-support only and routes to a named finance owner — it never books an entry or decides accounting treatment. Distinct from finance\u002Ffinancial-analysis (corporate DCF, close, valuation) and research\u002Fgrants (funding discovery — this manages money already won).\nversion: 2.9.0\nauthor: claude-code-skills\nlicense: MIT\ntags: [research-ops, research-finance, rd-budget, burn-rate, runway, fa-rate, capitalize-vs-expense, portfolio]\ncompatible_tools: [claude-code, codex-cli, cursor, antigravity, opencode, gemini-cli]\n---\n\n# research-finance\n\nFinancial management of internal R&D programs and portfolios: program budgeting with F&A, burn\u002Frunway tracking, and capitalize-vs-expense routing. Every number ships with its **assumptions block**, and accounting-treatment calls **route to a named finance owner** — this skill never books an entry.\n\n## Purpose\n\nR&D finance partners, program controllers, and operations leads manage money that has already been allocated or raised — not the corporate close, not the next funding round, not finding a grant. This skill structures three recurring decisions:\n\nThree deterministic tools:\n\n1. `program_budget_planner.py` — Builds a multi-period budget from work-package line items, applies the F&A (indirect) rate to an MTDC-style eligible base, and rolls up direct \u002F F&A \u002F fully-loaded cost per period with an explicit assumptions block.\n2. `burn_runway_tracker.py` — Computes average + trailing burn, runway in periods\u002Fmonths, and whether each value-inflection milestone is reachable before cash runs out. Flags accelerating burn and below-threshold runway.\n3. `capex_vs_opex_router.py` — Scores each R&D cost item against the IAS 38 development-phase criteria (or flags US GAAP ASC 730 expense-as-incurred) and routes it to **CAPITALIZE-CANDIDATE \u002F EXPENSE \u002F FINANCE-OWNER-REVIEW** with a named owner. Never auto-decides.\n\n## When to use\n\nInvoke this skill when:\n\n- You are building or revising an R&D program budget and need the F&A split made explicit.\n- A program's runway is in question and you need a milestone-vs-cash read.\n- Finance asks whether a development cost can be capitalized and you need a defensible first routing.\n- You are preparing a portfolio review and need per-program burn consistency.\n\n**Do NOT use this skill to**: run corporate DCF \u002F valuation \u002F close (use `finance\u002Ffinancial-analysis`), discover or position grants (use `research\u002Fgrants`), or make the final accounting determination (that is the controller's + auditor's call — this tool only routes).\n\n## Workflow\n\n1. **Lay out the program** — Fill `assets\u002Frd_program_budget_template.md` with work-package lines, categories, and per-period amounts.\n2. **Build the budget** — Run `program_budget_planner.py --input program.json --profile {pharma-rd|biotech|medtech|deep-tech|software-rd|university-lab} --fa-rate \u003Cnegotiated rate>`. Read direct \u002F F&A \u002F fully-loaded rollups + assumptions.\n3. **Track burn & runway** — Run `burn_runway_tracker.py --input ledger.json --threshold-months 6`. Read runway + milestone verdicts + flags.\n4. **Route accounting treatment** — Run `capex_vs_opex_router.py --input costs.json --standard {ifrs|usgaap}`. Read the per-item routing; send CAPITALIZE-CANDIDATE and FINANCE-OWNER-REVIEW items to the named owner.\n5. **Assemble the review** — Combine into a program-finance packet. Every number carries its assumptions; treatment calls carry a named owner.\n\n## Scripts\n\n| Script | Purpose | Profiles |\n|---|---|---|\n| `scripts\u002Fprogram_budget_planner.py` | Multi-period budget + F&A split + assumptions | pharma-rd, biotech, medtech, deep-tech, software-rd, university-lab |\n| `scripts\u002Fburn_runway_tracker.py` | Burn, runway, milestone-vs-cash alignment | n\u002Fa (ledger-driven) |\n| `scripts\u002Fcapex_vs_opex_router.py` | IAS 38 \u002F ASC 730 routing to named finance owner | pharma-rd, biotech, medtech, deep-tech, software-rd, university-lab |\n\nAll three: stdlib-only, `--help`, `--sample`, `--output {human,json}`.\n\n## Onboarding & customization\n\nRun the onboarding questionnaire **once before you start** — it captures your defaults so every tool in this skill is pre-configured. Customization is the point: the answers actually change tool behavior.\n\n```bash\npython3 scripts\u002Fonboard.py            # interactive (also: --defaults, --set key=value, --reset)\npython3 scripts\u002Fonboard.py --show     # see the questions + current effective config\n```\n\nAnswers are saved to `~\u002F.config\u002Fresearch-ops\u002Fresearch-finance.json` (global) or `.\u002F.research-ops\u002Fresearch-finance.json` (`--scope project`) and are read automatically by `config_loader.py`. They set the default R&D-area **profile**, the default **F&A rate**, the **runway alert threshold**, the **accounting standard**, and the named **finance owner** printed on capitalize-vs-expense routing. CLI flags always override saved config; `RESEARCH_OPS_NO_CONFIG=1` ignores it.\n\n**The five questions:** R&D area · F&A rate · runway threshold · accounting standard · finance owner.\n\n## Optimize with autoresearch (opt-in)\n\nThis skill ships an **isolated, opt-in** bridge to `engineering\u002Fautoresearch-agent`. Only when you ask to \"optimize\" \u002F \"extend runway\" \u002F \"run a loop\" does an autoresearch experiment iteratively improve a program plan against this skill's runway metric. `scripts\u002Far_evaluator.py` is the ground-truth evaluator; it prints `runway_months: \u003Cfloat>` (higher is better).\n\n```bash\n\u002Far:setup --domain custom --name extend-runway \\\n  --target ledger.json \\\n  --eval \"python3 ar_evaluator.py --target ledger.json\" \\\n  --metric runway_months --direction higher\n\u002Far:loop custom\u002Fextend-runway\n```\n\nIsolated: no hard dependency — autoresearch runs only on demand, and the loop edits `ledger.json`, never the evaluator.\n\n## References\n\n- `references\u002Frd_program_finance_canon.md` — IAS 38 (research vs development); ASC 730 + ASC 985-20; Uniform Guidance 2 CFR 200 (F&A); FASB\u002FIFRS capitalization criteria; NICRA basics.\n- `references\u002Fburn_and_portfolio.md` — Cooper stage-gate; rNPV \u002F real-options for R&D; risk-adjusted portfolio ROI; burn-rate \u002F runway frameworks; milestone-based budgeting.\n- `references\u002Findirect_rate_modeling.md` — F&A pool composition (facilities + administration); MTDC base; de minimis 10%; fringe\u002Foverhead loading; CAS primer.\n\n## Assumptions\n\n- The F&A rate is the most error-prone input. The planner applies whatever rate you pass; it warns you to confirm it is a negotiated NICRA, not a guess.\n- Burn\u002Frunway uses the trailing (recent-weighted) burn as the forward run-rate and assumes flat forward spend unless your ledger encodes a ramp.\n- The capex router asserts criteria from your input; asserting \"technical feasibility\" does not make it true — the named finance owner and auditor validate it.\n- Profiles annotate context (e.g., \"most drug R&D is expensed\") but do not change the accounting test.\n\n## Anti-patterns\n\n- **Stating a budget number without its assumptions.** F&A rate, escalation, and base must travel with the number.\n- **Auto-deciding capitalize-vs-expense.** This tool routes; the controller (and auditor where required) decides.\n- **Using lifetime-average burn for runway.** Recent burn is the honest forward run-rate; averages hide a slowdown or a ramp.\n- **Applying F&A to the full base.** Capital equipment, large subaward portions, and certain categories are MTDC-exempt.\n- **Confusing this with corporate finance.** Valuation, close, and fundraising live in `finance\u002F`.\n\n## Distinct from\n\n| Sibling \u002F neighbor | Scope | Difference |\n|---|---|---|\n| `finance\u002Ffinancial-analysis` | Corporate DCF, ratios, close, rolling forecast, SaaS metrics | That is **company-level**; this is **R&D-program-level** |\n| `research\u002Fgrants` | NIH funding discovery + positioning | That **finds funding**; this **manages money already won** |\n| `clinical-research` (sibling) | Study design + feasibility + budget gate-check | That **scopes** the study; this **funds + tracks** the program |\n| `ra-qm-team` | Regulatory\u002FQM submission | Unrelated — no financial scope |\n\n## Quick examples\n\n```bash\npython3 scripts\u002Fprogram_budget_planner.py --sample\npython3 scripts\u002Fprogram_budget_planner.py --input program.json --profile university-lab --fa-rate 0.585\npython3 scripts\u002Fburn_runway_tracker.py --sample --output json\npython3 scripts\u002Fcapex_vs_opex_router.py --sample --standard ifrs\n```\n\nThe sample budget excludes the sequencer (capital equipment) and CRO subaward from the F&A base; the capex router routes exploratory screening to EXPENSE, a fully-criteria'd pilot line to CAPITALIZE-CANDIDATE, and a partial-criteria software build to FINANCE-OWNER-REVIEW.\n\n## Forcing-question library (Matt Pocock grill discipline)\n\nWalked one at a time by `\u002Fcs:grill-research-ops` or the orchestrator. Recommended answer + canon citation per question. Never bundled.\n\n1. **\"Is this spend in the research phase or the development phase — and can you evidence technical feasibility?\"**\n   Recommended: research = expense; development = capitalize-candidate only with feasibility evidence, routed to a named finance owner.\n   Canon: IAS 38.54-57; ASC 730.\n\n2. **\"What F&A \u002F indirect rate are you applying, and is it your negotiated NICRA, a de minimis 10%, or an assumption?\"**\n   Recommended: use the negotiated rate; if assumed, flag it explicitly.\n   Canon: 2 CFR 200 (Uniform Guidance); NICRA basics.\n\n3. **\"What's runway in months at current burn, and does it clear the next value-inflection milestone?\"**\n   Recommended: runway must cover the milestone plus a buffer; surface the gap.\n   Canon: Cooper stage-gate; SaaS\u002Fstartup efficiency frameworks (a16z, Bessemer).\n\n4. **\"Is portfolio ROI risk-adjusted (rNPV \u002F probability-of-success weighted) or raw NPV?\"**\n   Recommended: risk-adjusted; raw NPV overstates R&D value.\n   Canon: rNPV drug-development valuation; real-options literature.\n\n5. **\"Who is the named finance \u002F controller owner who signs the capitalize-vs-expense treatment?\"**\n   Recommended: name them — this tool recommends, it never books the entry.\n   Canon: ASC 730 \u002F IAS 38 governance; auditor sign-off requirements.\n\nWalk depth-first. Lock 1-2 before opening 3-5. After all are answered, invoke `program_budget_planner.py` → `burn_runway_tracker.py` → `capex_vs_opex_router.py`.\n","# research-finance\n\nFinancial management of internal R&D programs and portfolios: program budgeting with F&A, burn\u002Frunway tracking, and capitalize-vs-expense routing. Every number ships with its **assumptions block**, and accounting-treatment calls **route to a named finance owner** — this skill never books an entry.\n\n## Purpose\n\nR&D finance partners, program controllers, and operations leads manage money that has already been allocated or raised — not the corporate close, not the next funding round, not finding a grant. This skill structures three recurring decisions:\n\nThree deterministic tools:\n\n1. `program_budget_planner.py` — Builds a multi-period budget from work-package line items, applies the F&A (indirect) rate to an MTDC-style eligible base, and rolls up direct \u002F F&A \u002F fully-loaded cost per period with an explicit assumptions block.\n2. `burn_runway_tracker.py` — Computes average + trailing burn, runway in periods\u002Fmonths, and whether each value-inflection milestone is reachable before cash runs out. Flags accelerating burn and below-threshold runway.\n3. `capex_vs_opex_router.py` — Scores each R&D cost item against the IAS 38 development-phase criteria (or flags US GAAP ASC 730 expense-as-incurred) and routes it to **CAPITALIZE-CANDIDATE \u002F EXPENSE \u002F FINANCE-OWNER-REVIEW** with a named owner. Never auto-decides.\n\n## When to use\n\nInvoke this skill when:\n\n- You are building or revising an R&D program budget and need the F&A split made explicit.\n- A program's runway is in question and you need a milestone-vs-cash read.\n- Finance asks whether a development cost can be capitalized and you need a defensible first routing.\n- You are preparing a portfolio review and need per-program burn consistency.\n\n**Do NOT use this skill to**: run corporate DCF \u002F valuation \u002F close (use `finance\u002Ffinancial-analysis`), discover or position grants (use `research\u002Fgrants`), or make the final accounting determination (that is the controller's + auditor's call — this tool only routes).\n\n## Workflow\n\n1. **Lay out the program** — Fill `assets\u002Frd_program_budget_template.md` with work-package lines, categories, and per-period amounts.\n2. **Build the budget** — Run `program_budget_planner.py --input program.json --profile {pharma-rd|biotech|medtech|deep-tech|software-rd|university-lab} --fa-rate \u003Cnegotiated rate>`. Read direct \u002F F&A \u002F fully-loaded rollups + assumptions.\n3. **Track burn & runway** — Run `burn_runway_tracker.py --input ledger.json --threshold-months 6`. Read runway + milestone verdicts + flags.\n4. **Route accounting treatment** — Run `capex_vs_opex_router.py --input costs.json --standard {ifrs|usgaap}`. Read the per-item routing; send CAPITALIZE-CANDIDATE and FINANCE-OWNER-REVIEW items to the named owner.\n5. **Assemble the review** — Combine into a program-finance packet. Every number carries its assumptions; treatment calls carry a named owner.\n\n## Scripts\n\n| Script | Purpose | Profiles |\n|---|---|---|\n| `scripts\u002Fprogram_budget_planner.py` | Multi-period budget + F&A split + assumptions | pharma-rd, biotech, medtech, deep-tech, software-rd, university-lab |\n| `scripts\u002Fburn_runway_tracker.py` | Burn, runway, milestone-vs-cash alignment | n\u002Fa (ledger-driven) |\n| `scripts\u002Fcapex_vs_opex_router.py` | IAS 38 \u002F ASC 730 routing to named finance owner | pharma-rd, biotech, medtech, deep-tech, software-rd, university-lab |\n\nAll three: stdlib-only, `--help`, `--sample`, `--output {human,json}`.\n\n## Onboarding & customization\n\nRun the onboarding questionnaire **once before you start** — it captures your defaults so every tool in this skill is pre-configured. Customization is the point: the answers actually change tool behavior.\n\n```bash\npython3 scripts\u002Fonboard.py            # interactive (also: --defaults, --set key=value, --reset)\npython3 scripts\u002Fonboard.py --show     # see the questions + current effective config\n```\n\nAnswers are saved to `~\u002F.config\u002Fresearch-ops\u002Fresearch-finance.json` (global) or `.\u002F.research-ops\u002Fresearch-finance.json` (`--scope project`) and are read automatically by `config_loader.py`. They set the default R&D-area **profile**, the default **F&A rate**, the **runway alert threshold**, the **accounting standard**, and the named **finance owner** printed on capitalize-vs-expense routing. CLI flags always override saved config; `RESEARCH_OPS_NO_CONFIG=1` ignores it.\n\n**The five questions:** R&D area · F&A rate · runway threshold · accounting standard · finance owner.\n\n## Optimize with autoresearch (opt-in)\n\nThis skill ships an **isolated, opt-in** bridge to `engineering\u002Fautoresearch-agent`. Only when you ask to \"optimize\" \u002F \"extend runway\" \u002F \"run a loop\" does an autoresearch experiment iteratively improve a program plan against this skill's runway metric. `scripts\u002Far_evaluator.py` is the ground-truth evaluator; it prints `runway_months: \u003Cfloat>` (higher is better).\n\n```bash\n\u002Far:setup --domain custom --name extend-runway \\\n  --target ledger.json \\\n  --eval \"python3 ar_evaluator.py --target ledger.json\" \\\n  --metric runway_months --direction higher\n\u002Far:loop custom\u002Fextend-runway\n```\n\nIsolated: no hard dependency — autoresearch runs only on demand, and the loop edits `ledger.json`, never the evaluator.\n\n## References\n\n- `references\u002Frd_program_finance_canon.md` — IAS 38 (research vs development); ASC 730 + ASC 985-20; Uniform Guidance 2 CFR 200 (F&A); FASB\u002FIFRS capitalization criteria; NICRA basics.\n- `references\u002Fburn_and_portfolio.md` — Cooper stage-gate; rNPV \u002F real-options for R&D; risk-adjusted portfolio ROI; burn-rate \u002F runway frameworks; milestone-based budgeting.\n- `references\u002Findirect_rate_modeling.md` — F&A pool composition (facilities + administration); MTDC base; de minimis 10%; fringe\u002Foverhead loading; CAS primer.\n\n## Assumptions\n\n- The F&A rate is the most error-prone input. The planner applies whatever rate you pass; it warns you to confirm it is a negotiated NICRA, not a guess.\n- Burn\u002Frunway uses the trailing (recent-weighted) burn as the forward run-rate and assumes flat forward spend unless your ledger encodes a ramp.\n- The capex router asserts criteria from your input; asserting \"technical feasibility\" does not make it true — the named finance owner and auditor validate it.\n- Profiles annotate context (e.g., \"most drug R&D is expensed\") but do not change the accounting test.\n\n## Anti-patterns\n\n- **Stating a budget number without its assumptions.** F&A rate, escalation, and base must travel with the number.\n- **Auto-deciding capitalize-vs-expense.** This tool routes; the controller (and auditor where required) decides.\n- **Using lifetime-average burn for runway.** Recent burn is the honest forward run-rate; averages hide a slowdown or a ramp.\n- **Applying F&A to the full base.** Capital equipment, large subaward portions, and certain categories are MTDC-exempt.\n- **Confusing this with corporate finance.** Valuation, close, and fundraising live in `finance\u002F`.\n\n## Distinct from\n\n| Sibling \u002F neighbor | Scope | Difference |\n|---|---|---|\n| `finance\u002Ffinancial-analysis` | Corporate DCF, ratios, close, rolling forecast, SaaS metrics | That is **company-level**; this is **R&D-program-level** |\n| `research\u002Fgrants` | NIH funding discovery + positioning | That **finds funding**; this **manages money already won** |\n| `clinical-research` (sibling) | Study design + feasibility + budget gate-check | That **scopes** the study; this **funds + tracks** the program |\n| `ra-qm-team` | Regulatory\u002FQM submission | Unrelated — no financial scope |\n\n## Quick examples\n\n```bash\npython3 scripts\u002Fprogram_budget_planner.py --sample\npython3 scripts\u002Fprogram_budget_planner.py --input program.json --profile university-lab --fa-rate 0.585\npython3 scripts\u002Fburn_runway_tracker.py --sample --output json\npython3 scripts\u002Fcapex_vs_opex_router.py --sample --standard ifrs\n```\n\nThe sample budget excludes the sequencer (capital equipment) and CRO subaward from the F&A base; the capex router routes exploratory screening to EXPENSE, a fully-criteria'd pilot line to CAPITALIZE-CANDIDATE, and a partial-criteria software build to FINANCE-OWNER-REVIEW.\n\n## Forcing-question library (Matt Pocock grill discipline)\n\nWalked one at a time by `\u002Fcs:grill-research-ops` or the orchestrator. Recommended answer + canon citation per question. Never bundled.\n\n1. **\"Is this spend in the research phase or the development phase — and can you evidence technical feasibility?\"**\n   Recommended: research = expense; development = capitalize-candidate only with feasibility evidence, routed to a named finance owner.\n   Canon: IAS 38.54-57; ASC 730.\n\n2. **\"What F&A \u002F indirect rate are you applying, and is it your negotiated NICRA, a de minimis 10%, or an assumption?\"**\n   Recommended: use the negotiated rate; if assumed, flag it explicitly.\n   Canon: 2 CFR 200 (Uniform Guidance); NICRA basics.\n\n3. **\"What's runway in months at current burn, and does it clear the next value-inflection milestone?\"**\n   Recommended: runway must cover the milestone plus a buffer; surface the gap.\n   Canon: Cooper stage-gate; SaaS\u002Fstartup efficiency frameworks (a16z, Bessemer).\n\n4. **\"Is portfolio ROI risk-adjusted (rNPV \u002F probability-of-success weighted) or raw NPV?\"**\n   Recommended: risk-adjusted; raw NPV overstates R&D value.\n   Canon: rNPV drug-development valuation; real-options literature.\n\n5. **\"Who is the named finance \u002F controller owner who signs the capitalize-vs-expense treatment?\"**\n   Recommended: name them — this tool recommends, it never books the entry.\n   Canon: ASC 730 \u002F IAS 38 governance; auditor sign-off requirements.\n\nWalk depth-first. Lock 1-2 before opening 3-5. After all are answered, invoke `program_budget_planner.py` → `burn_runway_tracker.py` → `capex_vs_opex_router.py`.\n",{"name":5,"tags":24,"author":32,"license":15,"version":33,"description":7,"compatible_tools":34},[25,5,26,27,28,29,30,31],"research-ops","rd-budget","burn-rate","runway","fa-rate","capitalize-vs-expense","portfolio","claude-code-skills","2.9.0",[35,36,37,38,39,40],"claude-code","codex-cli","cursor","antigravity","opencode","gemini-cli","main","26a049c61e6bda33cca8f5e7c1fcdcd20681221f","Research-and-Productivity\u002Fresearch-finance","https:\u002F\u002Fgithub.com\u002Fibada0410\u002FCLAUDE-SKILLS","https:\u002F\u002Fgithub.com\u002Fibada0410","2026-10-15 17:21:48",{"source":8,"skillName":5,"commands":48,"prompt":58,"zipAvailable":59},[49,52,55],{"tool":50,"command":51},"npx","npx skills add ibada0410\u002FCLAUDE-SKILLS --skill research-finance",{"tool":53,"command":54},"bunx","bunx skills add ibada0410\u002FCLAUDE-SKILLS --skill research-finance",{"tool":56,"command":57},"pnpm","pnpm dlx skills add ibada0410\u002FCLAUDE-SKILLS --skill research-finance","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fibada0410\u002FCLAUDE-SKILLS\u002Fblob\u002Fmain\u002FResearch-and-Productivity\u002Fresearch-finance\u002FSKILL.md",true,[61,67,73,77,81,87,91,95,99,103],{"path":62,"resourceType":63,"resourceTypeDesc":64,"sizeBytes":65,"sourceHtmlUrl":66},"assets\u002Frd_program_budget_template.md","ASSET","资产文件",1792,"https:\u002F\u002Fgithub.com\u002Fibada0410\u002FCLAUDE-SKILLS\u002Fblob\u002Fmain\u002FResearch-and-Productivity\u002Fresearch-finance\u002Fassets\u002Frd_program_budget_template.md",{"path":68,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":71,"sourceHtmlUrl":72},"references\u002Fburn_and_portfolio.md","REFERENCE","参考文档",2776,"https:\u002F\u002Fgithub.com\u002Fibada0410\u002FCLAUDE-SKILLS\u002Fblob\u002Fmain\u002FResearch-and-Productivity\u002Fresearch-finance\u002Freferences\u002Fburn_and_portfolio.md",{"path":74,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":75,"sourceHtmlUrl":76},"references\u002Findirect_rate_modeling.md",2459,"https:\u002F\u002Fgithub.com\u002Fibada0410\u002FCLAUDE-SKILLS\u002Fblob\u002Fmain\u002FResearch-and-Productivity\u002Fresearch-finance\u002Freferences\u002Findirect_rate_modeling.md",{"path":78,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":79,"sourceHtmlUrl":80},"references\u002Frd_program_finance_canon.md",2833,"https:\u002F\u002Fgithub.com\u002Fibada0410\u002FCLAUDE-SKILLS\u002Fblob\u002Fmain\u002FResearch-and-Productivity\u002Fresearch-finance\u002Freferences\u002Frd_program_finance_canon.md",{"path":82,"resourceType":83,"resourceTypeDesc":84,"sizeBytes":85,"sourceHtmlUrl":86},"scripts\u002Far_evaluator.py","SCRIPT","脚本",2468,"https:\u002F\u002Fgithub.com\u002Fibada0410\u002FCLAUDE-SKILLS\u002Fblob\u002Fmain\u002FResearch-and-Productivity\u002Fresearch-finance\u002Fscripts\u002Far_evaluator.py",{"path":88,"resourceType":83,"resourceTypeDesc":84,"sizeBytes":89,"sourceHtmlUrl":90},"scripts\u002Fburn_runway_tracker.py",6312,"https:\u002F\u002Fgithub.com\u002Fibada0410\u002FCLAUDE-SKILLS\u002Fblob\u002Fmain\u002FResearch-and-Productivity\u002Fresearch-finance\u002Fscripts\u002Fburn_runway_tracker.py",{"path":92,"resourceType":83,"resourceTypeDesc":84,"sizeBytes":93,"sourceHtmlUrl":94},"scripts\u002Fcapex_vs_opex_router.py",7658,"https:\u002F\u002Fgithub.com\u002Fibada0410\u002FCLAUDE-SKILLS\u002Fblob\u002Fmain\u002FResearch-and-Productivity\u002Fresearch-finance\u002Fscripts\u002Fcapex_vs_opex_router.py",{"path":96,"resourceType":83,"resourceTypeDesc":84,"sizeBytes":97,"sourceHtmlUrl":98},"scripts\u002Fconfig_loader.py",3912,"https:\u002F\u002Fgithub.com\u002Fibada0410\u002FCLAUDE-SKILLS\u002Fblob\u002Fmain\u002FResearch-and-Productivity\u002Fresearch-finance\u002Fscripts\u002Fconfig_loader.py",{"path":100,"resourceType":83,"resourceTypeDesc":84,"sizeBytes":101,"sourceHtmlUrl":102},"scripts\u002Fonboard.py",4267,"https:\u002F\u002Fgithub.com\u002Fibada0410\u002FCLAUDE-SKILLS\u002Fblob\u002Fmain\u002FResearch-and-Productivity\u002Fresearch-finance\u002Fscripts\u002Fonboard.py",{"path":104,"resourceType":83,"resourceTypeDesc":84,"sizeBytes":105,"sourceHtmlUrl":106},"scripts\u002Fprogram_budget_planner.py",7185,"https:\u002F\u002Fgithub.com\u002Fibada0410\u002FCLAUDE-SKILLS\u002Fblob\u002Fmain\u002FResearch-and-Productivity\u002Fresearch-finance\u002Fscripts\u002Fprogram_budget_planner.py",[108,117,125,133,141,149],{"skillNo":109,"name":110,"nameZh":6,"description":111,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":112,"licenseFileUrl":113,"sourceHtmlUrl":114,"categories":115,"keywords":116,"publishedAt":19},"01M7F0YW5WXY39G4W3203E8PHN","internal-comms","A set of resources to help me write all kinds of internal communications, using the formats that my company likes to use. Claude should use this skill whenever asked to write some sort of internal communications (status reports, leadership updates, 3P updates, company newsletters, FAQs, incident reports, project updates, etc.).","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fibada0410\u002FCLAUDE-SKILLS\u002Fblob\u002Fmain\u002FWriting-Compliance-and-General\u002Finternal-comms\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fibada0410\u002FCLAUDE-SKILLS\u002Fblob\u002Fmain\u002FWriting-Compliance-and-General\u002Finternal-comms\u002FSKILL.md",[],[],{"skillNo":118,"name":119,"nameZh":6,"description":120,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":121,"sourceHtmlUrl":122,"categories":123,"keywords":124,"publishedAt":19},"01M7F0YGDEVB7BCSJX8V91XK15","eu-ai-act-reviewer","Review user journeys, public content, and codebases for potentially relevant EU AI Act provisions, with exact official citations, evidence gaps, application dates, and plain-language next actions. Use for EU AI Act issue-spotting, not final legal or compliance decisions.","https:\u002F\u002Fgithub.com\u002Fibada0410\u002FCLAUDE-SKILLS\u002Fblob\u002Fmain\u002FWriting-Compliance-and-General\u002Feu-ai-act-reviewer\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fibada0410\u002FCLAUDE-SKILLS\u002Fblob\u002Fmain\u002FWriting-Compliance-and-General\u002Feu-ai-act-reviewer\u002FSKILL.md",[],[],{"skillNo":126,"name":127,"nameZh":6,"description":128,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":112,"licenseFileUrl":129,"sourceHtmlUrl":130,"categories":131,"keywords":132,"publishedAt":19},"01M7F0Y1GYY34HD1WM5EWYB80Z","discernment-nudge","After you give a substantive answer or draft that the user may act on — advice or recommendations, drafted artifacts such as goals, plans, pitches, proposals, or emails, estimates or projections, analysis or interpretation of data, factual claims they may rely on, or a multi-step argument — invoke this skill BEFORE finalizing your reply and then, if it applies, append 2-3 short follow-up questions, each tied to something specific in what you just produced, that help the user check key facts, probe the reasoning or assumptions, and notice missing context. Do this at most once per conversation. Skip it when the user asked a trivial how-to or simple lookup, wants a purely educational explanation, asked you only to format, convert, or assemble a file from content they provided, is writing code they will run, is doing creative writing or casual chat, or already asked you to double-check, cite, or review — the skill file explains these boundaries and the exact output format.","https:\u002F\u002Fgithub.com\u002Fibada0410\u002FCLAUDE-SKILLS\u002Fblob\u002Fmain\u002FWriting-Compliance-and-General\u002Fdiscernment-nudge\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fibada0410\u002FCLAUDE-SKILLS\u002Fblob\u002Fmain\u002FWriting-Compliance-and-General\u002Fdiscernment-nudge\u002FSKILL.md",[],[],{"skillNo":134,"name":135,"nameZh":6,"description":136,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":112,"licenseFileUrl":137,"sourceHtmlUrl":138,"categories":139,"keywords":140,"publishedAt":19},"01M7F0W4SJJY8Z345JZH9901RD","academy-guide","Stop and check this skill before finishing any reply to a question about how to use Claude or a Claude product — it recommends matching courses, tutorials, and use cases from Claude Academy (academy.claude.com), Anthropic's learning hub. Trigger on: \"how do I\", \"how can I\", \"getting started with\", \"what can Claude do\", \"teach me\", \"learn to use\"; questions about artifacts, projects, skills, plugins, connectors, MCP; requests about rolling Claude out to a team, class, or organization; and any ask for training materials, onboarding content, or learning resources. Use it when the user is learning how to use a feature or product — not when they are mid-task and just want the task done. This skill composes with other skills: after consulting product documentation to answer how a Claude feature works, also check here for a matching course or tutorial — a docs-grounded answer and an Academy recommendation belong together. Only recommend on a strong match; never invent Academy content.","https:\u002F\u002Fgithub.com\u002Fibada0410\u002FCLAUDE-SKILLS\u002Fblob\u002Fmain\u002FWriting-Compliance-and-General\u002Facademy-guide\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fibada0410\u002FCLAUDE-SKILLS\u002Fblob\u002Fmain\u002FWriting-Compliance-and-General\u002Facademy-guide\u002FSKILL.md",[],[],{"skillNo":142,"name":143,"nameZh":6,"description":144,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":112,"licenseFileUrl":145,"sourceHtmlUrl":146,"categories":147,"keywords":148,"publishedAt":19},"01M7F0W0X5YSTSFS77CFA5P5KJ","webapp-testing","Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.","https:\u002F\u002Fgithub.com\u002Fibada0410\u002FCLAUDE-SKILLS\u002Fblob\u002Fmain\u002FUI-and-Web-Design\u002Fwebapp-testing\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fibada0410\u002FCLAUDE-SKILLS\u002Fblob\u002Fmain\u002FUI-and-Web-Design\u002Fwebapp-testing\u002FSKILL.md",[],[],{"skillNo":150,"name":151,"nameZh":6,"description":152,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":112,"licenseFileUrl":153,"sourceHtmlUrl":154,"categories":155,"keywords":156,"publishedAt":19},"01M7F0VV4P1HYHG44P0K48C4Q7","web-artifacts-builder","Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn\u002Fui). Use for complex artifacts requiring state management, routing, or shadcn\u002Fui components - not for simple single-file HTML\u002FJSX artifacts.","https:\u002F\u002Fgithub.com\u002Fibada0410\u002FCLAUDE-SKILLS\u002Fblob\u002Fmain\u002FUI-and-Web-Design\u002Fweb-artifacts-builder\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fibada0410\u002FCLAUDE-SKILLS\u002Fblob\u002Fmain\u002FUI-and-Web-Design\u002Fweb-artifacts-builder\u002FSKILL.md",[],[]]