[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7E8XQ2W849DKXKXMP6S7T8V":3,"skill-same:01M7E8XQ2W849DKXKXMP6S7T8V":48},{"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":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":27,"commitSha":28,"skillDirectory":29,"forksCount":30,"repositoryHtmlUrl":31,"repositoryHomepageUrl":6,"ownerHtmlUrl":32,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":33,"install":34,"resources":47},"01M7E8XQ2W849DKXKXMP6S7T8V","technical-docs",null,"Writes technical documentation, specs and design docs (context, goals, ADR-style decisions, mermaid diagrams, rollout plan) and suggests where to store them. Use when asked to \"document this\", for a design doc, a spec, an ADR, a technical proposal or an architecture README.","ngentile92\u002Fmnemos","ngentile92","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F87906865?v=4","01M7E8WERDXTQ76PMJD1HTD165","Nicolas Gentile","01M7E8WESDCPS8MEED5021NYFK",4,"MIT","https:\u002F\u002Fgithub.com\u002Fngentile92\u002Fmnemos\u002Fblob\u002Fmain\u002Fexamples\u002Fskills\u002Fskills\u002Fshared\u002Ftechnical-docs\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: technical-docs\ndescription: Writes technical documentation, specs and design docs (context, goals, ADR-style decisions, mermaid diagrams, rollout plan) and suggests where to store them. Use when asked to \"document this\", for a design doc, a spec, an ADR, a technical proposal or an architecture README.\nmetadata:\n  hub-owner: shared\n  version: \"1\"\n---\n\n# Technical documentation\n\n## Before writing\n1. `hub_whoami` for the context and `memory_search` on the topic (previous decisions, existing docs, system names).\n   Don't contradict a recorded decision without flagging it.\n2. Read the real code you are documenting (models, endpoints, flows). Don't invent class, table or endpoint names:\n   if you haven't verified it, mark it `TODO: verify`.\n3. Pick the type: **design doc\u002Fspec** (something to build), **ADR** (one specific decision), **system doc** (how\n   something that already exists works).\n\n## Design doc \u002F spec structure\n```\n# Design: \u003Ctitle>\n## Overview            (3-5 lines: what and why)\n## Goals \u002F Non-goals   (bullets; non-goals prevent scope creep)\n## Current State       (how it works today, with file paths)\n## Problem Statement\n## Proposed Architecture (+ mermaid diagram)\n## Decisions           (ADR format below, one per decision)\n## Rollout \u002F Migration (steps, feature flags, data migrations, rollback)\n## Testing             (unit, integration, e2e; what gets measured)\n## Open Questions      (with an owner if known)\n```\n\n## Decisions (short ADR)\n```\n### D1: \u003Cdecision in one line>\n- Status: proposed | accepted | superseded by Dn\n- Context: what forces the decision\n- Options: A (pros\u002Fcons), B (pros\u002Fcons)\n- Decision and consequences\n```\nReal pros and cons; if an option has no downsides, don't force a trade-off.\n\n## Diagrams\nUse mermaid in a ```mermaid block: `flowchart LR` for pipelines and components, `sequenceDiagram` for\nrequests\u002Fwebhooks\u002FMCP, `erDiagram` for data models. At most ~15 nodes per diagram; split it if it grows.\n\n## Where to store it\n- Follow the repo's convention if there is one (`docs\u002F`, `design_docs\u002F`, `adr\u002F`). Otherwise: design docs in\n  `docs\u002Fdesign\u002F\u003Ctopic>.md`, ADRs in `docs\u002Fadr\u002FNNNN-\u003Ctitle>.md`, system docs in `docs\u002F\u003CTOPIC>.md`, short ones in `README.md`.\n- Docs that must be visible outside the repo (wiki, task tracker) only if the user asks.\n- Never paste secret values or `.env` contents; name the variable and say it lives in the secret manager (the hub\n  injects it with `secret_http_request`).\n\n## When done\n- Check: would a newcomer understand the *why* without asking you? Is every claim about the code verified?\n- `memory_save` a self-contained note: date, doc path, main decision and status (proposed vs accepted). Pass\n  `project` where required.\n","# Technical documentation\n\n## Before writing\n1. `hub_whoami` for the context and `memory_search` on the topic (previous decisions, existing docs, system names).\n   Don't contradict a recorded decision without flagging it.\n2. Read the real code you are documenting (models, endpoints, flows). Don't invent class, table or endpoint names:\n   if you haven't verified it, mark it `TODO: verify`.\n3. Pick the type: **design doc\u002Fspec** (something to build), **ADR** (one specific decision), **system doc** (how\n   something that already exists works).\n\n## Design doc \u002F spec structure\n```\n# Design: \u003Ctitle>\n## Overview            (3-5 lines: what and why)\n## Goals \u002F Non-goals   (bullets; non-goals prevent scope creep)\n## Current State       (how it works today, with file paths)\n## Problem Statement\n## Proposed Architecture (+ mermaid diagram)\n## Decisions           (ADR format below, one per decision)\n## Rollout \u002F Migration (steps, feature flags, data migrations, rollback)\n## Testing             (unit, integration, e2e; what gets measured)\n## Open Questions      (with an owner if known)\n```\n\n## Decisions (short ADR)\n```\n### D1: \u003Cdecision in one line>\n- Status: proposed | accepted | superseded by Dn\n- Context: what forces the decision\n- Options: A (pros\u002Fcons), B (pros\u002Fcons)\n- Decision and consequences\n```\nReal pros and cons; if an option has no downsides, don't force a trade-off.\n\n## Diagrams\nUse mermaid in a ```mermaid block: `flowchart LR` for pipelines and components, `sequenceDiagram` for\nrequests\u002Fwebhooks\u002FMCP, `erDiagram` for data models. At most ~15 nodes per diagram; split it if it grows.\n\n## Where to store it\n- Follow the repo's convention if there is one (`docs\u002F`, `design_docs\u002F`, `adr\u002F`). Otherwise: design docs in\n  `docs\u002Fdesign\u002F\u003Ctopic>.md`, ADRs in `docs\u002Fadr\u002FNNNN-\u003Ctitle>.md`, system docs in `docs\u002F\u003CTOPIC>.md`, short ones in `README.md`.\n- Docs that must be visible outside the repo (wiki, task tracker) only if the user asks.\n- Never paste secret values or `.env` contents; name the variable and say it lives in the secret manager (the hub\n  injects it with `secret_http_request`).\n\n## When done\n- Check: would a newcomer understand the *why* without asking you? Is every claim about the code verified?\n- `memory_save` a self-contained note: date, doc path, main decision and status (proposed vs accepted). Pass\n  `project` where required.\n",{"name":5,"metadata":24,"description":7},{"version":25,"hub-owner":26},"1","shared","main","975f3927027c15c51a62020786c31e9b84bf7923","examples\u002Fskills\u002Fskills\u002Fshared\u002Ftechnical-docs",1,"https:\u002F\u002Fgithub.com\u002Fngentile92\u002Fmnemos","https:\u002F\u002Fgithub.com\u002Fngentile92","2026-11-02 03:28:07",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add ngentile92\u002Fmnemos --skill technical-docs",{"tool":40,"command":41},"bunx","bunx skills add ngentile92\u002Fmnemos --skill technical-docs",{"tool":43,"command":44},"pnpm","pnpm dlx skills add ngentile92\u002Fmnemos --skill technical-docs","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fngentile92\u002Fmnemos\u002Fblob\u002Fmain\u002Fexamples\u002Fskills\u002Fskills\u002Fshared\u002Ftechnical-docs\u002FSKILL.md",true,[],[49,56,63,70,77,84],{"skillNo":50,"name":51,"nameZh":6,"description":52,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":53,"categories":54,"keywords":55,"publishedAt":19},"01M7E8XXY7B3WF14QD3BCH6H08","incident-postmortem","Writes a blameless incident postmortem (timeline, impact, root cause, contributing factors, action items) from logs, chat history or notes. Use after an outage, a failed deploy or a production bug, or when asked for an \"incident report\" or \"postmortem\".","https:\u002F\u002Fgithub.com\u002Fngentile92\u002Fmnemos\u002Fblob\u002Fmain\u002Fexamples\u002Fskills\u002Fskills\u002Fwork\u002Fincident-postmortem\u002FSKILL.md",[],[],{"skillNo":57,"name":58,"nameZh":6,"description":59,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":19},"01M7E8XV3TTMVHXME1GNBJ19NA","release-notes","Writes user-facing release notes and a changelog entry from merged PRs or commits since the last release. Use when asked for \"release notes\", a \"changelog\" or \"what changed since vX\".","https:\u002F\u002Fgithub.com\u002Fngentile92\u002Fmnemos\u002Fblob\u002Fmain\u002Fexamples\u002Fskills\u002Fskills\u002Fside\u002Frelease-notes\u002FSKILL.md",[],[],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":19},"01M7E8XKCVF0Z2XMKHEF8F5FFN","status-report","Builds a status report (weekly or for a period) by combining git history, the task tracker and hub memory; returns done \u002F in progress \u002F blockers \u002F next steps. Use when asked for a status report, a weekly, \"what did I do this week\", a standup summary or an update for a manager.","https:\u002F\u002Fgithub.com\u002Fngentile92\u002Fmnemos\u002Fblob\u002Fmain\u002Fexamples\u002Fskills\u002Fskills\u002Fshared\u002Fstatus-report\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":19},"01M7E8XF8BC23TTSR1NZ61ZDEN","review-pr","Reviews a pull request with a fixed checklist (correctness, security, tests, readability) and returns prioritized findings. Use when asked to review a PR, a diff or a code change.","https:\u002F\u002Fgithub.com\u002Fngentile92\u002Fmnemos\u002Fblob\u002Fmain\u002Fexamples\u002Fskills\u002Fskills\u002Fshared\u002Freview-pr\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":19},"01M7E8XAWJZVCQX2FQ8KN3Q0BR","memory-capture","Decides what is worth remembering from the conversation and saves it as short, self-contained notes with [[links]] to people, companies and projects. Use when the user says \"remember this\", \"save this\", \"note that\", or at the end of a session with decisions worth keeping.","https:\u002F\u002Fgithub.com\u002Fngentile92\u002Fmnemos\u002Fblob\u002Fmain\u002Fexamples\u002Fskills\u002Fskills\u002Fshared\u002Fmemory-capture\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":19},"01M7E8X7BP55TZM325DHHMK7HR","meeting-notes","Turns a meeting transcript or rough notes into a summary with decisions, action items (owner + date) and open questions, and saves the durable parts to memory. Use when the user pastes a transcript, call notes or says \"summarise this meeting\".","https:\u002F\u002Fgithub.com\u002Fngentile92\u002Fmnemos\u002Fblob\u002Fmain\u002Fexamples\u002Fskills\u002Fskills\u002Fshared\u002Fmeeting-notes\u002FSKILL.md",[],[]]