[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6CCVDSZXKQG6JB7RMVJ2H11":3,"skill-same:01M6CCVDSZXKQG6JB7RMVJ2H11":145},{"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":34,"publishedAt":55,"linkOnly":56,"markdownContent":57,"markdownBody":58,"frontMatter":59,"refName":60,"commitSha":61,"skillDirectory":62,"forksCount":63,"repositoryHtmlUrl":64,"repositoryHomepageUrl":6,"ownerHtmlUrl":65,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":66,"install":67,"resources":80},"01M6CCVDSZXKQG6JB7RMVJ2H11","writing-studio",null,"Write or review professional, human-facing prose so the result is clear, well-structured, correctly shaped for its document type, and free of AI-sounding filler. Use this skill WHENEVER you are about to write something a person will read (a proposal, email, chat or Slack message, document or wiki page, blog post, announcement, status update, RFC or design doc, release notes, exec brief, incident report, peer performance feedback, RACI or roles-and-responsibilities matrix, program or project poster, PR\u002FFAQ or working-backwards doc) OR when asked to review, improve, polish, critique, proofread, tighten, sharpen, or shorten any existing text. Prefer it over ad-hoc style fixes, especially for multi-paragraph or long-form writing. Do NOT use it for code, code comments, commit messages, machine-readable data (JSON\u002FYAML\u002FCSV), or trivial one-line replies.","aminfara\u002Fdotfiles","aminfara","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F9583722?v=4","01M6CCSBYF8CKS4GQNN5D00V1A","Ali Aminfar","01M6CCSC2TC2ZEYPEXXW64FEPN",0,"MIT","https:\u002F\u002Fgithub.com\u002Faminfara\u002Fdotfiles\u002Fblob\u002Fmain\u002Fagents\u002Fskills\u002Fwriting-studio\u002FSKILL.md",[18,23,26,29],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000005","邮件与沟通","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000015","视觉设计",{"categoryNo":27,"categoryName":28,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":30,"categoryName":31,"taxonomyType":32,"taxonomyTypeDesc":33},"01JBSEEDCAT000000000000036","内容创作者","PROFESSION","适用职业",[35,36,37,38,39,40,41,42,43,44,45,46,47,48,49,50,51,52,53,54],"writing studio","studio","writing","project","release","read","update","proofread","human","slack","you","free","code comments","critique","notes","text","sharpen","design","improve","incident report","2026-11-10 10:12:30",false,"---\nname: writing-studio\ndescription: Write or review professional, human-facing prose so the result is clear, well-structured, correctly shaped for its document type, and free of AI-sounding filler. Use this skill WHENEVER you are about to write something a person will read (a proposal, email, chat or Slack message, document or wiki page, blog post, announcement, status update, RFC or design doc, release notes, exec brief, incident report, peer performance feedback, RACI or roles-and-responsibilities matrix, program or project poster, PR\u002FFAQ or working-backwards doc) OR when asked to review, improve, polish, critique, proofread, tighten, sharpen, or shorten any existing text. Prefer it over ad-hoc style fixes, especially for multi-paragraph or long-form writing. Do NOT use it for code, code comments, commit messages, machine-readable data (JSON\u002FYAML\u002FCSV), or trivial one-line replies.\n---\n\n# Writing Studio\n\nWrite new prose well, or review existing prose, for any human reader.\n\n## Overview\n\nThis skill helps you do two things: **generate** strong professional writing on the first try, and **review** existing writing and return useful, prioritized feedback. It works for any document a person reads, including proposals, emails, chat messages, documents and wiki pages, blog posts, announcements, status updates, RFCs, release notes, incident reports, and PR\u002FFAQs.\n\nFor any task, you first identify a few things about the writing (its document type, purpose, where it will be read, the tone, and the audience), then apply a shared set of writing rules plus a template for that document type. The rules cover clarity, structure, concision, and honesty, and they include checks that stop the output from sounding machine-written or stating facts that were never given.\n\nA good result in generate mode is a draft that is shaped correctly for its document type, holds the requested tone, invents no facts, and reads like a capable person wrote it. A good result in review mode is a short, prioritized list of findings grouped by impact, each explaining the problem and the fix.\n\n## When to use this skill\n\nLoad this skill whenever you are about to produce, expand, edit, or review prose a person will read. Beyond the document types in the description, this includes:\n\n- Converting notes or an outline into prose, or summarizing a long document.\n- Adjusting writing to a target tone or audience (\"make this more formal\", \"an exec version\").\n- Producing output that other people, not just the requester, will read, even mid-task in a larger job.\n\n### When NOT to use this skill\n\n- Code generation, code comments shorter than a sentence, or commit messages governed by house conventions.\n- Machine-readable data (JSON, YAML, CSV) — there is no human reader to optimize for.\n- One-line acknowledgements (\"done\", \"got it\").\n- Translation\u002Ftranscription where the source style must be preserved verbatim.\n\n## Constraints\n\n- **Preserve the writer's intent and voice.** In review, do not rewrite meaning or flatten a distinctive voice into generic corporate prose. Make the minimum effective edit: fix what is broken and leave strong sentences as the writer wrote them. In generate, match the requested tone; do not impose a house style.\n- **Apply rules with judgment, not as a checklist.** Each universal rule names when it applies and when it does not. Clarity for the actual reader beats conformity. If a rule would hurt this format\u002Ftone\u002Faudience, skip it and (in review) say why.\n- **Never fabricate.** No invented quantification, sources, names, or dates. Name the gap (`[CLARIFY: ...]`) instead. This is enforced by the anti-hallucination pass in `references\u002Funiversal-rules.md` (rule A9).\n- **Honor stated length limits as hard caps.** If content will not fit, ask what to cut rather than overflowing. In review, prioritize and deduplicate findings: group by impact (structure → substance → sentence-level) and report a repeated issue once with examples, not per-paragraph.\n\n## Inputs\n\nBefore drafting or reviewing, resolve these from context. Infer silently when confident; **ask only when a key input is genuinely unclear.**\n\n- **mode** — `generate` (write new text) or `review` (give feedback on existing text). If the user supplies text and says \"improve\", default to `review` and offer a rewrite.\n- **format** — the document type (proposal, email, blog, status update, RFC, ...). This selects the template in `references\u002Fformats\u002F`. If none matches, see Workflow Step 2.\n- **purpose** — inform, persuade\u002Frecommend, announce, request, instruct, report, document a decision, narrate a vision.\n- **medium** — where it will be read: email, chat, wiki page or document, issue tracker, printed page. This sets length and formatting conventions.\n- **tone** — formal, neutral, friendly, persuasive, authoritative, visionary, urgent, or a free-form description (\"warm but direct\"). If unspecified, use the format's default.\n- **audience** — who reads it, what they know, how much attention they will give. This drives tone and vocabulary.\n- **completeness** (only for formats that define levels, e.g. proposal, RACI) — how fully worked-out this should be. The level names are format-specific and listed in that format's base file. Infer from the request: \"shoot a quick note proposing X\" → proposal floater; \"write up a one-pager\" → one-pager; \"write the proposal doc\" → full; \"drop a note in the channel on who owns what\" → RACI prose. Ask if unclear. Formats without levels (e.g. blog post, peer feedback) ignore this.\n\nExample: \"Write an email to the team reporting the launch slip\" resolves cleanly (format=email, purpose=report, medium=email, audience=team) — proceed. \"Write something about X\" does not — ask for format and destination.\n\n## Output\n\n**Generate mode.** Lead with the deliverable itself, starting with its natural title (or no title for a short email\u002Fmessage). Put meta below a `---` divider so a human sees only the prose:\n\n```text\n[the prose]\n\n---\n## Notes (for the agent, not the reader)\n- What you used: format \u002F purpose \u002F medium \u002F tone \u002F audience (inferred or given)\n- Rules relaxed and why (e.g. \"skipped quantify-impact: visionary tone\")\n- Open items: [CLARIFY: ...] for anything unverified\n```\n\n**Review mode.** Use this template:\n\n```text\n## Verdict\nOne or two sentences: is it fit for its format, purpose, audience? Biggest lever to improve it.\n\n## Findings (highest impact first)\n### Structure\n- [issue] -> [why it hurts the reader] -> [suggested fix]\n### Substance\n- ...\n### Sentence-level \u002F style\n- [pattern] (e.g. \"em-dash overuse, 6 instances\") -> [fix], shown once with examples\n\n## Suggested revision (optional)\n[A rewritten version, if wanted or if it is the fastest way to show the fix.]\n```\n\n## Workflow\n\n### Step 1: Resolve the inputs\n\nDetermine the mode and the other inputs (see Inputs). Infer when confident; ask only when a key input is genuinely unclear. In generate mode, when you infer rather than ask, record your read in the *notes* block, not in the deliverable.\n\n### Step 2: Load the rules and the format\n\nAlways read `references\u002Funiversal-rules.md` and `references\u002Fai-patterns.md`. Then load the matching format:\n\n- A simple format is a single file: `references\u002Fformats\u002F\u003Cformat>.md`.\n- A format with **completeness levels** is a folder: load the base `references\u002Fformats\u002F\u003Cformat>\u002F\u003Cformat>.md` plus **exactly one** level file matching the completeness (e.g. `proposal\u002Fproposal-floater.md`). Do not load the other levels.\n\nIf no format matches, say so (\"I don't have a dedicated template for \u003Cformat> yet, so I'm using the universal rules\"), then write with the universal rules and the closest structural pattern. Do not pretend a template exists.\n\n### Step 3: Produce the draft or the review\n\nIn **generate**, write to the format template, apply the tone and medium guidance, and suppress the ai-patterns. In **review**, produce findings with the review template, applying each rule only where it fits this format, tone, and audience.\n\n### Step 4: Run the final passes, then present\n\nRun the **anti-hallucination pass** (universal-rules.md A9): classify each specific factual claim as Verified \u002F Inferred \u002F Unknown, and ask about or strip the Inferred and Unknown ones; never invent facts. Then run the **ai-patterns pass**. Then run the **reader-walk**: read each paragraph as the actual reader, who was not in your research or your context, and rewrite every sentence they could not restate in their own words without opening a link. Keep your analysis, verification tags and method notes in the notes block; the deliverable carries only what the reader needs. Present the output in the shape defined under Output.\n\n## Reference files\n\n- `references\u002Funiversal-rules.md` — always-on rules (incl. the A9 anti-hallucination protocol), conditional rules, and the tone and medium guidance. Read every time.\n- `references\u002Fai-patterns.md` — LLM tells to suppress so text does not read as machine-written. Read every time you draft.\n- `references\u002Fformats\u002F` — per-format templates and rules. Currently supported:\n  - `references\u002Fformats\u002Fproposal\u002F` — internal decision\u002Fstrategy proposal. Load the base (proposal.md) plus exactly one level file: proposal-floater.md, proposal-onepager.md, or proposal-full.md.\n  - `references\u002Fformats\u002Fraci\u002F` — RACI responsibility matrix (Responsible \u002F Accountable \u002F Consulted \u002F Informed). Load the base (raci.md) plus exactly one level file: raci-prose.md for plain text in Slack or email, or raci-onepager.md for the wiki-page artifact. The base carries the *ownership clause*: the mandatory sections that stop a RACI becoming a \"not my job\" shield or a blame map.\n  - `references\u002Fformats\u002Fpeer-feedback.md` — peer performance feedback (Strengths + Opportunities). Single file; no completeness levels. Collects receiver role, optional role expectations, and optional org values before generating or reviewing SBI-structured feedback items.\n  - `references\u002Fformats\u002Fposter.md` — program or project poster: the durable 1-2 page orientation page for work that already exists (what \u002F why and why now \u002F which goal it ladders up to \u002F in and out of scope \u002F tenets). Also answers to program brief, program overview, program profile, and project charter. Single file; two variants (program, project) selected inside it. Carries the *orientation contract* (the six questions a cold reader must answer without opening a link or asking anyone), the *durability rule* (the page holds the definition of the work, never its condition), and the two tenet tests. Every section is mandatory, glossary included, so the page stands alone. Not a proposal, not a status report, and not the pre-decision workshop artifact that shares the name.\n  - `references\u002Fformats\u002Fprfaq.md`: PR\u002FFAQ in the Amazon working-backwards style. It is the launch-day press release for a product not yet built, then a Customer FAQ for the end user (internal or external), an Internal FAQ for the leaders deciding to build it and for the builder team, and visuals of the customer experience: static, simple HTML wireframes first, one per customer benefit, then Mermaid diagrams for journeys and flows. Also answers to PRFAQ, working-backwards doc, and future press release. Single file; no completeness levels. Carries the nine-part press release in AWS's order, a mandatory FAQ core of nine questions plus a menu (around 15 questions), a per-part table of which rules the press release may relax (quotes and wireframe sample content are declared fiction), and length guidelines rather than hard caps: press release 250 to 375 words, press release plus FAQ under about 1,500 words, visuals outside the guide. Not a proposal, and not a real announcement of something already shipped.\n  - `references\u002Fformats\u002Fblog.md` — first-person blog post: the author telling colleagues what they think, why, and what changes. Single file; two variants (direction-setting, perspective) selected inside it. Carries the voice rule (\"I\" for the author's experience, \"we\" for team change), the altitude rule (direction-setting posts state what and why and leave the how to the team), and optional voice samples to match the author's own cadence.\n  - `references\u002Fformats\u002F_TEMPLATE.md` — scaffold for adding a new format (single-file or base+levels).\n\nTo grow the library, copy `_TEMPLATE.md`, fill in the template, default axes, format-specific rules, and which conditional rules to relax, then add a line to the supported list above. Build format-by-format; a small set of well-specified formats beats a large set of thin ones.\n","# Writing Studio\n\nWrite new prose well, or review existing prose, for any human reader.\n\n## Overview\n\nThis skill helps you do two things: **generate** strong professional writing on the first try, and **review** existing writing and return useful, prioritized feedback. It works for any document a person reads, including proposals, emails, chat messages, documents and wiki pages, blog posts, announcements, status updates, RFCs, release notes, incident reports, and PR\u002FFAQs.\n\nFor any task, you first identify a few things about the writing (its document type, purpose, where it will be read, the tone, and the audience), then apply a shared set of writing rules plus a template for that document type. The rules cover clarity, structure, concision, and honesty, and they include checks that stop the output from sounding machine-written or stating facts that were never given.\n\nA good result in generate mode is a draft that is shaped correctly for its document type, holds the requested tone, invents no facts, and reads like a capable person wrote it. A good result in review mode is a short, prioritized list of findings grouped by impact, each explaining the problem and the fix.\n\n## When to use this skill\n\nLoad this skill whenever you are about to produce, expand, edit, or review prose a person will read. Beyond the document types in the description, this includes:\n\n- Converting notes or an outline into prose, or summarizing a long document.\n- Adjusting writing to a target tone or audience (\"make this more formal\", \"an exec version\").\n- Producing output that other people, not just the requester, will read, even mid-task in a larger job.\n\n### When NOT to use this skill\n\n- Code generation, code comments shorter than a sentence, or commit messages governed by house conventions.\n- Machine-readable data (JSON, YAML, CSV) — there is no human reader to optimize for.\n- One-line acknowledgements (\"done\", \"got it\").\n- Translation\u002Ftranscription where the source style must be preserved verbatim.\n\n## Constraints\n\n- **Preserve the writer's intent and voice.** In review, do not rewrite meaning or flatten a distinctive voice into generic corporate prose. Make the minimum effective edit: fix what is broken and leave strong sentences as the writer wrote them. In generate, match the requested tone; do not impose a house style.\n- **Apply rules with judgment, not as a checklist.** Each universal rule names when it applies and when it does not. Clarity for the actual reader beats conformity. If a rule would hurt this format\u002Ftone\u002Faudience, skip it and (in review) say why.\n- **Never fabricate.** No invented quantification, sources, names, or dates. Name the gap (`[CLARIFY: ...]`) instead. This is enforced by the anti-hallucination pass in `references\u002Funiversal-rules.md` (rule A9).\n- **Honor stated length limits as hard caps.** If content will not fit, ask what to cut rather than overflowing. In review, prioritize and deduplicate findings: group by impact (structure → substance → sentence-level) and report a repeated issue once with examples, not per-paragraph.\n\n## Inputs\n\nBefore drafting or reviewing, resolve these from context. Infer silently when confident; **ask only when a key input is genuinely unclear.**\n\n- **mode** — `generate` (write new text) or `review` (give feedback on existing text). If the user supplies text and says \"improve\", default to `review` and offer a rewrite.\n- **format** — the document type (proposal, email, blog, status update, RFC, ...). This selects the template in `references\u002Fformats\u002F`. If none matches, see Workflow Step 2.\n- **purpose** — inform, persuade\u002Frecommend, announce, request, instruct, report, document a decision, narrate a vision.\n- **medium** — where it will be read: email, chat, wiki page or document, issue tracker, printed page. This sets length and formatting conventions.\n- **tone** — formal, neutral, friendly, persuasive, authoritative, visionary, urgent, or a free-form description (\"warm but direct\"). If unspecified, use the format's default.\n- **audience** — who reads it, what they know, how much attention they will give. This drives tone and vocabulary.\n- **completeness** (only for formats that define levels, e.g. proposal, RACI) — how fully worked-out this should be. The level names are format-specific and listed in that format's base file. Infer from the request: \"shoot a quick note proposing X\" → proposal floater; \"write up a one-pager\" → one-pager; \"write the proposal doc\" → full; \"drop a note in the channel on who owns what\" → RACI prose. Ask if unclear. Formats without levels (e.g. blog post, peer feedback) ignore this.\n\nExample: \"Write an email to the team reporting the launch slip\" resolves cleanly (format=email, purpose=report, medium=email, audience=team) — proceed. \"Write something about X\" does not — ask for format and destination.\n\n## Output\n\n**Generate mode.** Lead with the deliverable itself, starting with its natural title (or no title for a short email\u002Fmessage). Put meta below a `---` divider so a human sees only the prose:\n\n```text\n[the prose]\n\n---\n## Notes (for the agent, not the reader)\n- What you used: format \u002F purpose \u002F medium \u002F tone \u002F audience (inferred or given)\n- Rules relaxed and why (e.g. \"skipped quantify-impact: visionary tone\")\n- Open items: [CLARIFY: ...] for anything unverified\n```\n\n**Review mode.** Use this template:\n\n```text\n## Verdict\nOne or two sentences: is it fit for its format, purpose, audience? Biggest lever to improve it.\n\n## Findings (highest impact first)\n### Structure\n- [issue] -> [why it hurts the reader] -> [suggested fix]\n### Substance\n- ...\n### Sentence-level \u002F style\n- [pattern] (e.g. \"em-dash overuse, 6 instances\") -> [fix], shown once with examples\n\n## Suggested revision (optional)\n[A rewritten version, if wanted or if it is the fastest way to show the fix.]\n```\n\n## Workflow\n\n### Step 1: Resolve the inputs\n\nDetermine the mode and the other inputs (see Inputs). Infer when confident; ask only when a key input is genuinely unclear. In generate mode, when you infer rather than ask, record your read in the *notes* block, not in the deliverable.\n\n### Step 2: Load the rules and the format\n\nAlways read `references\u002Funiversal-rules.md` and `references\u002Fai-patterns.md`. Then load the matching format:\n\n- A simple format is a single file: `references\u002Fformats\u002F\u003Cformat>.md`.\n- A format with **completeness levels** is a folder: load the base `references\u002Fformats\u002F\u003Cformat>\u002F\u003Cformat>.md` plus **exactly one** level file matching the completeness (e.g. `proposal\u002Fproposal-floater.md`). Do not load the other levels.\n\nIf no format matches, say so (\"I don't have a dedicated template for \u003Cformat> yet, so I'm using the universal rules\"), then write with the universal rules and the closest structural pattern. Do not pretend a template exists.\n\n### Step 3: Produce the draft or the review\n\nIn **generate**, write to the format template, apply the tone and medium guidance, and suppress the ai-patterns. In **review**, produce findings with the review template, applying each rule only where it fits this format, tone, and audience.\n\n### Step 4: Run the final passes, then present\n\nRun the **anti-hallucination pass** (universal-rules.md A9): classify each specific factual claim as Verified \u002F Inferred \u002F Unknown, and ask about or strip the Inferred and Unknown ones; never invent facts. Then run the **ai-patterns pass**. Then run the **reader-walk**: read each paragraph as the actual reader, who was not in your research or your context, and rewrite every sentence they could not restate in their own words without opening a link. Keep your analysis, verification tags and method notes in the notes block; the deliverable carries only what the reader needs. Present the output in the shape defined under Output.\n\n## Reference files\n\n- `references\u002Funiversal-rules.md` — always-on rules (incl. the A9 anti-hallucination protocol), conditional rules, and the tone and medium guidance. Read every time.\n- `references\u002Fai-patterns.md` — LLM tells to suppress so text does not read as machine-written. Read every time you draft.\n- `references\u002Fformats\u002F` — per-format templates and rules. Currently supported:\n  - `references\u002Fformats\u002Fproposal\u002F` — internal decision\u002Fstrategy proposal. Load the base (proposal.md) plus exactly one level file: proposal-floater.md, proposal-onepager.md, or proposal-full.md.\n  - `references\u002Fformats\u002Fraci\u002F` — RACI responsibility matrix (Responsible \u002F Accountable \u002F Consulted \u002F Informed). Load the base (raci.md) plus exactly one level file: raci-prose.md for plain text in Slack or email, or raci-onepager.md for the wiki-page artifact. The base carries the *ownership clause*: the mandatory sections that stop a RACI becoming a \"not my job\" shield or a blame map.\n  - `references\u002Fformats\u002Fpeer-feedback.md` — peer performance feedback (Strengths + Opportunities). Single file; no completeness levels. Collects receiver role, optional role expectations, and optional org values before generating or reviewing SBI-structured feedback items.\n  - `references\u002Fformats\u002Fposter.md` — program or project poster: the durable 1-2 page orientation page for work that already exists (what \u002F why and why now \u002F which goal it ladders up to \u002F in and out of scope \u002F tenets). Also answers to program brief, program overview, program profile, and project charter. Single file; two variants (program, project) selected inside it. Carries the *orientation contract* (the six questions a cold reader must answer without opening a link or asking anyone), the *durability rule* (the page holds the definition of the work, never its condition), and the two tenet tests. Every section is mandatory, glossary included, so the page stands alone. Not a proposal, not a status report, and not the pre-decision workshop artifact that shares the name.\n  - `references\u002Fformats\u002Fprfaq.md`: PR\u002FFAQ in the Amazon working-backwards style. It is the launch-day press release for a product not yet built, then a Customer FAQ for the end user (internal or external), an Internal FAQ for the leaders deciding to build it and for the builder team, and visuals of the customer experience: static, simple HTML wireframes first, one per customer benefit, then Mermaid diagrams for journeys and flows. Also answers to PRFAQ, working-backwards doc, and future press release. Single file; no completeness levels. Carries the nine-part press release in AWS's order, a mandatory FAQ core of nine questions plus a menu (around 15 questions), a per-part table of which rules the press release may relax (quotes and wireframe sample content are declared fiction), and length guidelines rather than hard caps: press release 250 to 375 words, press release plus FAQ under about 1,500 words, visuals outside the guide. Not a proposal, and not a real announcement of something already shipped.\n  - `references\u002Fformats\u002Fblog.md` — first-person blog post: the author telling colleagues what they think, why, and what changes. Single file; two variants (direction-setting, perspective) selected inside it. Carries the voice rule (\"I\" for the author's experience, \"we\" for team change), the altitude rule (direction-setting posts state what and why and leave the how to the team), and optional voice samples to match the author's own cadence.\n  - `references\u002Fformats\u002F_TEMPLATE.md` — scaffold for adding a new format (single-file or base+levels).\n\nTo grow the library, copy `_TEMPLATE.md`, fill in the template, default axes, format-specific rules, and which conditional rules to relax, then add a line to the supported list above. Build format-by-format; a small set of well-specified formats beats a large set of thin ones.\n",{"name":5,"description":7},"main","2919e29f0400d30ab8df88875909dd3f1c46f405","agents\u002Fskills\u002Fwriting-studio",1,"https:\u002F\u002Fgithub.com\u002Faminfara\u002Fdotfiles","https:\u002F\u002Fgithub.com\u002Faminfara","2026-11-08 07:16:22",{"source":8,"skillName":5,"commands":68,"prompt":78,"zipAvailable":79},[69,72,75],{"tool":70,"command":71},"npx","npx skills add aminfara\u002Fdotfiles --skill writing-studio",{"tool":73,"command":74},"bunx","bunx skills add aminfara\u002Fdotfiles --skill writing-studio",{"tool":76,"command":77},"pnpm","pnpm dlx skills add aminfara\u002Fdotfiles --skill writing-studio","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Faminfara\u002Fdotfiles\u002Fblob\u002Fmain\u002Fagents\u002Fskills\u002Fwriting-studio\u002FSKILL.md",true,[81,87,93,97,101,105,109,113,117,121,125,129,133,137,141],{"path":82,"resourceType":83,"resourceTypeDesc":84,"sizeBytes":85,"sourceHtmlUrl":86},".markdownlint-cli2.jsonc","OTHER","其他",453,"https:\u002F\u002Fgithub.com\u002Faminfara\u002Fdotfiles\u002Fblob\u002Fmain\u002Fagents\u002Fskills\u002Fwriting-studio\u002F.markdownlint-cli2.jsonc",{"path":88,"resourceType":89,"resourceTypeDesc":90,"sizeBytes":91,"sourceHtmlUrl":92},"references\u002Fai-patterns.md","REFERENCE","参考文档",7119,"https:\u002F\u002Fgithub.com\u002Faminfara\u002Fdotfiles\u002Fblob\u002Fmain\u002Fagents\u002Fskills\u002Fwriting-studio\u002Freferences\u002Fai-patterns.md",{"path":94,"resourceType":89,"resourceTypeDesc":90,"sizeBytes":95,"sourceHtmlUrl":96},"references\u002Fformats\u002F_TEMPLATE.md",2388,"https:\u002F\u002Fgithub.com\u002Faminfara\u002Fdotfiles\u002Fblob\u002Fmain\u002Fagents\u002Fskills\u002Fwriting-studio\u002Freferences\u002Fformats\u002F_TEMPLATE.md",{"path":98,"resourceType":89,"resourceTypeDesc":90,"sizeBytes":99,"sourceHtmlUrl":100},"references\u002Fformats\u002Fblog.md",4997,"https:\u002F\u002Fgithub.com\u002Faminfara\u002Fdotfiles\u002Fblob\u002Fmain\u002Fagents\u002Fskills\u002Fwriting-studio\u002Freferences\u002Fformats\u002Fblog.md",{"path":102,"resourceType":89,"resourceTypeDesc":90,"sizeBytes":103,"sourceHtmlUrl":104},"references\u002Fformats\u002Fpeer-feedback.md",9052,"https:\u002F\u002Fgithub.com\u002Faminfara\u002Fdotfiles\u002Fblob\u002Fmain\u002Fagents\u002Fskills\u002Fwriting-studio\u002Freferences\u002Fformats\u002Fpeer-feedback.md",{"path":106,"resourceType":89,"resourceTypeDesc":90,"sizeBytes":107,"sourceHtmlUrl":108},"references\u002Fformats\u002Fposter.md",21393,"https:\u002F\u002Fgithub.com\u002Faminfara\u002Fdotfiles\u002Fblob\u002Fmain\u002Fagents\u002Fskills\u002Fwriting-studio\u002Freferences\u002Fformats\u002Fposter.md",{"path":110,"resourceType":89,"resourceTypeDesc":90,"sizeBytes":111,"sourceHtmlUrl":112},"references\u002Fformats\u002Fprfaq.md",32579,"https:\u002F\u002Fgithub.com\u002Faminfara\u002Fdotfiles\u002Fblob\u002Fmain\u002Fagents\u002Fskills\u002Fwriting-studio\u002Freferences\u002Fformats\u002Fprfaq.md",{"path":114,"resourceType":89,"resourceTypeDesc":90,"sizeBytes":115,"sourceHtmlUrl":116},"references\u002Fformats\u002Fproposal\u002Fproposal-floater.md",1546,"https:\u002F\u002Fgithub.com\u002Faminfara\u002Fdotfiles\u002Fblob\u002Fmain\u002Fagents\u002Fskills\u002Fwriting-studio\u002Freferences\u002Fformats\u002Fproposal\u002Fproposal-floater.md",{"path":118,"resourceType":89,"resourceTypeDesc":90,"sizeBytes":119,"sourceHtmlUrl":120},"references\u002Fformats\u002Fproposal\u002Fproposal-full.md",4404,"https:\u002F\u002Fgithub.com\u002Faminfara\u002Fdotfiles\u002Fblob\u002Fmain\u002Fagents\u002Fskills\u002Fwriting-studio\u002Freferences\u002Fformats\u002Fproposal\u002Fproposal-full.md",{"path":122,"resourceType":89,"resourceTypeDesc":90,"sizeBytes":123,"sourceHtmlUrl":124},"references\u002Fformats\u002Fproposal\u002Fproposal-onepager.md",2050,"https:\u002F\u002Fgithub.com\u002Faminfara\u002Fdotfiles\u002Fblob\u002Fmain\u002Fagents\u002Fskills\u002Fwriting-studio\u002Freferences\u002Fformats\u002Fproposal\u002Fproposal-onepager.md",{"path":126,"resourceType":89,"resourceTypeDesc":90,"sizeBytes":127,"sourceHtmlUrl":128},"references\u002Fformats\u002Fproposal\u002Fproposal.md",6891,"https:\u002F\u002Fgithub.com\u002Faminfara\u002Fdotfiles\u002Fblob\u002Fmain\u002Fagents\u002Fskills\u002Fwriting-studio\u002Freferences\u002Fformats\u002Fproposal\u002Fproposal.md",{"path":130,"resourceType":89,"resourceTypeDesc":90,"sizeBytes":131,"sourceHtmlUrl":132},"references\u002Fformats\u002Fraci\u002Fraci-onepager.md",6283,"https:\u002F\u002Fgithub.com\u002Faminfara\u002Fdotfiles\u002Fblob\u002Fmain\u002Fagents\u002Fskills\u002Fwriting-studio\u002Freferences\u002Fformats\u002Fraci\u002Fraci-onepager.md",{"path":134,"resourceType":89,"resourceTypeDesc":90,"sizeBytes":135,"sourceHtmlUrl":136},"references\u002Fformats\u002Fraci\u002Fraci-prose.md",3719,"https:\u002F\u002Fgithub.com\u002Faminfara\u002Fdotfiles\u002Fblob\u002Fmain\u002Fagents\u002Fskills\u002Fwriting-studio\u002Freferences\u002Fformats\u002Fraci\u002Fraci-prose.md",{"path":138,"resourceType":89,"resourceTypeDesc":90,"sizeBytes":139,"sourceHtmlUrl":140},"references\u002Fformats\u002Fraci\u002Fraci.md",14892,"https:\u002F\u002Fgithub.com\u002Faminfara\u002Fdotfiles\u002Fblob\u002Fmain\u002Fagents\u002Fskills\u002Fwriting-studio\u002Freferences\u002Fformats\u002Fraci\u002Fraci.md",{"path":142,"resourceType":89,"resourceTypeDesc":90,"sizeBytes":143,"sourceHtmlUrl":144},"references\u002Funiversal-rules.md",9574,"https:\u002F\u002Fgithub.com\u002Faminfara\u002Fdotfiles\u002Fblob\u002Fmain\u002Fagents\u002Fskills\u002Fwriting-studio\u002Freferences\u002Funiversal-rules.md",[146,173,185,194,206,216],{"skillNo":147,"name":148,"nameZh":6,"description":149,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":150,"categories":151,"keywords":155,"publishedAt":55},"01M6WMDV1M95RG1TFY6GJSMRP5","programming","Before writing, changing, or fixing any code in any language, read this guide of design principles (deep modules, functional core and imperative shell, explicit dependencies, modular monolith). It applies under any workflow skill, including test-first ones, and does not define a test loop.","https:\u002F\u002Fgithub.com\u002Faminfara\u002Fdotfiles\u002Fblob\u002Fmain\u002Fagents\u002Fskills\u002Fprogramming\u002FSKILL.md",[152],{"categoryNo":153,"categoryName":154,"taxonomyType":32,"taxonomyTypeDesc":33},"01JBSEEDCAT000000000000030","开发工程师",[148,156,157,158,159,160,161,162,52,163,164,165,166,167,168,169,170,171,172,37],"design principles","core","code","first","shell","loop","modules","deep","define","workflow skill","functional","principles","monolith","test-first","modular","test","workflow",{"skillNo":174,"name":175,"nameZh":6,"description":176,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":177,"categories":178,"keywords":182,"publishedAt":55},"01M6CCV8Y4KAPBNWFK3NX53W40","workflow-step-numbering","Fixture with non-sequential step numbering to verify R011 fires.","https:\u002F\u002Fgithub.com\u002Faminfara\u002Fdotfiles\u002Fblob\u002Fmain\u002Fagents\u002Fskills\u002Fskill-linter\u002Ftests\u002Ffixtures\u002Fworkflow-step-numbering\u002FSKILL.md",[179],{"categoryNo":180,"categoryName":181,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",[183,172,184],"workflow step numbering","verify",{"skillNo":186,"name":187,"nameZh":6,"description":188,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":189,"categories":190,"keywords":192,"publishedAt":55},"01M6CCV7ESK7X85T4MZ3P0HK0A","workflow-no-steps","Fixture whose Workflow has no Step sub-headings to verify R010 fires.","https:\u002F\u002Fgithub.com\u002Faminfara\u002Fdotfiles\u002Fblob\u002Fmain\u002Fagents\u002Fskills\u002Fskill-linter\u002Ftests\u002Ffixtures\u002Fworkflow-no-steps\u002FSKILL.md",[191],{"categoryNo":180,"categoryName":181,"taxonomyType":21,"taxonomyTypeDesc":22},[193,172,184],"workflow no steps",{"skillNo":195,"name":196,"nameZh":6,"description":197,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":198,"categories":199,"keywords":201,"publishedAt":55},"01M6CCV5P9SH25CBHDDRJFY393","valid-skill","A fully compliant fixture skill used to verify skill-linter passes a clean SKILL.md without findings.","https:\u002F\u002Fgithub.com\u002Faminfara\u002Fdotfiles\u002Fblob\u002Fmain\u002Fagents\u002Fskills\u002Fskill-linter\u002Ftests\u002Ffixtures\u002Fvalid-skill\u002FSKILL.md",[200],{"categoryNo":180,"categoryName":181,"taxonomyType":21,"taxonomyTypeDesc":22},[202,203,204,205,184],"valid skill","valid","fixture skill","linter",{"skillNo":207,"name":208,"nameZh":6,"description":209,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":210,"categories":211,"keywords":213,"publishedAt":55},"01M6CCV3X1D1WRCP0VNCX4XE17","section-out-of-order","Fixture with Workflow before When to use to verify R007 fires.","https:\u002F\u002Fgithub.com\u002Faminfara\u002Fdotfiles\u002Fblob\u002Fmain\u002Fagents\u002Fskills\u002Fskill-linter\u002Ftests\u002Ffixtures\u002Fsection-out-of-order\u002FSKILL.md",[212],{"categoryNo":180,"categoryName":181,"taxonomyType":21,"taxonomyTypeDesc":22},[214,215,184,172],"section out of order","use",{"skillNo":217,"name":218,"nameZh":6,"description":219,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":220,"categories":221,"keywords":222,"publishedAt":55},"01M6CCV25Q9K6BWJZDAXQPH0HG","references-with-binary","Fixture whose references directory contains a non-text file to verify R025 fires.","https:\u002F\u002Fgithub.com\u002Faminfara\u002Fdotfiles\u002Fblob\u002Fmain\u002Fagents\u002Fskills\u002Fskill-linter\u002Ftests\u002Ffixtures\u002Freferences-with-binary\u002FSKILL.md",[],[223,224,50,184,225],"references with binary","directory","file"]