[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M75EWMFVCVR9QY42H28NFNQJ":3,"skill-same:01M75EWMFVCVR9QY42H28NFNQJ":46},{"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":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":23,"commitSha":24,"skillDirectory":25,"forksCount":26,"repositoryHtmlUrl":27,"repositoryHomepageUrl":28,"ownerHtmlUrl":29,"ownerBlogUrl":30,"ownerDescription":6,"updatedAt":31,"install":32,"resources":45},"01M75EWMFVCVR9QY42H28NFNQJ","kickoff-doc",null,"Turn a shaped project kickoff transcript into a reference document for the builder. Use when the user has a transcript (VTT, etc.) from a kickoff call and wants to produce a document that captures what was shaped and agreed.","agisota\u002Fold-one","agisota","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F121413592?v=4","01M75B4BRNT67EC1NDRT8QZEP2","01M75B4BS7QR9VP580MSCPTS3X",3,"MIT","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fkickoff-doc\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: kickoff-doc\ndescription: Turn a shaped project kickoff transcript into a reference document for the builder. Use when the user has a transcript (VTT, etc.) from a kickoff call and wants to produce a document that captures what was shaped and agreed.\n---\n\n# Kickoff Document from Transcript\n\nTurn a kickoff call transcript into a builder-facing reference document for a shaped project.\n\n---\n\n## Before You Start\n\nAsk the user:\n\n1. **Who is the primary audience?** (Usually the builder who will implement the work.)\n2. **What other inputs are there?** (Visuals, screenshots, mockups, breadboards from the session.)\n\nThe transcript is your source material. The document is NOT a summary of the call — it's a **map of the territory** that was shaped.\n\n---\n\n## Organizing Principle: Territory, Not Timeline\n\nA kickoff transcript is sequential — people talk through things in the order they come up, circle back, go on tangents, get sidetracked by browser issues. Your job is to reconstruct the **territory they were describing**, not replay the conversation.\n\n**Organize by the thing being built.** Each section should describe one area of the system fully — so the builder can look up \"how does the Criteria tab work?\" and find everything in one place.\n\n**Do NOT organize by build sequence.** If the team identified slices (a sequence of vertical slices to build in order), those are managed separately — not in this document.\n\n---\n\n## Structure\n\nThe document has two top-level sections: **Frame** and **Shape**. Both are `##` headings. Their subsections are `###`.\n\n### 1. Frame (`## Frame`)\n\nThe strategic context and boundary conditions. This is NOT fluff — the builder needs this to make judgment calls when they hit ambiguity.\n\n- `### Problem` — Why this project, why now. What's broken or missing.\n- `### Outcome` — The specific outcomes expected. What success looks like.\n\n### 2. Shape (`## Shape`)\n\nOne `###` section per area of the system. For each area, describe:\n\n- What it is and what's on the screen (affordances, components, data displayed)\n- How it relates to other areas\n- Design decisions that belong to THIS area — inline, not in a separate section\n- Edge cases or flags that were called out\n- What's temporary\u002Fplaceholder vs. what's a real commitment\n\n**Do NOT include a Build Sequence section.** Slices are tracked separately from this document.\n\n---\n\n## Voice: Use Their Words\n\nThe document is a record of shared understanding from the kickoff call.\n\n### Do\n\n- Use the actual words and phrases people used on the call\n- Synthesize scattered discussion into clearer form (taking something said across several turns and stating it cleanly)\n- Capture the reasoning people gave for decisions (\"we're doing X because Y\")\n\n### Don't\n\n- Put new ideas or conclusions in people's mouths\n- Add motivational framing they didn't express (\"each piece is a foundation, not a throwaway\")\n- Editorialize about importance or quality beyond what was said\n\n### The Test\n\nFor every sentence, you should be able to point to a moment in the transcript where someone said it or clearly meant it. If you can't, either cut it or flag it as your own synthesis.\n\n**Exception:** Editorializing that clarifies or synthesizes what was said IS fine. \"The criteria screen is how filtering is expressed in the new world\" — nobody said that exact sentence, but it accurately captures a point made across several turns. That's the job: make scattered discussion legible without adding your own conclusions.\n\n---\n\n## Design Decisions: Vertical, Not Horizontal\n\nDo NOT create a grab-bag \"Design Decisions\" section. Instead, put each decision inline in the section where it matters.\n\n- \"Matches stored in DB not Redis\" → goes in the section about matching\n- \"Candidates must be materialized before attachment\" → goes in the section about attaching\n- \"Per-ICP match data as value objects\" → goes in the section about match results\n\nIf a decision only matters when building one specific area, it belongs in that area's section. The builder shouldn't have to cross-reference a separate decisions list while working on a specific screen.\n\n---\n\n## Process\n\n1. **Read the full transcript.** Don't start writing after reading part of it.\n2. **Identify the areas of the system** that were discussed — these become your `###` sections under `## Shape`.\n3. **Draft the Frame** (`## Frame` with `### Problem` and `### Outcome`) from the framing\u002Foutcomes discussion (usually near the start of the call).\n4. **Write each Shape section** (`### ...`), pulling from wherever in the transcript that area was discussed. A single section may draw from moments scattered across the whole call.\n5. **Place design decisions inline** in the section they belong to.\n6. **Review against the transcript** — can you point to where each claim was said?\n","# Kickoff Document from Transcript\n\nTurn a kickoff call transcript into a builder-facing reference document for a shaped project.\n\n---\n\n## Before You Start\n\nAsk the user:\n\n1. **Who is the primary audience?** (Usually the builder who will implement the work.)\n2. **What other inputs are there?** (Visuals, screenshots, mockups, breadboards from the session.)\n\nThe transcript is your source material. The document is NOT a summary of the call — it's a **map of the territory** that was shaped.\n\n---\n\n## Organizing Principle: Territory, Not Timeline\n\nA kickoff transcript is sequential — people talk through things in the order they come up, circle back, go on tangents, get sidetracked by browser issues. Your job is to reconstruct the **territory they were describing**, not replay the conversation.\n\n**Organize by the thing being built.** Each section should describe one area of the system fully — so the builder can look up \"how does the Criteria tab work?\" and find everything in one place.\n\n**Do NOT organize by build sequence.** If the team identified slices (a sequence of vertical slices to build in order), those are managed separately — not in this document.\n\n---\n\n## Structure\n\nThe document has two top-level sections: **Frame** and **Shape**. Both are `##` headings. Their subsections are `###`.\n\n### 1. Frame (`## Frame`)\n\nThe strategic context and boundary conditions. This is NOT fluff — the builder needs this to make judgment calls when they hit ambiguity.\n\n- `### Problem` — Why this project, why now. What's broken or missing.\n- `### Outcome` — The specific outcomes expected. What success looks like.\n\n### 2. Shape (`## Shape`)\n\nOne `###` section per area of the system. For each area, describe:\n\n- What it is and what's on the screen (affordances, components, data displayed)\n- How it relates to other areas\n- Design decisions that belong to THIS area — inline, not in a separate section\n- Edge cases or flags that were called out\n- What's temporary\u002Fplaceholder vs. what's a real commitment\n\n**Do NOT include a Build Sequence section.** Slices are tracked separately from this document.\n\n---\n\n## Voice: Use Their Words\n\nThe document is a record of shared understanding from the kickoff call.\n\n### Do\n\n- Use the actual words and phrases people used on the call\n- Synthesize scattered discussion into clearer form (taking something said across several turns and stating it cleanly)\n- Capture the reasoning people gave for decisions (\"we're doing X because Y\")\n\n### Don't\n\n- Put new ideas or conclusions in people's mouths\n- Add motivational framing they didn't express (\"each piece is a foundation, not a throwaway\")\n- Editorialize about importance or quality beyond what was said\n\n### The Test\n\nFor every sentence, you should be able to point to a moment in the transcript where someone said it or clearly meant it. If you can't, either cut it or flag it as your own synthesis.\n\n**Exception:** Editorializing that clarifies or synthesizes what was said IS fine. \"The criteria screen is how filtering is expressed in the new world\" — nobody said that exact sentence, but it accurately captures a point made across several turns. That's the job: make scattered discussion legible without adding your own conclusions.\n\n---\n\n## Design Decisions: Vertical, Not Horizontal\n\nDo NOT create a grab-bag \"Design Decisions\" section. Instead, put each decision inline in the section where it matters.\n\n- \"Matches stored in DB not Redis\" → goes in the section about matching\n- \"Candidates must be materialized before attachment\" → goes in the section about attaching\n- \"Per-ICP match data as value objects\" → goes in the section about match results\n\nIf a decision only matters when building one specific area, it belongs in that area's section. The builder shouldn't have to cross-reference a separate decisions list while working on a specific screen.\n\n---\n\n## Process\n\n1. **Read the full transcript.** Don't start writing after reading part of it.\n2. **Identify the areas of the system** that were discussed — these become your `###` sections under `## Shape`.\n3. **Draft the Frame** (`## Frame` with `### Problem` and `### Outcome`) from the framing\u002Foutcomes discussion (usually near the start of the call).\n4. **Write each Shape section** (`### ...`), pulling from wherever in the transcript that area was discussed. A single section may draw from moments scattered across the whole call.\n5. **Place design decisions inline** in the section they belong to.\n6. **Review against the transcript** — can you point to where each claim was said?\n",{"name":5,"description":7},"main","f37de8f681f0c0ca0e0ebab6e5fddf764ca7553d","skills\u002Fkickoff-doc",1,"https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one","https:\u002F\u002Fagisota.github.io\u002Fold-one\u002F","https:\u002F\u002Fgithub.com\u002Fagisota","pzd.world","2026-07-04 22:32:06",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add agisota\u002Fold-one --skill kickoff-doc",{"tool":38,"command":39},"bunx","bunx skills add agisota\u002Fold-one --skill kickoff-doc",{"tool":41,"command":42},"pnpm","pnpm dlx skills add agisota\u002Fold-one --skill kickoff-doc","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fkickoff-doc\u002FSKILL.md",true,[],[47,54,61,70,77,84],{"skillNo":48,"name":49,"nameZh":6,"description":50,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":51,"categories":52,"keywords":53,"publishedAt":18},"01M75KRGZWQWE9JDBS6RX42NWV","zoom-out","Tell the agent to zoom out and give broader context or a higher-level perspective. Use when you're unfamiliar with a section of code or need to understand how it fits into the bigger picture.","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fzoom-out\u002FSKILL.md",[],[],{"skillNo":55,"name":56,"nameZh":6,"description":57,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":58,"categories":59,"keywords":60,"publishedAt":18},"01M75KRCZHKE0ZYAQFFYHS0YNP","zeroize-audit","Detects missing zeroization of sensitive data in source code and identifies zeroization removed by compiler optimizations, with assembly-level analysis, and control-flow verification. Use for auditing C\u002FC++\u002FRust code handling secrets, keys, passwords, or other sensitive data.","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fzeroize-audit\u002FSKILL.md",[],[],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":65,"licenseFileUrl":66,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":18},"01M75KR94KYQ30DTE1P9WNDAE0","yeet","Use only when the user explicitly asks to stage, commit, push, and open a GitHub pull request in one flow using the GitHub CLI (`gh`).","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fyeet\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fyeet\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":18},"01M75KR3H13YJ9QHMD49818FA1","yara-rule-authoring","Guides authoring of high-quality YARA-X detection rules for malware identification. Use when writing, reviewing, or optimizing YARA rules. Covers naming conventions, string selection, performance optimization, migration from legacy YARA, and false positive reduction. Triggers on: YARA, YARA-X, malware detection, threat hunting, IOC, signature, crx module, dex module.","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fyara-rule-authoring\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":18},"01M75KQMPY8A4Y8XTDD2DT0M9T","x-twitter-growth","X\u002FTwitter growth engine for building audience, crafting viral content, and analyzing engagement. Use when the user wants to grow on X\u002FTwitter, write tweets or threads, analyze their X profile, research competitors on X, plan a posting strategy, or optimize engagement. Complements social-content (generic multi-platform) with X-specific depth: algorithm mechanics, thread engineering, reply strategy, profile optimization, and competitive intelligence via web search.","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fx-twitter-growth\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":18},"01M75KQHNZ0ANZNJGZY6M8MDAK","x-api","X\u002FTwitter API integration for posting tweets, threads, reading timelines, search, and analytics. Covers OAuth auth patterns, rate limits, and platform-native content posting. Use when the user wants to interact with X programmatically.","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fx-api\u002FSKILL.md",[],[]]