[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M718K5KPE357S4MAN2S98VCF":3,"skill-same:01M718K5KPE357S4MAN2S98VCF":85},{"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":39,"linkOnly":40,"markdownContent":41,"markdownBody":42,"frontMatter":43,"refName":46,"commitSha":47,"skillDirectory":48,"forksCount":49,"repositoryHtmlUrl":50,"repositoryHomepageUrl":6,"ownerHtmlUrl":51,"ownerBlogUrl":52,"ownerDescription":53,"updatedAt":54,"install":55,"resources":68},"01M718K5KPE357S4MAN2S98VCF","project-manager",null,"Manage projects end to end: intake, prioritise, track status across parallel builds, and produce standup and weekly-review summaries. Use when the user asks to manage, track or drive a project, plan the week, or asks for a status or standup update.","lionelsimai\u002Fclaude-skills-collection","lionelsimai","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F260158848?v=4","01M6CHZPS8G9TSB113TT0BBM6E","Lionel ","01M6CHZPXGW2SPE3BHQTGJ0S8J",38,"MIT","https:\u002F\u002Fgithub.com\u002Flionelsimai\u002Fclaude-skills-collection\u002Fblob\u002Fmain\u002Fskills\u002Fproject-manager\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38],"project manager","manager","project","summaries","plan","track","across","review","prioritise","when","use","produce","intake","end","manage","standup","for","projects","weekly","parallel","2026-11-10 10:12:30",false,"---\nname: project-manager\ndescription: \"Manage projects end to end: intake, prioritise, track status across parallel builds, and produce standup and weekly-review summaries. Use when the user asks to manage, track or drive a project, plan the week, or asks for a status or standup update.\"\ncategory: Operations\nlicense: MIT\nversion: 1.0.0\n---\n\n# Project Manager\n\n## Purpose\nKeep the user's many parallel builds (workshops, partnerships, community programs, product experiments, job-hunt threads) organized: one place for every project, its goal, its tasks, and its current state. Own task intake, prioritization, and status reporting. Keep builds running in their own threads — this skill coordinates and reports; it never does unrelated work on the side.\n\nInspired by [finna\u002Fproject-manager-skill](https:\u002F\u002Fgithub.com\u002Ffinna\u002Fproject-manager-skill); rebuilt here in original form for a multi-project builder workflow.\n\n## Tooling\n- CLI: `bin\u002Fpm` (python3 stdlib only). Run as `. \u003Ccmd>`, or add the skill's `bin\u002F` to PATH for the session.\n- Data: one JSON file per project in `.`. Override with `PM_PROJECTS_DIR` (used by tests). Schema in `references\u002Ftask-schema.md`.\n\n## Workflow\n\n### 1. Intake\nWhen the user names a new project or a task, capture it before anything else:\n- `pm init \"Project Name\" --goal \"...\" --deadline YYYY-MM-DD` (creates the project file)\n- `pm task add \u003Cproject> \"Task title\" --priority P0|P1|P2|P3 --due YYYY-MM-DD`\n\n### 2. Prioritize\n- Default every task to P2. P0 = blocked revenue or hard deadline this week; P1 = moves a live deal or event; P3 = nice-to-have.\n- If he gives a deadline, record it. Flag overdue items in status and reviews — never silently drop them.\n- One project may have many tasks; across projects, keep the total P0 count small. If P0s pile up, surface that explicitly.\n\n### 3. Track\n- `pm task start|done|block|unblock \u003Cproject> \u003Ctask-id> --note \"...\"` — move tasks through `todo → doing → done`, with `blocked` as a side state. Notes are timestamped and kept.\n- `pm note \u003Cproject> \"text\" [--task tN]` — decisions, context, anything worth remembering about the project.\n- `pm status \u003Cproject>` — render the markdown status summary (goal, deadline, grouped tasks, recent notes). `--out file.md` writes it to a file.\n\n### 4. Report\n- **Standup:** `pm standup` — done since yesterday, next up, blocked, across all active projects. Good as a morning brief.\n- **Weekly review:** `pm review` — shipped \u002F in-flight \u002F blocked \u002F overdue per project for the trailing 7 days.\n- `pm list` — active projects with done counts; `--status all` or `archived` to see the rest; `pm archive \u003Cproject>` when finished or killed.\n\n## Output Contract\n- `pm status` \u002F `pm standup` \u002F `pm review` print markdown to stdout — reuse it directly in the chat reply or as a document.\n- When reporting to the user: lead with blockers and overdue items, then what's next. Keep it short; he reads bullets, not essays.\n- A status answer never starts new work, sends messages, or spends money. Say so if he asks.\n\n## Operating Rules\n- Project facts live in `.`, never in this skill's directory and never in memory files.\n- Keep `implemented` distinct from `done-and-verified`: a task is `done` only when its outcome is actually confirmed, not when a draft exists.\n- Silence is not approval. If a milestone needs a decision that changes scope, deadline, or money, ask.\n- Killed projects get archived, not deleted — the record stays for the weekly review.\n\n## When to use\n\nUse this skill when the task described in the purpose above is in front of you, before improvising your own process.\n\n## Guardrails and quality checks\n\n- Apply the rules in this skill throughout. Never fabricate facts or numbers, keep external actions draft-only until a human approves them, and state anything you could not verify.\n\n## Worked example\n\nExample request: \"Use the Project Manager skill: [the user describes their situation, inputs and goal].\" Worked output: follow the workflow step by step, produce the output format defined above, run the quality checks, and list any unverified item instead of guessing it.\n","# Project Manager\n\n## Purpose\nKeep the user's many parallel builds (workshops, partnerships, community programs, product experiments, job-hunt threads) organized: one place for every project, its goal, its tasks, and its current state. Own task intake, prioritization, and status reporting. Keep builds running in their own threads — this skill coordinates and reports; it never does unrelated work on the side.\n\nInspired by [finna\u002Fproject-manager-skill](https:\u002F\u002Fgithub.com\u002Ffinna\u002Fproject-manager-skill); rebuilt here in original form for a multi-project builder workflow.\n\n## Tooling\n- CLI: `bin\u002Fpm` (python3 stdlib only). Run as `. \u003Ccmd>`, or add the skill's `bin\u002F` to PATH for the session.\n- Data: one JSON file per project in `.`. Override with `PM_PROJECTS_DIR` (used by tests). Schema in `references\u002Ftask-schema.md`.\n\n## Workflow\n\n### 1. Intake\nWhen the user names a new project or a task, capture it before anything else:\n- `pm init \"Project Name\" --goal \"...\" --deadline YYYY-MM-DD` (creates the project file)\n- `pm task add \u003Cproject> \"Task title\" --priority P0|P1|P2|P3 --due YYYY-MM-DD`\n\n### 2. Prioritize\n- Default every task to P2. P0 = blocked revenue or hard deadline this week; P1 = moves a live deal or event; P3 = nice-to-have.\n- If he gives a deadline, record it. Flag overdue items in status and reviews — never silently drop them.\n- One project may have many tasks; across projects, keep the total P0 count small. If P0s pile up, surface that explicitly.\n\n### 3. Track\n- `pm task start|done|block|unblock \u003Cproject> \u003Ctask-id> --note \"...\"` — move tasks through `todo → doing → done`, with `blocked` as a side state. Notes are timestamped and kept.\n- `pm note \u003Cproject> \"text\" [--task tN]` — decisions, context, anything worth remembering about the project.\n- `pm status \u003Cproject>` — render the markdown status summary (goal, deadline, grouped tasks, recent notes). `--out file.md` writes it to a file.\n\n### 4. Report\n- **Standup:** `pm standup` — done since yesterday, next up, blocked, across all active projects. Good as a morning brief.\n- **Weekly review:** `pm review` — shipped \u002F in-flight \u002F blocked \u002F overdue per project for the trailing 7 days.\n- `pm list` — active projects with done counts; `--status all` or `archived` to see the rest; `pm archive \u003Cproject>` when finished or killed.\n\n## Output Contract\n- `pm status` \u002F `pm standup` \u002F `pm review` print markdown to stdout — reuse it directly in the chat reply or as a document.\n- When reporting to the user: lead with blockers and overdue items, then what's next. Keep it short; he reads bullets, not essays.\n- A status answer never starts new work, sends messages, or spends money. Say so if he asks.\n\n## Operating Rules\n- Project facts live in `.`, never in this skill's directory and never in memory files.\n- Keep `implemented` distinct from `done-and-verified`: a task is `done` only when its outcome is actually confirmed, not when a draft exists.\n- Silence is not approval. If a milestone needs a decision that changes scope, deadline, or money, ask.\n- Killed projects get archived, not deleted — the record stays for the weekly review.\n\n## When to use\n\nUse this skill when the task described in the purpose above is in front of you, before improvising your own process.\n\n## Guardrails and quality checks\n\n- Apply the rules in this skill throughout. Never fabricate facts or numbers, keep external actions draft-only until a human approves them, and state anything you could not verify.\n\n## Worked example\n\nExample request: \"Use the Project Manager skill: [the user describes their situation, inputs and goal].\" Worked output: follow the workflow step by step, produce the output format defined above, run the quality checks, and list any unverified item instead of guessing it.\n",{"name":5,"license":15,"version":44,"category":45,"description":7},"1.0.0","Operations","main","c605eae5729892d78c0b76dfdd58d3533bb26a91","skills\u002Fproject-manager",5,"https:\u002F\u002Fgithub.com\u002Flionelsimai\u002Fclaude-skills-collection","https:\u002F\u002Fgithub.com\u002Flionelsimai","www.theaicapitol.com","Founder at The AI Capitol | I help founders turn AI into 10X revenue through systems, not tools. Ex-Apple • Ex-TikTok 👉 http:\u002F\u002Flionelsim.substack.com","2026-11-09 07:48:48",{"source":8,"skillName":5,"commands":56,"prompt":66,"zipAvailable":67},[57,60,63],{"tool":58,"command":59},"npx","npx skills add lionelsimai\u002Fclaude-skills-collection --skill project-manager",{"tool":61,"command":62},"bunx","bunx skills add lionelsimai\u002Fclaude-skills-collection --skill project-manager",{"tool":64,"command":65},"pnpm","pnpm dlx skills add lionelsimai\u002Fclaude-skills-collection --skill project-manager","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Flionelsimai\u002Fclaude-skills-collection\u002Fblob\u002Fmain\u002Fskills\u002Fproject-manager\u002FSKILL.md",true,[69,75,81],{"path":70,"resourceType":71,"resourceTypeDesc":72,"sizeBytes":73,"sourceHtmlUrl":74},"bin\u002Fpm","OTHER","其他",12322,"https:\u002F\u002Fgithub.com\u002Flionelsimai\u002Fclaude-skills-collection\u002Fblob\u002Fmain\u002Fskills\u002Fproject-manager\u002Fbin\u002Fpm",{"path":76,"resourceType":77,"resourceTypeDesc":78,"sizeBytes":79,"sourceHtmlUrl":80},"references\u002Freview-templates.md","REFERENCE","参考文档",1068,"https:\u002F\u002Fgithub.com\u002Flionelsimai\u002Fclaude-skills-collection\u002Fblob\u002Fmain\u002Fskills\u002Fproject-manager\u002Freferences\u002Freview-templates.md",{"path":82,"resourceType":77,"resourceTypeDesc":78,"sizeBytes":83,"sourceHtmlUrl":84},"references\u002Ftask-schema.md",1062,"https:\u002F\u002Fgithub.com\u002Flionelsimai\u002Fclaude-skills-collection\u002Fblob\u002Fmain\u002Fskills\u002Fproject-manager\u002Freferences\u002Ftask-schema.md",[86,108,121,133,150,164],{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":39},"01M71E7TB5HAR0K6EXB80YXBT7","youth-work-troubleshooting-guide","Diagnose and resolve common problems a youth worker meets in youth centres, schools and outreach settings.\nTRIGGERS - Use when a youth worker needs a troubleshooting & problem solving for young people and their communities in youth centres, schools and outreach settings.","https:\u002F\u002Fgithub.com\u002Flionelsimai\u002Fclaude-skills-collection\u002Fblob\u002Fmain\u002Fskills\u002Fyouth-work-troubleshooting-guide\u002FSKILL.md",[],[93,94,95,96,97,98,35,99,100,101,28,102,29,103,104,105,106,107],"youth work troubleshooting guide","work","troubleshooting","troubleshooting guide","guide","problem solving","outreach","settings","common","people","worker","triggers","diagnose","problem","communities",{"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":15,"licenseFileUrl":6,"sourceHtmlUrl":112,"categories":113,"keywords":114,"publishedAt":39},"01M71E7R3YHK4RAQVCRPB4CTXN","youth-work-tools-equipment-checklist","Select, check and maintain the tools and equipment a youth worker relies on.\nTRIGGERS - Use when a youth worker needs a tools & equipment checklist for young people and their communities in youth centres, schools and outreach settings.","https:\u002F\u002Fgithub.com\u002Flionelsimai\u002Fclaude-skills-collection\u002Fblob\u002Fmain\u002Fskills\u002Fyouth-work-tools-equipment-checklist\u002FSKILL.md",[],[115,94,116,117,28,102,29,118,103,104,119,35,107,120,99,100],"youth work tools equipment checklist","checklist","Tools","maintain","select","check",{"skillNo":122,"name":123,"nameZh":6,"description":124,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":125,"categories":126,"keywords":127,"publishedAt":39},"01M71E7NX1BMFEFBH01KCRJDEP","youth-work-supplies-procurement","Specify, source and manage the supplies and materials used in youth centres, schools and outreach settings.\nTRIGGERS - Use when a youth worker needs a supplies & procurement for young people and their communities in youth centres, schools and outreach settings.","https:\u002F\u002Fgithub.com\u002Flionelsimai\u002Fclaude-skills-collection\u002Fblob\u002Fmain\u002Fskills\u002Fyouth-work-supplies-procurement\u002FSKILL.md",[],[128,129,94,130,131,99,100,102,29,103,104,132,33,35,107,28],"procurement","youth work supplies procurement","materials","source","specify",{"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":15,"licenseFileUrl":6,"sourceHtmlUrl":137,"categories":138,"keywords":144,"publishedAt":39},"01M71E7JVFP6P96GAT2VT9JY0D","youth-work-stakeholder-presentation","Present youth worker findings and proposals to decision-makers and stakeholders.\nTRIGGERS - Use when a youth worker needs a stakeholder presentation for young people and their communities in youth centres, schools and outreach settings.","https:\u002F\u002Fgithub.com\u002Flionelsimai\u002Fclaude-skills-collection\u002Fblob\u002Fmain\u002Fskills\u002Fyouth-work-stakeholder-presentation\u002FSKILL.md",[139],{"categoryNo":140,"categoryName":141,"taxonomyType":142,"taxonomyTypeDesc":143},"01JBSEEDCAT000000000000003","演示文稿","SCENARIO","使用场景",[145,94,146,147,35,148,107,104,149,99,100,28,102,29,103],"youth work stakeholder presentation","presentation","decision","proposals","present",{"skillNo":151,"name":152,"nameZh":6,"description":153,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":154,"categories":155,"keywords":156,"publishedAt":39},"01M71E7GE5VA1RG4XEM2GAZRFY","youth-work-session-delivery","Prepare for and deliver a professional session or appointment for young people and their communities in youth centres, schools and outreach settings.\nTRIGGERS - Use when a youth worker needs a session delivery guide for young people and their communities in youth centres, schools and outreach settings.","https:\u002F\u002Fgithub.com\u002Flionelsimai\u002Fclaude-skills-collection\u002Fblob\u002Fmain\u002Fskills\u002Fyouth-work-session-delivery\u002FSKILL.md",[],[157,158,159,94,160,100,97,161,99,28,102,29,103,104,35,162,163,107],"delivery","work session","session","youth work session delivery","prepare","professional","deliver",{"skillNo":165,"name":166,"nameZh":6,"description":167,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":168,"categories":169,"keywords":173,"publishedAt":39},"01M71E7DQSMY2ZW1BF3A1Z0VJM","youth-work-service-plan","Design a realistic, measurable service plan for young people and their communities as a youth worker.\nTRIGGERS - Use when a youth worker needs a service plan design for young people and their communities in youth centres, schools and outreach settings.","https:\u002F\u002Fgithub.com\u002Flionelsimai\u002Fclaude-skills-collection\u002Fblob\u002Fmain\u002Fskills\u002Fyouth-work-service-plan\u002FSKILL.md",[170],{"categoryNo":171,"categoryName":172,"taxonomyType":142,"taxonomyTypeDesc":143},"01JBSEEDCAT000000000000015","视觉设计",[94,174,23,175,35,104,103,176,177,107,100,99,102,29,28],"service","youth work service plan","design","as"]