[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M75KPJFTYS2VDDN71QS1STWV":3,"skill-same:01M75KPJFTYS2VDDN71QS1STWV":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},"01M75KPJFTYS2VDDN71QS1STWV","writing-fragments",null,"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.","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\u002Fwriting-fragments\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: writing-fragments\ndescription: 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.\n---\n\n\u003Cwhat-to-do>\n\nRun a grilling session that produces fragments. Interview the user relentlessly about whatever they want to write about. Do not impose phases, outlines, or structure — that is explicitly out of scope.\n\nAs fragments emerge from either side of the conversation, append them to a single markdown file. The user will be editing this file during the session; always re-read it before writing so their edits are preserved.\n\nIf the user did not pass a path, ask once where to save the document, then remember it for the rest of the session.\n\nOn first write, put a single H1 at the top with a working title (it can change later) and nothing else — no metadata, no TOC, no date.\n\n\u003C\u002Fwhat-to-do>\n\n\u003Csupporting-info>\n\n## What is a fragment\n\nA fragment is any piece of text that might survive into the final article. It must be _readable by the author_ — the author can tell what it means — but it does not need to define its terms or be comprehensible to a cold reader. The bar is \"is this a piece of good writing?\", not \"is this a self-contained argument?\"\n\nFragments are deliberately heterogeneous. Examples of what could be a fragment:\n\n- A sharp sentence you'd want to deploy somewhere but don't yet know where.\n- A claim with a one-line justification.\n- A vignette: a thing that happened, a code snippet, a scenario, an analogy.\n- A half-thought: \"something about how X feels like Y, work this out later.\"\n- A quote, a piece of dialogue, an overheard line.\n- A list of related observations that hang together by feel.\n- A complaint, a confession, a punchline.\n\nThe novelist's diary is the model: years of unstructured noticings that later get mined for raw material. Fragments are noticings.\n\n## How the session feels\n\nLike a grilling session, with fragments as a by-product. The shape:\n\n- Start by asking what the user is circling around. Let them ramble.\n- Catch fragments from their words. When they say something quotable, capture it verbatim or slightly sharpened.\n- Generate candidate fragments back at them. Try things on. Offer two or three versions of the same idea and let them pick or reject.\n- When something lands, append it. When it doesn't, drop it.\n- Press for more. Excavate. \"You said X — say it three different ways.\" \"What's the version of that you wouldn't say in public?\" \"What's the example that made you believe this in the first place?\"\n- Push on quality. The article will only be as good as its fragments. If a fragment is mushy, propose a sharper rewrite before appending.\n\nBlue-sky generously, but apply pressure to deepen and tighten. Do not rush to outline. Do not group. Do not propose a structure. If the user starts asking about structure, redirect: \"We're still mining. Structure comes later.\"\n\n## File format\n\n```markdown\n# Working title\n\nA first fragment lives here.\n\nIt can be multiple paragraphs. It can include lists, code, quotes — whatever\nshape the fragment naturally takes.\n\n---\n\nA second fragment.\n\n---\n\n> A quoted line that the user wants to keep around.\n\nA reaction to it.\n\n---\n\n- A cluster of related observations\n- That hang together by feel\n- And want to be near each other\n```\n\nFragments are separated by a horizontal rule (`\\n---\\n`). No headings inside the body. No tags. No order beyond the order they were added.\n\n## Writing rhythm\n\nAppend silently. Don't ask permission for each fragment. Mention what you added in passing (\"adding that\"), but don't interrupt the conversation with save dialogs.\n\nBefore every write: re-read the file from disk. The user may have edited, reordered, or deleted fragments between turns — preserve their changes. Never overwrite the file; only append (or, if the user asks, edit a specific fragment in place).\n\nThe user can say \"cut the last one\", \"rewrite that one sharper\", \"merge those two\" at any time. Treat those as first-class instructions.\n\n## Out of scope\n\n- Outlines, section plans, paragraph structure, transitions.\n- Deciding the article's thesis, argument, or audience.\n- Producing prose that reads as finished writing.\n- Linking fragments together with connective tissue.\n\nIf the user is ready for any of that, the session is over and a different tool takes over. Do not name or recommend that tool — just stop.\n\n\u003C\u002Fsupporting-info>\n","\u003Cwhat-to-do>\n\nRun a grilling session that produces fragments. Interview the user relentlessly about whatever they want to write about. Do not impose phases, outlines, or structure — that is explicitly out of scope.\n\nAs fragments emerge from either side of the conversation, append them to a single markdown file. The user will be editing this file during the session; always re-read it before writing so their edits are preserved.\n\nIf the user did not pass a path, ask once where to save the document, then remember it for the rest of the session.\n\nOn first write, put a single H1 at the top with a working title (it can change later) and nothing else — no metadata, no TOC, no date.\n\n\u003C\u002Fwhat-to-do>\n\n\u003Csupporting-info>\n\n## What is a fragment\n\nA fragment is any piece of text that might survive into the final article. It must be _readable by the author_ — the author can tell what it means — but it does not need to define its terms or be comprehensible to a cold reader. The bar is \"is this a piece of good writing?\", not \"is this a self-contained argument?\"\n\nFragments are deliberately heterogeneous. Examples of what could be a fragment:\n\n- A sharp sentence you'd want to deploy somewhere but don't yet know where.\n- A claim with a one-line justification.\n- A vignette: a thing that happened, a code snippet, a scenario, an analogy.\n- A half-thought: \"something about how X feels like Y, work this out later.\"\n- A quote, a piece of dialogue, an overheard line.\n- A list of related observations that hang together by feel.\n- A complaint, a confession, a punchline.\n\nThe novelist's diary is the model: years of unstructured noticings that later get mined for raw material. Fragments are noticings.\n\n## How the session feels\n\nLike a grilling session, with fragments as a by-product. The shape:\n\n- Start by asking what the user is circling around. Let them ramble.\n- Catch fragments from their words. When they say something quotable, capture it verbatim or slightly sharpened.\n- Generate candidate fragments back at them. Try things on. Offer two or three versions of the same idea and let them pick or reject.\n- When something lands, append it. When it doesn't, drop it.\n- Press for more. Excavate. \"You said X — say it three different ways.\" \"What's the version of that you wouldn't say in public?\" \"What's the example that made you believe this in the first place?\"\n- Push on quality. The article will only be as good as its fragments. If a fragment is mushy, propose a sharper rewrite before appending.\n\nBlue-sky generously, but apply pressure to deepen and tighten. Do not rush to outline. Do not group. Do not propose a structure. If the user starts asking about structure, redirect: \"We're still mining. Structure comes later.\"\n\n## File format\n\n```markdown\n# Working title\n\nA first fragment lives here.\n\nIt can be multiple paragraphs. It can include lists, code, quotes — whatever\nshape the fragment naturally takes.\n\n---\n\nA second fragment.\n\n---\n\n> A quoted line that the user wants to keep around.\n\nA reaction to it.\n\n---\n\n- A cluster of related observations\n- That hang together by feel\n- And want to be near each other\n```\n\nFragments are separated by a horizontal rule (`\\n---\\n`). No headings inside the body. No tags. No order beyond the order they were added.\n\n## Writing rhythm\n\nAppend silently. Don't ask permission for each fragment. Mention what you added in passing (\"adding that\"), but don't interrupt the conversation with save dialogs.\n\nBefore every write: re-read the file from disk. The user may have edited, reordered, or deleted fragments between turns — preserve their changes. Never overwrite the file; only append (or, if the user asks, edit a specific fragment in place).\n\nThe user can say \"cut the last one\", \"rewrite that one sharper\", \"merge those two\" at any time. Treat those as first-class instructions.\n\n## Out of scope\n\n- Outlines, section plans, paragraph structure, transitions.\n- Deciding the article's thesis, argument, or audience.\n- Producing prose that reads as finished writing.\n- Linking fragments together with connective tissue.\n\nIf the user is ready for any of that, the session is over and a different tool takes over. Do not name or recommend that tool — just stop.\n\n\u003C\u002Fsupporting-info>\n",{"name":5,"description":7},"main","f37de8f681f0c0ca0e0ebab6e5fddf764ca7553d","skills\u002Fwriting-fragments",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 writing-fragments",{"tool":38,"command":39},"bunx","bunx skills add agisota\u002Fold-one --skill writing-fragments",{"tool":41,"command":42},"pnpm","pnpm dlx skills add agisota\u002Fold-one --skill writing-fragments","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fwriting-fragments\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",[],[]]