[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6R94PYA9SSJ1S0X2QQQFHW2":3,"skill-same:01M6R94PYA9SSJ1S0X2QQQFHW2":55},{"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":27,"linkOnly":28,"markdownContent":29,"markdownBody":30,"frontMatter":31,"refName":33,"commitSha":34,"skillDirectory":35,"forksCount":36,"repositoryHtmlUrl":37,"repositoryHomepageUrl":6,"ownerHtmlUrl":38,"ownerBlogUrl":39,"ownerDescription":40,"updatedAt":41,"install":42,"resources":54},"01M6R94PYA9SSJ1S0X2QQQFHW2","ask-matt",null,"Ask which skill or flow fits your situation. A router over the user-invoked skills in this repo.","Nairon-AI\u002Fagentic-starter-pack","Nairon-AI","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F260662138?v=4","01M6R8PZ1Y8CSQGFN61VACZGTH","Nairon AI","01M6R8PZ6184VR3BA88YZFBC3N",4,"MIT","https:\u002F\u002Fgithub.com\u002FNairon-AI\u002Fagentic-starter-pack\u002Fblob\u002Fmain\u002Fengineering\u002Fask-matt\u002FSKILL.md",[],[19,20,21,22,23,24,25,26],"ask matt","ask","flow","repo","user","router","true","which","2026-11-10 10:12:30",false,"---\nname: ask-matt\ndescription: Ask which skill or flow fits your situation. A router over the user-invoked skills in this repo.\ndisable-model-invocation: true\n---\n\n# Ask Matt\n\nYou don't remember every skill, so ask.\n\nA **flow** is a path through the skills. Most paths run along one **main flow**, and two **on-ramps** merge onto it. Everything else is standalone.\n\n## The main flow: idea → ship\n\nThe route most work travels. You have an idea and want it built.\n\n1. **`\u002Fgrill-me`** — sharpen the idea by interview. It inspects code and maintains canonical plans, `CONTEXT.md`, and ADRs when a repository is present; otherwise it keeps a standalone decision log.\n2. **Branch — can you settle every question in conversation?** If a question needs a runnable answer (state, business logic, a UI you have to see), detour through a prototype, bridged by **`\u002Fhandoff`** in both directions (see Crossing sessions):\n   - **`\u002Fhandoff`** out, then open a fresh session against that file,\n   - **`\u002Fprototype`** to answer the question with throwaway code,\n   - **`\u002Fhandoff`** back what you learned, and reference it from the original idea thread.\n3. **Branch — is this a multi-session build?**\n   - **Yes** → **`\u002Fto-prd`** (turn the thread into a PRD) → **`\u002Fto-issues`** (split the PRD into independently-grabbable issues). Because the issues are independent, **clear context between each one**: start a fresh session per issue and kick off **`\u002Fimplement`** by passing it the PRD and the single issue to work on.\n   - **No** → **`\u002Fimplement`** right here, in the same context window.\n\n### Context hygiene\n\nKeep steps 1–3 in **one unbroken context window** — don't compact or clear until after `\u002Fto-issues` — so the grilling, PRD, and issues all build on the same thinking. Each `\u002Fimplement` then starts fresh, working from the issue.\n\nThe limit on this is the **[smart zone](https:\u002F\u002Fwww.aihero.dev\u002Fai-coding-dictionary\u002Fsmart-zone)**: the window (~120k tokens on state-of-the-art models) within which the model still reasons sharply. If a session approaches it before `\u002Fto-issues`, don't push on degraded — `\u002Fhandoff` and continue in a fresh thread.\n\n## On-ramps\n\nA starting situation that generates work, then merges onto the main flow.\n\n- **Bugs and requests piling up** → **`\u002Ftriage`**. It moves issues through triage roles and produces agent-ready issues, which **`\u002Fimplement`** later picks up.\n\n  Triage is only for issues **you didn't create** — bug reports, incoming feature requests, anything that arrives raw. Issues that `\u002Fto-issues` produced are already agent-ready, so **don't triage them**.\n\n## Codebase health\n\nNot feature work — upkeep.\n\n- **`\u002Fimprove-codebase-architecture`** — run whenever you have a spare moment to keep the codebase good for agents to operate in. It surfaces deepening opportunities; picking one _generates an idea_ you can take into the main flow at `\u002Fgrill-me`.\n\n## Crossing sessions\n\n- **`\u002Fhandoff`** — when a thread is full or you need to branch off (e.g. into a `\u002Fprototype` session), this compacts the conversation into a markdown file. You don't continue in place — you **open a new session and reference that file** to carry the context across. It's the bridge between context windows, in either direction. Use it when you want a **fresh session** but need the **current conversation preserved**.\n- **`\u002Fcompact`** (built-in) — stay in the **same conversation**, letting the earlier turns be summarized. Use it at **intentional breaks between phases**, when you don't mind losing the verbatim history. Don't compact mid-phase — the agent can lose its way. `\u002Fhandoff` forks; `\u002Fcompact` continues.\n\n## Standalone\n\nOff the main flow entirely.\n\n- **`\u002Fteach`** — learn a concept over multiple sessions, using the current directory as a stateful workspace.\n- **`\u002Fwriting-great-skills`** — reference for writing and editing skills well.\n\n## Precondition\n\n**`\u002Fsetup-matt-pocock-skills`** — run before your first engineering flow to configure the issue tracker, triage labels, and doc layout the other skills assume. Custom issue trackers also work.\n","# Ask Matt\n\nYou don't remember every skill, so ask.\n\nA **flow** is a path through the skills. Most paths run along one **main flow**, and two **on-ramps** merge onto it. Everything else is standalone.\n\n## The main flow: idea → ship\n\nThe route most work travels. You have an idea and want it built.\n\n1. **`\u002Fgrill-me`** — sharpen the idea by interview. It inspects code and maintains canonical plans, `CONTEXT.md`, and ADRs when a repository is present; otherwise it keeps a standalone decision log.\n2. **Branch — can you settle every question in conversation?** If a question needs a runnable answer (state, business logic, a UI you have to see), detour through a prototype, bridged by **`\u002Fhandoff`** in both directions (see Crossing sessions):\n   - **`\u002Fhandoff`** out, then open a fresh session against that file,\n   - **`\u002Fprototype`** to answer the question with throwaway code,\n   - **`\u002Fhandoff`** back what you learned, and reference it from the original idea thread.\n3. **Branch — is this a multi-session build?**\n   - **Yes** → **`\u002Fto-prd`** (turn the thread into a PRD) → **`\u002Fto-issues`** (split the PRD into independently-grabbable issues). Because the issues are independent, **clear context between each one**: start a fresh session per issue and kick off **`\u002Fimplement`** by passing it the PRD and the single issue to work on.\n   - **No** → **`\u002Fimplement`** right here, in the same context window.\n\n### Context hygiene\n\nKeep steps 1–3 in **one unbroken context window** — don't compact or clear until after `\u002Fto-issues` — so the grilling, PRD, and issues all build on the same thinking. Each `\u002Fimplement` then starts fresh, working from the issue.\n\nThe limit on this is the **[smart zone](https:\u002F\u002Fwww.aihero.dev\u002Fai-coding-dictionary\u002Fsmart-zone)**: the window (~120k tokens on state-of-the-art models) within which the model still reasons sharply. If a session approaches it before `\u002Fto-issues`, don't push on degraded — `\u002Fhandoff` and continue in a fresh thread.\n\n## On-ramps\n\nA starting situation that generates work, then merges onto the main flow.\n\n- **Bugs and requests piling up** → **`\u002Ftriage`**. It moves issues through triage roles and produces agent-ready issues, which **`\u002Fimplement`** later picks up.\n\n  Triage is only for issues **you didn't create** — bug reports, incoming feature requests, anything that arrives raw. Issues that `\u002Fto-issues` produced are already agent-ready, so **don't triage them**.\n\n## Codebase health\n\nNot feature work — upkeep.\n\n- **`\u002Fimprove-codebase-architecture`** — run whenever you have a spare moment to keep the codebase good for agents to operate in. It surfaces deepening opportunities; picking one _generates an idea_ you can take into the main flow at `\u002Fgrill-me`.\n\n## Crossing sessions\n\n- **`\u002Fhandoff`** — when a thread is full or you need to branch off (e.g. into a `\u002Fprototype` session), this compacts the conversation into a markdown file. You don't continue in place — you **open a new session and reference that file** to carry the context across. It's the bridge between context windows, in either direction. Use it when you want a **fresh session** but need the **current conversation preserved**.\n- **`\u002Fcompact`** (built-in) — stay in the **same conversation**, letting the earlier turns be summarized. Use it at **intentional breaks between phases**, when you don't mind losing the verbatim history. Don't compact mid-phase — the agent can lose its way. `\u002Fhandoff` forks; `\u002Fcompact` continues.\n\n## Standalone\n\nOff the main flow entirely.\n\n- **`\u002Fteach`** — learn a concept over multiple sessions, using the current directory as a stateful workspace.\n- **`\u002Fwriting-great-skills`** — reference for writing and editing skills well.\n\n## Precondition\n\n**`\u002Fsetup-matt-pocock-skills`** — run before your first engineering flow to configure the issue tracker, triage labels, and doc layout the other skills assume. Custom issue trackers also work.\n",{"name":5,"description":7,"disable-model-invocation":32},true,"main","c9d0c408715983e993b2f9ebffdbfa7f10153bcb","engineering\u002Fask-matt",0,"https:\u002F\u002Fgithub.com\u002FNairon-AI\u002Fagentic-starter-pack","https:\u002F\u002Fgithub.com\u002FNairon-AI","https:\u002F\u002Fwww.naironai.com\u002F","Building the future of Work","2026-09-20 17:40:05",{"source":8,"skillName":5,"commands":43,"prompt":53,"zipAvailable":32},[44,47,50],{"tool":45,"command":46},"npx","npx skills add Nairon-AI\u002Fagentic-starter-pack --skill ask-matt",{"tool":48,"command":49},"bunx","bunx skills add Nairon-AI\u002Fagentic-starter-pack --skill ask-matt",{"tool":51,"command":52},"pnpm","pnpm dlx skills add Nairon-AI\u002Fagentic-starter-pack --skill ask-matt","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FNairon-AI\u002Fagentic-starter-pack\u002Fblob\u002Fmain\u002Fengineering\u002Fask-matt\u002FSKILL.md",[],[56,93,114,135,155,177],{"skillNo":57,"name":58,"nameZh":6,"description":59,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":60,"categories":61,"keywords":72,"publishedAt":27},"01M6RBCG630Y8X99XWR9Q4GYNY","writing-shape","Take a markdown file of raw material and shape it into an article through a conversational session — drafting candidate openings, growing the piece paragraph by paragraph, arguing about format (lists, tables, callouts, quotes) at each step. Use when the user has a pile of notes, fragments, or a rough draft and wants help turning it into something publishable.","https:\u002F\u002Fgithub.com\u002FNairon-AI\u002Fagentic-starter-pack\u002Fblob\u002Fmain\u002Fwriting\u002Fwriting-shape\u002FSKILL.md",[62,67],{"categoryNo":63,"categoryName":64,"taxonomyType":65,"taxonomyTypeDesc":66},"01JBSEEDCAT000000000000018","写作与文案","SCENARIO","使用场景",{"categoryNo":68,"categoryName":69,"taxonomyType":70,"taxonomyTypeDesc":71},"01JBSEEDCAT000000000000036","内容创作者","PROFESSION","适用职业",[73,74,75,76,77,78,79,80,81,82,83,84,85,86,87,88,89,90,91,92],"writing","writing shape","shape","notes","help","file","markdown","format","session","use","take","draft","article","material","it","about","quotes","at","candidate","when",{"skillNo":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":97,"categories":98,"keywords":101,"publishedAt":27},"01M6RBCCCB1KMF01P5SYGFWBSW","writing-fragments","Grilling session that mines the user for fragments — heterogeneous nuggets of writing (claims, vignettes, sharp sentences, half-thoughts) — and appends them to a single document as raw material for a future article. Use when the user wants to develop ideas before imposing structure, or mentions \"fragments\", \"ideate\", or \"raw material\" for writing.","https:\u002F\u002Fgithub.com\u002FNairon-AI\u002Fagentic-starter-pack\u002Fblob\u002Fmain\u002Fwriting\u002Fwriting-fragments\u002FSKILL.md",[99,100],{"categoryNo":63,"categoryName":64,"taxonomyType":65,"taxonomyTypeDesc":66},{"categoryNo":68,"categoryName":69,"taxonomyType":70,"taxonomyTypeDesc":71},[73,102,103,104,105,23,81,82,106,107,108,85,109,86,110,111,112,113,92],"writing fragments","grilling","ideate","develop","document","structure","ideas","as","sharp","claims","for","single",{"skillNo":115,"name":116,"nameZh":6,"description":117,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":118,"categories":119,"keywords":122,"publishedAt":27},"01M6RBC8V7NHHKMTAZB4BPXVYQ","writing-beats","Shape an article as a journey of beats, choose-your-own-adventure style. The user picks a starting beat from the raw material, you write only that beat, then offer options for where to pivot next, beat by beat, until the article reaches a natural end. Use when the user has raw material and wants to assemble it as a narrative rather than an argument.","https:\u002F\u002Fgithub.com\u002FNairon-AI\u002Fagentic-starter-pack\u002Fblob\u002Fmain\u002Fwriting\u002Fwriting-beats\u002FSKILL.md",[120,121],{"categoryNo":63,"categoryName":64,"taxonomyType":65,"taxonomyTypeDesc":66},{"categoryNo":68,"categoryName":69,"taxonomyType":70,"taxonomyTypeDesc":71},[73,123,124,125,82,126,127,75,128,129,130,85,131,109,132,86,133,134,112,92],"writing beats","choose","write","assemble","only","journey","next","options","end","style","narrative","argument",{"skillNo":136,"name":137,"nameZh":6,"description":138,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":139,"categories":140,"keywords":143,"publishedAt":27},"01M6RBC58SG5Y5SC4ZV4ZNEFHC","stop-slop","Remove AI writing patterns from prose. Use when drafting, editing, or reviewing text to eliminate predictable AI tells.","https:\u002F\u002Fgithub.com\u002FNairon-AI\u002Fagentic-starter-pack\u002Fblob\u002Fmain\u002Fwriting\u002Fstop-slop\u002FSKILL.md",[141,142],{"categoryNo":63,"categoryName":64,"taxonomyType":65,"taxonomyTypeDesc":66},{"categoryNo":68,"categoryName":69,"taxonomyType":70,"taxonomyTypeDesc":71},[144,145,146,73,147,148,149,150,151,82,152,153,154,112,92],"stop","stop slop","slop","content","https","text","editing","remove","prose","patterns","drafts",{"skillNo":156,"name":157,"nameZh":6,"description":158,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":159,"categories":160,"keywords":163,"publishedAt":27},"01M6RBBJTTCJ7KZCP16G9JDFZH","humanizer","Remove signs of AI-generated writing from text. Use when editing or reviewing\ntext to make it sound more natural and human-written. Based on Wikipedia's\ncomprehensive \"Signs of AI writing\" guide. Detects and fixes patterns including:\ninflated symbolism, promotional language, superficial -ing analyses, vague\nattributions, em dash overuse, rule of three, AI vocabulary words, passive\nvoice, negative parallelisms, and filler phrases.","https:\u002F\u002Fgithub.com\u002FNairon-AI\u002Fagentic-starter-pack\u002Fblob\u002Fmain\u002Fwriting\u002Fhumanizer\u002FSKILL.md",[161,162],{"categoryNo":63,"categoryName":64,"taxonomyType":65,"taxonomyTypeDesc":66},{"categoryNo":68,"categoryName":69,"taxonomyType":70,"taxonomyTypeDesc":71},[157,73,164,165,149,166,125,167,168,151,169,170,153,171,172,173,174,175,176,92],"code","em dash","read","edit","generated","guide","opencode","three","human","make","wikipedia","vague","dash",{"skillNo":178,"name":179,"nameZh":6,"description":180,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":181,"categories":182,"keywords":183,"publishedAt":27},"01M6RBBEQKJ5HRH8AV9J85QB1T","feedback","Prepare, deliver, and debrief timely interpersonal feedback using a question-first coaching flow, observable behavior, owned experience, and concrete impact. Use when drafting feedback, coaching managers, rehearsing a feedback conversation, praising specific behavior, or reviewing whether feedback landed.","https:\u002F\u002Fgithub.com\u002FNairon-AI\u002Fagentic-starter-pack\u002Fblob\u002Fmain\u002Fwriting\u002Ffeedback\u002FSKILL.md",[],[179,184,21,185,186,187,82,188,189,190,191,192,92,193],"prepare","first","question","behavior","conversation","coaching","debrief","impact","managers","deliver"]