{"id":78817,"plugin_id":"plugins_6ab4352c7c48819199c4dd10b40fefe3","kind":"skill","collection_source":"plugin_package","comparison_source":null,"observed_at":"2026-11-03T18:48:06.679Z","digest":"1e94090df6183d73d61480d4da976553e2d9ade1887bc4e137e1142f58978339","against":null,"payload":{"description":"Write a natural, technically accurate article or blog post grounded in research, useful examples and a clear reader promise.","included_files":[],"name":"write-technical-article","skill_md_contents":"---\nname: write-technical-article\ndescription: Write a natural, technically accurate article or blog post grounded in research, useful examples and a clear reader promise.\n---\n\n# Write Technical Article\n\n**Shared standards.** Preserve the user's purpose and existing material; never fabricate evidence, URLs, quotations, citations, first-person experiences, interviews, tool runs or publication. Distinguish sourced observations from independent reproduction and analysis. Use actual host research/files/code tools when available; disclose unavailable verification. For current facts, verify fresh authoritative sources. Ask only when an essential constraint prevents useful work.\n\n## Procedure\n1. Determine reader knowledge, central claim and why the topic matters. For current claims load `deep-research` or `verify-sources` first.\n2. Choose a coherent story: practical problem → mental model → mechanism → real example → constraints → takeaway. Vary structure for topic; avoid a canned template.\n3. Show how and why, not merely a list of features. If code is included, label assumed versions and what was actually tested; never invent benchmark outcomes.\n4. Support material claims with appropriate sources near the claim; retain nuance, caveats, failure modes and trade-offs.\n5. Edit for natural human prose. No invented personal experience, fake dramatic hooks, filler 'AI era' intros, repetitive conclusions, hype, or SEO stuffing.\n6. When requested, supply a complete publishable article, not only an outline. Images/diagrams need a concrete explanatory purpose.\n## Deliver\nComplete article with strong title, appropriate headings, source links and a useful ending; note unverified assertions without pretending publication occurred.\n\n## Related references\n- Read `../../references/article-craft.md` when it materially informs this task.\n- Read `../../references/technical-examples.md` when it materially informs this task.\n- Read `../../references/fact-check-and-edit.md` when it materially informs this task.\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}