[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7ASQ1VWNVP1RE7M5D4G2QMG":3,"skill-same:01M7ASQ1VWNVP1RE7M5D4G2QMG":46},{"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":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":6,"ownerDescription":30,"updatedAt":31,"install":32,"resources":45},"01M7ASQ1VWNVP1RE7M5D4G2QMG","review-doc",null,"Use when the user asks to review, critique, score, grade, or \"how good is this doc\" for a Markdown doc or pasted text. Read-only. Scores it on the 20 Practical Prose dimensions and emits a findings table. Does not edit; fix-doc applies the findings next.","ozzycodes2\u002Fclaudellum","ozzycodes2","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F21285094?v=4","01M7ASJ57KTP519F96S4QGM7C5","Osniel Quintana","01M7ASJ589JS8S075AA92Y08S4",1,"MIT","https:\u002F\u002Fgithub.com\u002Fozzycodes2\u002Fclaudellum\u002Fblob\u002Fmain\u002Ftechnical-writing\u002Fskills\u002Freview-doc\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: review-doc\ndescription: Use when the user asks to review, critique, score, grade, or \"how good is this doc\" for a Markdown doc or pasted text. Read-only. Scores it on the 20 Practical Prose dimensions and emits a findings table. Does not edit; fix-doc applies the findings next.\n---\n\n# Reviewing Docs\n\nReview stage of generate, review, fix. Read the doc, score it against the Practical Prose rubric, and emit a findings table that `fix-doc` consumes. **Change nothing**: no edits to the doc, no side files. Grading is done by you against the rubric; there is no scoring CLI.\n\nInput is a file path or inline text. For inline text, review it the same way; Location uses heading names and paragraph ordinals (\"para 3\") since there are no lines.\n\nReferences, relative to this skill:\n\n- `..\u002F..\u002Freferences\u002Fpprose-rubric.md`: score anchors, NA\u002FERR decision tree, cascades, justified deviations.\n- `..\u002F..\u002Freferences\u002Fpprose-guidelines.md`: the rules cited as \"missed rule\".\n- `..\u002F..\u002Freferences\u002Fcommon-doc-guidelines.md`: structure, style, and Markdown formatting.\n- `..\u002F..\u002Freferences\u002Fdiagrams.md`: when a diagram is warranted.\n- `..\u002F..\u002Freferences\u002Fai-tells.md`: machine-written patterns; report them under Expression or Form.\n\nVendored files keep upstream names in their text: `practical-prose-guidelines.md` is `pprose-guidelines.md`, `practical-prose-rubric.md` is `pprose-rubric.md`, `ai-prose-corrections.md` is `ai-tells.md`. Principles, metrics, and runbooks are not vendored; ignore links to them.\n\n## Steps\n\n1. **Refuse generated files.** If the file carries a `DO NOT EDIT`, `@generated`, or \"generated by\" marker, or sits in a generated-output path, stop. Name the generator or source file and say to review that instead.\n2. **Orient.** Identify the reader, the doc type, the task the reader will do with it, and the risk level. Read the doc in full before scoring. Frontmatter and HTML comments are metadata, not prose defects.\n3. **Score all 20 dimensions** per the decision tree in `pprose-rubric.md`: `NA` if the per-dimension NA anchor fits, `ERR` only for a procedural failure, else 1-5. Honor the cascades (Verifiability to Factuality, Suitability to Relevance, Soundness to Parsimony). For every score below 5, cite the specific guideline rule missed from `pprose-guidelines.md`. A documented justified deviation (see rubric) is not a defect; note it and do not penalize it.\n4. **Check `common-doc-guidelines.md`.** File structure, headings, lists, links, and Markdown formatting problems become Form findings (Organization, Consistency, Formatting). Heading-case and list-punctuation rules yield to the doc's or repo's existing consistent convention; raise only inconsistency.\n5. **Check diagrams** per `diagrams.md`. Where the doc describes architecture, a flow, states, or more than three interacting components in prose and has no figure, add a finding with class `diagram`. Use the dimension the gap hurts most, usually Clarity or Organization.\n6. **Classify each finding** with pprose's apply-vs-flag rule:\n   - `apply`: safe and meaning-preserving. Expression and Form findings, including tells from `ai-tells.md`, whose fix cannot change meaning, claim strength, or scope. `fix-doc` auto-applies these rows.\n   - `flag`: substantive and judgment-bearing. Every Purpose, Reasoning, Grounding, and Judgment finding. Also any Expression or Form finding whose fix would alter meaning, claim strength, or scope (for example, a Concision cut that removes a caveat). Needs the author or new facts; never present as decided.\n   - `diagram`: a figure to add (step 5).\n\n   When a defect fits two classes, file it at the shallowest class that fully fixes it, but a possible meaning change always makes it `flag`. When unsure whether a fix preserves meaning, use `flag`.\n\n## Rules\n\n- **No footer.** Ignore footer-presence criteria when scoring; never mark a dimension NA for that reason. Never raise a footer finding.\n- Every score below 5 has a Missed rule; every finding names a concrete, locatable Fix. No generic advice (\"improve clarity\").\n- Each Findings row ties to a Scores row below 5. One dimension may have several findings.\n- Quote or point to the actual text in Location. Format: `\u003Cheading › paragraph or line>`, for example `Rollout › para 2` or `Setup › L41`.\n- For `flag` findings, Fix states what the author must supply or decide, not an invented fact.\n- Do not invent dimension names; use exactly the 20 in the table below.\n\n## Output\n\nPrint exactly two tables, `## Scores` then `## Findings`, with these column names and class values. Other skills parse them.\n\n```markdown\n## Scores\n| Group | Dimension | Score | Missed rule |\n|---|---|---|---|\n| Purpose | Suitability | 4 | \u003Cguideline rule, required when \u003C 5> |\n\n## Findings\n| ID | Dimension | Location | Class | Issue | Fix |\n|---|---|---|---|---|---|\n| F1 | Clarity | Setup › para 2 | apply | \u003Cwhat is wrong> | \u003Cconcrete change> |\n```\n\nScores has 20 rows, grouped in this order. Score is `1-5`, `NA`, or `ERR`; Missed rule is `-` when the score is 5, NA, or ERR.\n\n| Group | Dimensions |\n|---|---|\n| Purpose | Suitability, Scope, Breadth, Depth |\n| Expression | Clarity, Coherence, Concision |\n| Form | Organization, Consistency, Formatting |\n| Reasoning | Discipline, Soundness, Precision, Parsimony |\n| Grounding | Verifiability, Factuality, Relevance |\n| Judgment | Calibration, Fairness, Robustness |\n\nFindings IDs run F1, F2, ... in document order. Class is exactly `apply`, `flag`, or `diagram`. If there are no findings, print the Scores table and a Findings table with header only.\n\nEnd with: \"Run `fix-doc` to apply these findings?\"\n","# Reviewing Docs\n\nReview stage of generate, review, fix. Read the doc, score it against the Practical Prose rubric, and emit a findings table that `fix-doc` consumes. **Change nothing**: no edits to the doc, no side files. Grading is done by you against the rubric; there is no scoring CLI.\n\nInput is a file path or inline text. For inline text, review it the same way; Location uses heading names and paragraph ordinals (\"para 3\") since there are no lines.\n\nReferences, relative to this skill:\n\n- `..\u002F..\u002Freferences\u002Fpprose-rubric.md`: score anchors, NA\u002FERR decision tree, cascades, justified deviations.\n- `..\u002F..\u002Freferences\u002Fpprose-guidelines.md`: the rules cited as \"missed rule\".\n- `..\u002F..\u002Freferences\u002Fcommon-doc-guidelines.md`: structure, style, and Markdown formatting.\n- `..\u002F..\u002Freferences\u002Fdiagrams.md`: when a diagram is warranted.\n- `..\u002F..\u002Freferences\u002Fai-tells.md`: machine-written patterns; report them under Expression or Form.\n\nVendored files keep upstream names in their text: `practical-prose-guidelines.md` is `pprose-guidelines.md`, `practical-prose-rubric.md` is `pprose-rubric.md`, `ai-prose-corrections.md` is `ai-tells.md`. Principles, metrics, and runbooks are not vendored; ignore links to them.\n\n## Steps\n\n1. **Refuse generated files.** If the file carries a `DO NOT EDIT`, `@generated`, or \"generated by\" marker, or sits in a generated-output path, stop. Name the generator or source file and say to review that instead.\n2. **Orient.** Identify the reader, the doc type, the task the reader will do with it, and the risk level. Read the doc in full before scoring. Frontmatter and HTML comments are metadata, not prose defects.\n3. **Score all 20 dimensions** per the decision tree in `pprose-rubric.md`: `NA` if the per-dimension NA anchor fits, `ERR` only for a procedural failure, else 1-5. Honor the cascades (Verifiability to Factuality, Suitability to Relevance, Soundness to Parsimony). For every score below 5, cite the specific guideline rule missed from `pprose-guidelines.md`. A documented justified deviation (see rubric) is not a defect; note it and do not penalize it.\n4. **Check `common-doc-guidelines.md`.** File structure, headings, lists, links, and Markdown formatting problems become Form findings (Organization, Consistency, Formatting). Heading-case and list-punctuation rules yield to the doc's or repo's existing consistent convention; raise only inconsistency.\n5. **Check diagrams** per `diagrams.md`. Where the doc describes architecture, a flow, states, or more than three interacting components in prose and has no figure, add a finding with class `diagram`. Use the dimension the gap hurts most, usually Clarity or Organization.\n6. **Classify each finding** with pprose's apply-vs-flag rule:\n   - `apply`: safe and meaning-preserving. Expression and Form findings, including tells from `ai-tells.md`, whose fix cannot change meaning, claim strength, or scope. `fix-doc` auto-applies these rows.\n   - `flag`: substantive and judgment-bearing. Every Purpose, Reasoning, Grounding, and Judgment finding. Also any Expression or Form finding whose fix would alter meaning, claim strength, or scope (for example, a Concision cut that removes a caveat). Needs the author or new facts; never present as decided.\n   - `diagram`: a figure to add (step 5).\n\n   When a defect fits two classes, file it at the shallowest class that fully fixes it, but a possible meaning change always makes it `flag`. When unsure whether a fix preserves meaning, use `flag`.\n\n## Rules\n\n- **No footer.** Ignore footer-presence criteria when scoring; never mark a dimension NA for that reason. Never raise a footer finding.\n- Every score below 5 has a Missed rule; every finding names a concrete, locatable Fix. No generic advice (\"improve clarity\").\n- Each Findings row ties to a Scores row below 5. One dimension may have several findings.\n- Quote or point to the actual text in Location. Format: `\u003Cheading › paragraph or line>`, for example `Rollout › para 2` or `Setup › L41`.\n- For `flag` findings, Fix states what the author must supply or decide, not an invented fact.\n- Do not invent dimension names; use exactly the 20 in the table below.\n\n## Output\n\nPrint exactly two tables, `## Scores` then `## Findings`, with these column names and class values. Other skills parse them.\n\n```markdown\n## Scores\n| Group | Dimension | Score | Missed rule |\n|---|---|---|---|\n| Purpose | Suitability | 4 | \u003Cguideline rule, required when \u003C 5> |\n\n## Findings\n| ID | Dimension | Location | Class | Issue | Fix |\n|---|---|---|---|---|---|\n| F1 | Clarity | Setup › para 2 | apply | \u003Cwhat is wrong> | \u003Cconcrete change> |\n```\n\nScores has 20 rows, grouped in this order. Score is `1-5`, `NA`, or `ERR`; Missed rule is `-` when the score is 5, NA, or ERR.\n\n| Group | Dimensions |\n|---|---|\n| Purpose | Suitability, Scope, Breadth, Depth |\n| Expression | Clarity, Coherence, Concision |\n| Form | Organization, Consistency, Formatting |\n| Reasoning | Discipline, Soundness, Precision, Parsimony |\n| Grounding | Verifiability, Factuality, Relevance |\n| Judgment | Calibration, Fairness, Robustness |\n\nFindings IDs run F1, F2, ... in document order. Class is exactly `apply`, `flag`, or `diagram`. If there are no findings, print the Scores table and a Findings table with header only.\n\nEnd with: \"Run `fix-doc` to apply these findings?\"\n",{"name":5,"description":7},"main","a3f19bcc313571bff79dca391a83f9c4d38bb335","technical-writing\u002Fskills\u002Freview-doc",0,"https:\u002F\u002Fgithub.com\u002Fozzycodes2\u002Fclaudellum","https:\u002F\u002Fgithub.com\u002Fozzycodes2","Software Engineer | Engineering Manager | AI whisperer | ☕Enjoyer","2026-11-14 04:50:11",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add ozzycodes2\u002Fclaudellum --skill review-doc",{"tool":38,"command":39},"bunx","bunx skills add ozzycodes2\u002Fclaudellum --skill review-doc",{"tool":41,"command":42},"pnpm","pnpm dlx skills add ozzycodes2\u002Fclaudellum --skill review-doc","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fozzycodes2\u002Fclaudellum\u002Fblob\u002Fmain\u002Ftechnical-writing\u002Fskills\u002Freview-doc\u002FSKILL.md",true,[],[47,54,61,68,75,82],{"skillNo":48,"name":49,"nameZh":6,"description":50,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":51,"categories":52,"keywords":53,"publishedAt":19},"01M7ASQB3CTKMKDNAXD9DCF1YC","writing-design-docs","Use when the user wants to write a problem-statement design doc, says \"let's plan a feature properly\" \u002F \"write a design doc\" \u002F \"I'm thinking about how to do X\" for a non-trivial X, or before committing to a non-obvious technical direction","https:\u002F\u002Fgithub.com\u002Fozzycodes2\u002Fclaudellum\u002Fblob\u002Fmain\u002Ftechnical-writing\u002Fskills\u002Fwriting-design-docs\u002FSKILL.md",[],[],{"skillNo":55,"name":56,"nameZh":6,"description":57,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":58,"categories":59,"keywords":60,"publishedAt":19},"01M7ASQ6JD4QRV5ZKK2QME401Y","write-doc","Use when the user asks to write or draft a README, ADR, runbook, tutorial, how-to, explanation, or reference doc, or a caller passes \"type ADR\" or \"type README\". Picks the type, fills a template, adds diagrams. RFCs and design docs belong to writing-design-docs.","https:\u002F\u002Fgithub.com\u002Fozzycodes2\u002Fclaudellum\u002Fblob\u002Fmain\u002Ftechnical-writing\u002Fskills\u002Fwrite-doc\u002FSKILL.md",[],[],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":19},"01M7ASPWST208JZNR7HF7J6KMV","fix-doc","Use when the user asks to fix, edit for prose quality, polish, tighten, humanize, or de-slop a Markdown doc or pasted text, or says \"make this read less AI\". Applies review-doc findings, generates flagged diagrams, lists substantive issues for the author, then runs the AI-tell pass last. Modifies the target.","https:\u002F\u002Fgithub.com\u002Fozzycodes2\u002Fclaudellum\u002Fblob\u002Fmain\u002Ftechnical-writing\u002Fskills\u002Ffix-doc\u002FSKILL.md",[],[],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":19},"01M7ASPS6Y9ZGK9KCDHNPDR75A","create-slides","Use when the user asks for a slide deck, presentation, talk, or slides from a document, report, PR, notes, or topic. Builds one self-contained Machinify-branded HTML deck in a minimalist style, with headline-plus-visual slides, speaker notes, and every diagram drawn by architecture-design:create-diagram.","https:\u002F\u002Fgithub.com\u002Fozzycodes2\u002Fclaudellum\u002Fblob\u002Fmain\u002Ftechnical-writing\u002Fskills\u002Fcreate-slides\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":19},"01M7ASPAKFY045KHR92Y4QFTWV","start-session","Open a Claude Code working session in a fresh, isolated git worktree, so the user can start a task with a single \u002Fstart-session \u003Cname>. Use at the START of a session when the user says \"start session\", \"start a worktree\", \"spin up a worktree for ABC-123\", \"begin work on \u003Cticket>\", or passes a name\u002Fticket to work under. Creates and ENTERS a worktree via the EnterWorktree tool (never `git worktree add`) under .claude\u002Fworktrees\u002F, named exactly after the argument, on a local branch `worktree-\u003Cargument>`. Reports what the worktree inherited (`.worktreeinclude` copies, symlinked node_modules) and whether its `.env` still points at the main checkout's stack. If the argument is a JIRA key (e.g. ABC-123, PROJ-1505), also loads that story with the Atlassian CLI (`acli`) when available and summarizes the implementation ask. Also renames the session to the argument (the same effect as `\u002Frename \u003CNAME>`) so it's easy to find in `\u002Fresume`. Then stops and waits — it sets up the workspace and context, it does not implement.","https:\u002F\u002Fgithub.com\u002Fozzycodes2\u002Fclaudellum\u002Fblob\u002Fmain\u002Fsession-mgmt\u002Fskills\u002Fstart-session\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":19},"01M7ASNSKFMMXSG954AEMW8HAZ","exit-session","Tear down the ephemeral resources a Claude Code working session created, then quit the CLI — so the user can wrap up with a single \u002Fexit-session. Use when the user says \"exit session\", \"clean up this session\", \"tear down everything\", \"wrap up and clean up resources\", \"remove the worktree and scratch\", \"stop the background processes\", \"shut down the stack\", \"clean up the agent worktrees\", or asks to clean up after finishing a task — even if they only name one resource (assume they want the full sweep unless they scope it). Runs teardown permission-free: stops background processes and dev servers, Docker\u002Fcompose stacks plus their volumes, networks and images, local Tilt\u002FKubernetes, git worktrees, merged local branches, and temp\u002Fscratch files without prompting, then exits the CLI. Covers the worktrees and Docker resources left behind by subagents spawned during the session, not just the primary agent's own worktree — both determined from git locks and Docker labels rather than from recall. Never touches resources a still-live session holds.","https:\u002F\u002Fgithub.com\u002Fozzycodes2\u002Fclaudellum\u002Fblob\u002Fmain\u002Fsession-mgmt\u002Fskills\u002Fexit-session\u002FSKILL.md",[],[]]