[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M73RXDTR96SBKTEEE35JMWS7":3,"skill-same:01M73RXDTR96SBKTEEE35JMWS7":51},{"skillNo":4,"name":5,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"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":6,"ownerHtmlUrl":28,"ownerBlogUrl":29,"ownerDescription":6,"updatedAt":30,"install":31,"resources":44},"01M73RXDTR96SBKTEEE35JMWS7","technical-writer-tutorial",null,"lookatitude\u002Fguild","lookatitude","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F524917?v=4","01M71GJ2KGXFSJZKAZC5P1ZXXM","Miguel Pinto","01M71GJ2MH4SH9WJKP8M7XZZ0P",8,"MIT","https:\u002F\u002Fgithub.com\u002Flookatitude\u002Fguild\u002Fblob\u002Fmain\u002Fskills\u002Fspecialists\u002Ftechnical-writer-tutorial\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: technical-writer-tutorial\ndescription: Writes a walk-through tutorial — getting-started, first-project, end-to-end integration — with numbered steps, expected output per step, and a troubleshooting section. Pulled by the `technical-writer` specialist. TRIGGER: \"write a getting-started tutorial for X\", \"write the quickstart guide\", \"walk a new developer through integrating Y\", \"write the first-project tutorial\", \"create a step-by-step how-to for Z\", \"write a hands-on walkthrough\". DO NOT TRIGGER for: reference docs for every endpoint (use `technical-writer-api-docs`), task-based user manual pages (use `technical-writer-user-manual`), release notes (use `technical-writer-release-notes`), designing the onboarding UX (product\u002Fdesign scope, not this skill), marketing content explaining why to use the product (copywriter-long-form).\nwhen_to_use: The parent `technical-writer` specialist pulls this skill when the task needs a linear, hands-on walkthrough a reader completes front-to-back. Also fires on explicit user request.\ntype: specialist\n---\n\n# technical-writer-tutorial\n\nMatch the product's actual install\u002Frun steps (verify them), don't rewrite adjacent docs, evidence = a reader who follows the tutorial reaches the working end-state without detours.\n\n## What you do\n\nWrite one tutorial that takes a reader from zero to a working outcome in one sitting. A tutorial is not reference — it is a guided, linear path with one happy path and explicit escape hatches.\n\n- State the outcome up front. The reader should know exactly what they'll have at the end (and roughly how long it takes).\n- List prerequisites concretely: OS, versions, accounts, CLIs. \"A recent Node\" is not a prereq; \"Node ≥ 20\" is.\n- Verify every command yourself or with the owning specialist before shipping. A broken step zero kills the tutorial.\n- Each step: one action, the command\u002Fcode, the expected output. If the output varies, show the anchor line.\n- Include a \"what could go wrong\" per risky step with the recovery command.\n- End with \"where to go next\" — 2–3 concrete follow-up paths.\n\n## Output shape\n\nA single markdown file with:\n\n1. **Outcome** — one paragraph on what you'll build + estimated time.\n2. **Prerequisites** — versioned list.\n3. **Steps** — numbered. Per step: action, code block, expected output, common pitfall.\n4. **Verify** — final check the reader runs to confirm success.\n5. **Troubleshooting** — 3–6 known failure modes with fixes.\n6. **Next** — linked reference docs, manual pages, deeper tutorials.\n\nStore at `.guild\u002Fruns\u002F\u003Crun-id>\u002Fdocs\u002Ftutorial-\u003Cslug>.md` if tracked.\n\n## Anti-patterns\n\n- Skipping setup — \"assuming you have the CLI installed\" is not a tutorial; it's a trap.\n- Assuming tools installed that aren't default (`jq`, `gh`, specific SDK versions).\n- No expected output — the reader can't tell pass from fail without running six more commands.\n- No troubleshooting section — the first error sends them to support.\n- Multiple happy paths in one tutorial (mac\u002Flinux\u002Fwindows all fully inline) — fork into variants instead.\n- Reference-doc creep — linking out is better than inlining the full schema.\n\n## Handoff\n\nReturn the tutorial path to the invoking `technical-writer` specialist. If the tutorial surfaces a broken step or missing feature, raise a followup for the owning engineering specialist. Chain into `technical-writer-api-docs` for reference depth and `technical-writer-user-manual` for task-based follow-ups. This skill does not dispatch.\n","# technical-writer-tutorial\n\nMatch the product's actual install\u002Frun steps (verify them), don't rewrite adjacent docs, evidence = a reader who follows the tutorial reaches the working end-state without detours.\n\n## What you do\n\nWrite one tutorial that takes a reader from zero to a working outcome in one sitting. A tutorial is not reference — it is a guided, linear path with one happy path and explicit escape hatches.\n\n- State the outcome up front. The reader should know exactly what they'll have at the end (and roughly how long it takes).\n- List prerequisites concretely: OS, versions, accounts, CLIs. \"A recent Node\" is not a prereq; \"Node ≥ 20\" is.\n- Verify every command yourself or with the owning specialist before shipping. A broken step zero kills the tutorial.\n- Each step: one action, the command\u002Fcode, the expected output. If the output varies, show the anchor line.\n- Include a \"what could go wrong\" per risky step with the recovery command.\n- End with \"where to go next\" — 2–3 concrete follow-up paths.\n\n## Output shape\n\nA single markdown file with:\n\n1. **Outcome** — one paragraph on what you'll build + estimated time.\n2. **Prerequisites** — versioned list.\n3. **Steps** — numbered. Per step: action, code block, expected output, common pitfall.\n4. **Verify** — final check the reader runs to confirm success.\n5. **Troubleshooting** — 3–6 known failure modes with fixes.\n6. **Next** — linked reference docs, manual pages, deeper tutorials.\n\nStore at `.guild\u002Fruns\u002F\u003Crun-id>\u002Fdocs\u002Ftutorial-\u003Cslug>.md` if tracked.\n\n## Anti-patterns\n\n- Skipping setup — \"assuming you have the CLI installed\" is not a tutorial; it's a trap.\n- Assuming tools installed that aren't default (`jq`, `gh`, specific SDK versions).\n- No expected output — the reader can't tell pass from fail without running six more commands.\n- No troubleshooting section — the first error sends them to support.\n- Multiple happy paths in one tutorial (mac\u002Flinux\u002Fwindows all fully inline) — fork into variants instead.\n- Reference-doc creep — linking out is better than inlining the full schema.\n\n## Handoff\n\nReturn the tutorial path to the invoking `technical-writer` specialist. If the tutorial surfaces a broken step or missing feature, raise a followup for the owning engineering specialist. Chain into `technical-writer-api-docs` for reference depth and `technical-writer-user-manual` for task-based follow-ups. This skill does not dispatch.\n",{},"main","2e58b0360ca51ca3c96ca8e015ef5aba5738803d","skills\u002Fspecialists\u002Ftechnical-writer-tutorial",0,"https:\u002F\u002Fgithub.com\u002Flookatitude\u002Fguild","https:\u002F\u002Fgithub.com\u002Flookatitude","https:\u002F\u002Flookatitude.com","2026-11-06 03:55:18",{"source":7,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add lookatitude\u002Fguild --skill technical-writer-tutorial",{"tool":37,"command":38},"bunx","bunx skills add lookatitude\u002Fguild --skill technical-writer-tutorial",{"tool":40,"command":41},"pnpm","pnpm dlx skills add lookatitude\u002Fguild --skill technical-writer-tutorial","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Flookatitude\u002Fguild\u002Fblob\u002Fmain\u002Fskills\u002Fspecialists\u002Ftechnical-writer-tutorial\u002FSKILL.md",true,[45],{"path":46,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":49,"sourceHtmlUrl":50},"evals.json","REFERENCE","参考文档",752,"https:\u002F\u002Fgithub.com\u002Flookatitude\u002Fguild\u002Fblob\u002Fmain\u002Fskills\u002Fspecialists\u002Ftechnical-writer-tutorial\u002Fevals.json",[52,58,64,70,76,82],{"skillNo":53,"name":54,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":55,"categories":56,"keywords":57,"publishedAt":18},"01M73RX9FY2GNEZT1S2SJZH307","social-media-thread","https:\u002F\u002Fgithub.com\u002Flookatitude\u002Fguild\u002Fblob\u002Fmain\u002Fskills\u002Fspecialists\u002Fsocial-media-thread\u002FSKILL.md",[],[],{"skillNo":59,"name":60,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":61,"categories":62,"keywords":63,"publishedAt":18},"01M73RWY3CNA6HP52QC65XTZ5A","security-dependency-audit","https:\u002F\u002Fgithub.com\u002Flookatitude\u002Fguild\u002Fblob\u002Fmain\u002Fskills\u002Fspecialists\u002Fsecurity-dependency-audit\u002FSKILL.md",[],[],{"skillNo":65,"name":66,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":18},"01M73RWBSKQXZ13SVRGS5K1K72","marketing-launch-plan","https:\u002F\u002Fgithub.com\u002Flookatitude\u002Fguild\u002Fblob\u002Fmain\u002Fskills\u002Fspecialists\u002Fmarketing-launch-plan\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":18},"01M73RW8DJAG381R94DN6KSTEG","marketing-ab-copy-variants","https:\u002F\u002Fgithub.com\u002Flookatitude\u002Fguild\u002Fblob\u002Fmain\u002Fskills\u002Fspecialists\u002Fmarketing-ab-copy-variants\u002FSKILL.md",[],[],{"skillNo":77,"name":78,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":18},"01M73RW44HRQJTJ33V12SVS612","frontend-bundler-config","https:\u002F\u002Fgithub.com\u002Flookatitude\u002Fguild\u002Fblob\u002Fmain\u002Fskills\u002Fspecialists\u002Ffrontend-bundler-config\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":18},"01M73RVFMJXAHRN7JVSF8FEJA5","doc-writer-onboarding-doc","Authors onboarding documentation and contributor guides — getting-started narrative pages, CONTRIBUTING.md, developer onboarding docs, new-user setup guides, CODE_OF_CONDUCT.md, GOVERNANCE.md. Pulled by the `doc-writer` specialist. TRIGGER: \"write a getting-started guide\", \"create a CONTRIBUTING.md\", \"onboarding guide for new developers\", \"write the contributor guide\", \"new-user setup documentation\", \"developer onboarding doc\", \"write the getting started page\", \"add a CODE_OF_CONDUCT\". DO NOT TRIGGER for: project README overview (use `doc-writer-readme`), onboarding email sequences for existing SaaS users (use `copywriter-email-sequences` — copywriter owns lifecycle nurture emails), API reference docs (use `technical-writer-api-docs`), formal step-by-step tutorials with prerequisite\u002Fverify blocks (use `technical-writer-tutorial`), changelogs or release notes (use `technical-writer-release-notes`), marketing copy about onboarding (use `copywriter-long-form`).","https:\u002F\u002Fgithub.com\u002Flookatitude\u002Fguild\u002Fblob\u002Fmain\u002Fskills\u002Fspecialists\u002Fdoc-writer-onboarding-doc\u002FSKILL.md",[],[]]