[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M757S955SHFNBEWX7WKYTY94":3,"skill-same:01M757S955SHFNBEWX7WKYTY94":91},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"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":6,"ownerDescription":29,"updatedAt":30,"install":31,"resources":44},"01M757S955SHFNBEWX7WKYTY94","bmad-review",null,"Multi-lens review over any diff, doc, spec, or artifact — whichever installed lenses fit the content, run singly or together. Shipped lenses include adversarial, edge-case, verification-gap, structure, and prose. Use when the user says \"review this\", \"critical review\", \"editorial review\", \"hunt edge cases\", \"review the structure\", or \"review the prose\".","SevWren\u002FDaily-Motivation-Brain-Helper","SevWren","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F4411791?v=4","01M757KRED8NN6CAZAHKC73C6K","01M757KRFHMA61WJTBVGCAPXS0",1,"MIT","https:\u002F\u002Fgithub.com\u002FSevWren\u002FDaily-Motivation-Brain-Helper\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fbmad-review\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: bmad-review\ndescription: 'Multi-lens review over any diff, doc, spec, or artifact — whichever installed lenses fit the content, run singly or together. Shipped lenses include adversarial, edge-case, verification-gap, structure, and prose. Use when the user says \"review this\", \"critical review\", \"editorial review\", \"hunt edge cases\", \"review the structure\", or \"review the prose\".'\n---\n\n# BMad Review\n\nReview content through lenses — each a distinct method and stance — and report findings in one canonical shape. Report what is real — never pad to look thorough. Each lens sets its own stance toward the content and toward zero findings: for most an empty result is valid; the adversarial lens requires at least ten concrete findings and treats an empty list as a signal to re-check; the editorial lenses hold content sacrosanct and critique only how it is organized and expressed.\n\nThe lens set is whatever `{workflow.lenses}` resolves to, not a fixed list — overrides add lenses and replace shipped ones. Never claim a capability from this file; read the resolved lenses and work from those.\n\n## Inputs\n\n- **content** — what to review: a diff, branch, uncommitted changes, file, spec, story, or any document. Args: `[path]`.\n- **lenses** (optional) — one or more lens codes or names, however the caller expresses them: a spoken request, or a directive of the form `skill:bmad-review lenses=\u003Ccode>[,\u003Ccode>...]` (the form bmm's `doc_standards` uses). Default: every applicable lens (a full review).\n- **also_consider** (optional) — areas to keep in mind alongside each lens's normal analysis.\n- **pre-resolved customization** (optional) — `[workflow]` field values supplied by a forwarding caller. See Execution step 1.\n\n## Conventions\n\n- Bare paths (e.g. `references\u002Flens-edge-case-hunter.md`) resolve from `{skill-root}` — this skill's installed directory, where `customize.toml` lives. `{project-root}` resolves to the project working directory.\n- `{workflow.\u003Cname>}` resolves to fields in `customize.toml`'s `[workflow]` table (overrides win per BMad merge rules).\n- In `style_guide`, `review_guidance`, and `persistent_facts`, a value prefixed `file:` is a path or glob — load that file's contents. If a `file:` value cannot be read, name the failed file in the output header and continue: the shipped baseline for `style_guide`, the remaining entries otherwise.\n\n## Execution\n\n1. **Resolve customization:** `uv run {project-root}\u002F_bmad\u002Fscripts\u002Fresolve_customization.py --skill {skill-root} --key workflow`. On failure, read `{skill-root}\u002Fcustomize.toml` directly and use defaults. **Forwarded activation:** if a caller invoked you with pre-resolved customization fields (e.g. the `bmad-editorial-review` shim), honor them verbatim for those named fields — they already carry the user's overrides — and resolve only the remaining fields from your own `customize.toml`. Then execute each `{workflow.activation_steps_prepend}` entry in order, hold `{workflow.persistent_facts}` as standing context for the session, and treat `{workflow.review_guidance}` entries as standing review directives for every lens.\n2. **Load the content.** If it is empty or cannot be decoded as text: when the caller expects the raw findings JSON array (e.g. the legacy edge-case forwarder), return `[{\"location\":\"N\u002FA\",\"trigger_condition\":\"Input empty or undecodable\",\"guard_snippet\":\"Provide valid content to review\",\"potential_consequence\":\"Review skipped — no analysis performed\"}]` (no `lens` field) and stop; otherwise say what's wrong and ask for reviewable content. Classify the content — diff, source file, function, or document — and whether it is **code** or **docs**; scope rules and lens applicability both depend on it. A document that defines behavior (spec, requirements, plan, story) is `docs` that a behavioral lens may still apply to; judge by `when`.\n3. **Select lenses** from `{workflow.lenses}`. A lens with an empty `instruction` is disabled. If the user or caller named lenses, run exactly those only — `applies_to` and `when` do not filter an explicit request. Otherwise run every enabled lens whose `applies_to` covers the content class (`any` always covers) and whose `when` applies.\n4. **Announce the plan** in one line before running anything: the content class, the lenses about to run, and — when any lens has `after` set — that it runs on top of the named lens's findings. Skip the announcement entirely when the caller pinned an exact output contract (the legacy forwarders that demand raw JSON or one exact line) — their contract covers everything you emit, not just the findings block. Then execute each `{workflow.activation_steps_append}` entry in order.\n5. **Run the independent lenses** — every selected lens without `after`. Each sees the content and `also_consider`, never another lens's findings. Follow each lens's `instruction`; the shipped lenses load their reference file just-in-time, so load only what runs. When subagents are available, spawn one per lens in parallel: give it the lens `instruction` with `{skill-root}` and paths resolved absolute, the content or where to read it, any `also_consider` areas, the standing review directives, and the constraint \"Return ONLY your findings — no other output.\" Otherwise run the lenses sequentially yourself, completing one before starting the next.\n6. **Run the dependent lenses** — every selected lens with `after`, once the lens it names has completed, passing that lens's findings in. A lens whose `after` target was not selected or produced nothing still runs, with no prior findings. Dependent lenses that name different targets are independent of each other and may run in parallel.\n7. **Assemble and present** per Output below. Keep every lens's findings — overlap between lenses is signal, not duplication; note it in the markdown report rather than deduping. Execute `{workflow.on_complete}` if set.\n\n## Output\n\nOne JSON array holding every finding from every lens. Each finding carries:\n\n- `lens` — the code of the lens that produced it\n- `location` — where in the content (file:line-range for code, section for documents)\n- `trigger_condition` — the problem, or the condition that exposes it, in one line\n- `guard_snippet` — the concrete fix, guard, or missing check\n- `potential_consequence` — what goes wrong if it ships as-is\n\nEach lens file refines these semantics for its findings and may add lens-specific fields (e.g. `kind`\u002F`confidence` on deletion findings, `gap_shape`\u002F`consumer`\u002F`evidence` on verification-gap findings). A lens file may instead declare its own findings shape and rendering — the editorial lenses render a findings table — and that shape wins for that lens's findings. `[]` is valid when nothing is found. No severity, priority, or ranking anywhere.\n\nPresent per `{workflow.output_format}` — `\"json\"` (the raw array in a fenced json block), `\"markdown\"`, or `\"both\"` — unless the caller requested a specific shape; a legacy forwarder's output contract always wins, and governs everything you emit rather than the findings block alone. The markdown report groups findings by lens, each rendered in its declared shape: a short block per finding rendering the fields plus any extras worth surfacing, one line for a lens that found nothing, and a plain clean statement when the whole review is clean. Shape the report per `{workflow.output_preferences}`.\n\nWhen `{workflow.report_path}` is set, write the report there; otherwise present it in chat.\n","# BMad Review\n\nReview content through lenses — each a distinct method and stance — and report findings in one canonical shape. Report what is real — never pad to look thorough. Each lens sets its own stance toward the content and toward zero findings: for most an empty result is valid; the adversarial lens requires at least ten concrete findings and treats an empty list as a signal to re-check; the editorial lenses hold content sacrosanct and critique only how it is organized and expressed.\n\nThe lens set is whatever `{workflow.lenses}` resolves to, not a fixed list — overrides add lenses and replace shipped ones. Never claim a capability from this file; read the resolved lenses and work from those.\n\n## Inputs\n\n- **content** — what to review: a diff, branch, uncommitted changes, file, spec, story, or any document. Args: `[path]`.\n- **lenses** (optional) — one or more lens codes or names, however the caller expresses them: a spoken request, or a directive of the form `skill:bmad-review lenses=\u003Ccode>[,\u003Ccode>...]` (the form bmm's `doc_standards` uses). Default: every applicable lens (a full review).\n- **also_consider** (optional) — areas to keep in mind alongside each lens's normal analysis.\n- **pre-resolved customization** (optional) — `[workflow]` field values supplied by a forwarding caller. See Execution step 1.\n\n## Conventions\n\n- Bare paths (e.g. `references\u002Flens-edge-case-hunter.md`) resolve from `{skill-root}` — this skill's installed directory, where `customize.toml` lives. `{project-root}` resolves to the project working directory.\n- `{workflow.\u003Cname>}` resolves to fields in `customize.toml`'s `[workflow]` table (overrides win per BMad merge rules).\n- In `style_guide`, `review_guidance`, and `persistent_facts`, a value prefixed `file:` is a path or glob — load that file's contents. If a `file:` value cannot be read, name the failed file in the output header and continue: the shipped baseline for `style_guide`, the remaining entries otherwise.\n\n## Execution\n\n1. **Resolve customization:** `uv run {project-root}\u002F_bmad\u002Fscripts\u002Fresolve_customization.py --skill {skill-root} --key workflow`. On failure, read `{skill-root}\u002Fcustomize.toml` directly and use defaults. **Forwarded activation:** if a caller invoked you with pre-resolved customization fields (e.g. the `bmad-editorial-review` shim), honor them verbatim for those named fields — they already carry the user's overrides — and resolve only the remaining fields from your own `customize.toml`. Then execute each `{workflow.activation_steps_prepend}` entry in order, hold `{workflow.persistent_facts}` as standing context for the session, and treat `{workflow.review_guidance}` entries as standing review directives for every lens.\n2. **Load the content.** If it is empty or cannot be decoded as text: when the caller expects the raw findings JSON array (e.g. the legacy edge-case forwarder), return `[{\"location\":\"N\u002FA\",\"trigger_condition\":\"Input empty or undecodable\",\"guard_snippet\":\"Provide valid content to review\",\"potential_consequence\":\"Review skipped — no analysis performed\"}]` (no `lens` field) and stop; otherwise say what's wrong and ask for reviewable content. Classify the content — diff, source file, function, or document — and whether it is **code** or **docs**; scope rules and lens applicability both depend on it. A document that defines behavior (spec, requirements, plan, story) is `docs` that a behavioral lens may still apply to; judge by `when`.\n3. **Select lenses** from `{workflow.lenses}`. A lens with an empty `instruction` is disabled. If the user or caller named lenses, run exactly those only — `applies_to` and `when` do not filter an explicit request. Otherwise run every enabled lens whose `applies_to` covers the content class (`any` always covers) and whose `when` applies.\n4. **Announce the plan** in one line before running anything: the content class, the lenses about to run, and — when any lens has `after` set — that it runs on top of the named lens's findings. Skip the announcement entirely when the caller pinned an exact output contract (the legacy forwarders that demand raw JSON or one exact line) — their contract covers everything you emit, not just the findings block. Then execute each `{workflow.activation_steps_append}` entry in order.\n5. **Run the independent lenses** — every selected lens without `after`. Each sees the content and `also_consider`, never another lens's findings. Follow each lens's `instruction`; the shipped lenses load their reference file just-in-time, so load only what runs. When subagents are available, spawn one per lens in parallel: give it the lens `instruction` with `{skill-root}` and paths resolved absolute, the content or where to read it, any `also_consider` areas, the standing review directives, and the constraint \"Return ONLY your findings — no other output.\" Otherwise run the lenses sequentially yourself, completing one before starting the next.\n6. **Run the dependent lenses** — every selected lens with `after`, once the lens it names has completed, passing that lens's findings in. A lens whose `after` target was not selected or produced nothing still runs, with no prior findings. Dependent lenses that name different targets are independent of each other and may run in parallel.\n7. **Assemble and present** per Output below. Keep every lens's findings — overlap between lenses is signal, not duplication; note it in the markdown report rather than deduping. Execute `{workflow.on_complete}` if set.\n\n## Output\n\nOne JSON array holding every finding from every lens. Each finding carries:\n\n- `lens` — the code of the lens that produced it\n- `location` — where in the content (file:line-range for code, section for documents)\n- `trigger_condition` — the problem, or the condition that exposes it, in one line\n- `guard_snippet` — the concrete fix, guard, or missing check\n- `potential_consequence` — what goes wrong if it ships as-is\n\nEach lens file refines these semantics for its findings and may add lens-specific fields (e.g. `kind`\u002F`confidence` on deletion findings, `gap_shape`\u002F`consumer`\u002F`evidence` on verification-gap findings). A lens file may instead declare its own findings shape and rendering — the editorial lenses render a findings table — and that shape wins for that lens's findings. `[]` is valid when nothing is found. No severity, priority, or ranking anywhere.\n\nPresent per `{workflow.output_format}` — `\"json\"` (the raw array in a fenced json block), `\"markdown\"`, or `\"both\"` — unless the caller requested a specific shape; a legacy forwarder's output contract always wins, and governs everything you emit rather than the findings block alone. The markdown report groups findings by lens, each rendered in its declared shape: a short block per finding rendering the fields plus any extras worth surfacing, one line for a lens that found nothing, and a plain clean statement when the whole review is clean. Shape the report per `{workflow.output_preferences}`.\n\nWhen `{workflow.report_path}` is set, write the report there; otherwise present it in chat.\n",{"name":5,"description":7},"main","b469548b8e522c5d7fbf5e126591af14e0dc3744",".claude\u002Fskills\u002Fbmad-review",0,"https:\u002F\u002Fgithub.com\u002FSevWren\u002FDaily-Motivation-Brain-Helper","https:\u002F\u002Fgithub.com\u002FSevWren","Mindset:  Improving yourself one day at a time -> made possible by utilizing today's technologies to fit your individual needs.","2026-10-25 09:39:17",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add SevWren\u002FDaily-Motivation-Brain-Helper --skill bmad-review",{"tool":37,"command":38},"bunx","bunx skills add SevWren\u002FDaily-Motivation-Brain-Helper --skill bmad-review",{"tool":40,"command":41},"pnpm","pnpm dlx skills add SevWren\u002FDaily-Motivation-Brain-Helper --skill bmad-review","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FSevWren\u002FDaily-Motivation-Brain-Helper\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fbmad-review\u002FSKILL.md",true,[45,51,57,61,65,69,73,77,81,87],{"path":46,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":49,"sourceHtmlUrl":50},"customize.toml","OTHER","其他",5903,"https:\u002F\u002Fgithub.com\u002FSevWren\u002FDaily-Motivation-Brain-Helper\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fbmad-review\u002Fcustomize.toml",{"path":52,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":55,"sourceHtmlUrl":56},"references\u002Feditorial-common.md","REFERENCE","参考文档",5811,"https:\u002F\u002Fgithub.com\u002FSevWren\u002FDaily-Motivation-Brain-Helper\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fbmad-review\u002Freferences\u002Feditorial-common.md",{"path":58,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":59,"sourceHtmlUrl":60},"references\u002Flens-adversarial.md",779,"https:\u002F\u002Fgithub.com\u002FSevWren\u002FDaily-Motivation-Brain-Helper\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fbmad-review\u002Freferences\u002Flens-adversarial.md",{"path":62,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":63,"sourceHtmlUrl":64},"references\u002Flens-edge-case-hunter.md",3845,"https:\u002F\u002Fgithub.com\u002FSevWren\u002FDaily-Motivation-Brain-Helper\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fbmad-review\u002Freferences\u002Flens-edge-case-hunter.md",{"path":66,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":67,"sourceHtmlUrl":68},"references\u002Flens-prose.md",1354,"https:\u002F\u002Fgithub.com\u002FSevWren\u002FDaily-Motivation-Brain-Helper\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fbmad-review\u002Freferences\u002Flens-prose.md",{"path":70,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":71,"sourceHtmlUrl":72},"references\u002Flens-structure.md",1582,"https:\u002F\u002Fgithub.com\u002FSevWren\u002FDaily-Motivation-Brain-Helper\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fbmad-review\u002Freferences\u002Flens-structure.md",{"path":74,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":75,"sourceHtmlUrl":76},"references\u002Flens-verification-gap.md",9518,"https:\u002F\u002Fgithub.com\u002FSevWren\u002FDaily-Motivation-Brain-Helper\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fbmad-review\u002Freferences\u002Flens-verification-gap.md",{"path":78,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":79,"sourceHtmlUrl":80},"references\u002Fstructure-models.md",1972,"https:\u002F\u002Fgithub.com\u002FSevWren\u002FDaily-Motivation-Brain-Helper\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fbmad-review\u002Freferences\u002Fstructure-models.md",{"path":82,"resourceType":83,"resourceTypeDesc":84,"sizeBytes":85,"sourceHtmlUrl":86},"scripts\u002Ftests\u002Ftest_word_metrics.py","SCRIPT","脚本",1556,"https:\u002F\u002Fgithub.com\u002FSevWren\u002FDaily-Motivation-Brain-Helper\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fbmad-review\u002Fscripts\u002Ftests\u002Ftest_word_metrics.py",{"path":88,"resourceType":83,"resourceTypeDesc":84,"sizeBytes":89,"sourceHtmlUrl":90},"scripts\u002Fword_metrics.py",3441,"https:\u002F\u002Fgithub.com\u002FSevWren\u002FDaily-Motivation-Brain-Helper\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fbmad-review\u002Fscripts\u002Fword_metrics.py",[92,99,106,113,120,127],{"skillNo":93,"name":94,"nameZh":6,"description":95,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":96,"categories":97,"keywords":98,"publishedAt":18},"01M757YEXC4V515X48TR4A7FW3","repo-doc-audit","Performs a comprehensive Repository Documentation Audit and Governance Standard (RDAGS) against an entire codebase. Use this skill whenever the user wants to audit, evaluate, or assess repository documentation — including requests like \"audit my repo docs\", \"find doc inconsistencies\", \"check for documentation drift\", \"governance review\", \"find dead or orphan knowledge\", \"check my CLAUDE.md or AGENTS.md for accuracy\", or any systematic documentation quality evaluation. Always trigger this skill when the user asks to run a documentation audit or governance review, even if they describe only part of the standard (e.g., \"check traceability\" or \"find contradictions in my docs\"). Produces five output files: Repository-Audit-Report.md (full 18-section report) plus Direct-Contradictions.md, Semantic-Contradictions.md, Traceability-Failures.md, and Proposed-Repository-Governance-Improvements.md as standalone action-oriented findings documents.","https:\u002F\u002Fgithub.com\u002FSevWren\u002FDaily-Motivation-Brain-Helper\u002Fblob\u002Fmain\u002FCLAUDE\u002Fskills\u002Frepo-doc-audit\u002FSKILL.md",[],[],{"skillNo":100,"name":101,"nameZh":6,"description":102,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":103,"categories":104,"keywords":105,"publishedAt":18},"01M757YCKK0QMK7JRZFPMXTGN4","writing-great-skills","Reference for writing and editing skills well — the vocabulary and principles that make a skill predictable.","https:\u002F\u002Fgithub.com\u002FSevWren\u002FDaily-Motivation-Brain-Helper\u002Fblob\u002Fmain\u002FCLAUDE\u002Fskills\u002Fproductivity\u002Fwriting-great-skills\u002FSKILL.md",[],[],{"skillNo":107,"name":108,"nameZh":6,"description":109,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":110,"categories":111,"keywords":112,"publishedAt":18},"01M757Y8AM0HGTW50KFG5MWCRD","write-a-skill","Create new agent skills with proper structure, progressive disclosure, and bundled resources. Use when user wants to create, write, or build a new skill.","https:\u002F\u002Fgithub.com\u002FSevWren\u002FDaily-Motivation-Brain-Helper\u002Fblob\u002Fmain\u002FCLAUDE\u002Fskills\u002Fproductivity\u002Fwrite-a-skill\u002FSKILL.md",[],[],{"skillNo":114,"name":115,"nameZh":6,"description":116,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":117,"categories":118,"keywords":119,"publishedAt":18},"01M757Y5RN0J4Y7XQQKSR8Z7D3","teach","Teach the user a new skill or concept, within this workspace.","https:\u002F\u002Fgithub.com\u002FSevWren\u002FDaily-Motivation-Brain-Helper\u002Fblob\u002Fmain\u002FCLAUDE\u002Fskills\u002Fproductivity\u002Fteach\u002FSKILL.md",[],[],{"skillNo":121,"name":122,"nameZh":6,"description":123,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":124,"categories":125,"keywords":126,"publishedAt":18},"01M757Y0R3DYWN3D07TKJWXDMD","self-reflect","Enterprise-grade forensic self-reflection over recent git history. Multi-axis audit with pass\u002Ffail gates, mandate compliance matrix, platform drift forensics, test quality review, and ranked generation constraints.","https:\u002F\u002Fgithub.com\u002FSevWren\u002FDaily-Motivation-Brain-Helper\u002Fblob\u002Fmain\u002FCLAUDE\u002Fskills\u002Fproductivity\u002Fself-reflect\u002FSKILL.md",[],[],{"skillNo":128,"name":129,"nameZh":6,"description":130,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":131,"categories":132,"keywords":133,"publishedAt":18},"01M757XYVBYVHJPP46YNDQGJER","handoff","Compact the current conversation into a handoff document for another agent to pick up.","https:\u002F\u002Fgithub.com\u002FSevWren\u002FDaily-Motivation-Brain-Helper\u002Fblob\u002Fmain\u002FCLAUDE\u002Fskills\u002Fproductivity\u002Fhandoff\u002FSKILL.md",[],[]]