[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M79CZ18942RE82RFFC6ZDCGA":3,"skill-same:01M79CZ18942RE82RFFC6ZDCGA":64},{"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":25,"commitSha":26,"skillDirectory":27,"forksCount":28,"repositoryHtmlUrl":29,"repositoryHomepageUrl":6,"ownerHtmlUrl":30,"ownerBlogUrl":6,"ownerDescription":31,"updatedAt":32,"install":33,"resources":45},"01M79CZ18942RE82RFFC6ZDCGA","improve-repo-harness",null,"Harness: MUST invoke only when a user explicitly asks to assess or improve agent guidance, repository navigation, validation discoverability, bootstrap documentation, or CONTEXT\u002FADR conventions. Do not invoke autonomously.","JanMichaelSE\u002Fagentic-marketplace","JanMichaelSE","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F55473580?v=4","01M79CW862FGHY91NG8DDRRFJC","Jan M Montalvo","01M79CW86M2NJQNRZ41VP9AJ51",1,"Apache-2.0","https:\u002F\u002Fgithub.com\u002FJanMichaelSE\u002Fagentic-marketplace\u002Fblob\u002Fmain\u002Fplugins\u002Fexperimental\u002Fskills\u002Fimprove-repo-harness\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: improve-repo-harness\ndescription: \"Harness: MUST invoke only when a user explicitly asks to assess or improve agent guidance, repository navigation, validation discoverability, bootstrap documentation, or CONTEXT\u002FADR conventions. Do not invoke autonomously.\"\ndisable-model-invocation: true\n---\n\n# Improve Repo Harness\n\n**Harness** durable repository guidance so an agent can orient itself, find\ngoverning documents, and discover supported validation and bootstrap surfaces.\nMake small, evidence-based improvements; the repository remains the source of\ntruth for its own structure and conventions.\n\n## Scope\n\nThis skill improves durable, repository-local guidance. It does not author a\ndomain model or architecture decisions. Route material domain-model work to\n[domain-modeling](..\u002F..\u002F..\u002Fsoftware-architecture\u002Fskills\u002Fdomain-modeling\u002FSKILL.md).\n\n## Process\n\n### 1. Explore the existing harness\n\nRead the existing agent front door, repository README and documentation index,\nnearby contribution guidance, build or validation entry points, and enough\nsource and test structure to understand current navigation. Inspect existing\n`GLOSSARY.md` \u002F `GLOSSARY-MAP.md` or `CONTEXT.md` \u002F `CONTEXT-MAP.md`, ADR\nlocations, and requirements or design documents only as evidence of established conventions.\n\nRecord the paths and concise observations that support each possible\nrecommendation. Consult [HARNESS-RUBRIC.md](HARNESS-RUBRIC.md) for the evidence\nto collect for all five sections.\n\n**Completion criterion:** You can cite repository-local evidence for every\nrecommendation, and have identified any section with insufficient evidence.\n\n### 2. Review sections one at a time\n\nPresent the following sections in order. For the current section, show the\nobserved evidence, the smallest recommendation, and its benefit. Ask the user\nto **adopt**, **skip**, or **revise** that recommendation, then wait for the\nanswer before presenting the next section.\n\n#### Front door\n\nAssess whether the existing agent guidance clearly points to durable rules,\ndocumentation, and safe validation entry points. Preserve its established\nformat and make only the smallest navigation improvement.\n\n#### Navigation and repository map\n\nAssess whether a reader can find the relevant source, tests, documents, and\nentry points from existing guidance. When a concise map is selected, use the\noptional [REPO-MAP-FORMAT.md](REPO-MAP-FORMAT.md) reference rather than\ninventing a repository-wide inventory.\n\n#### Validation and bootstrap\n\nAssess whether existing, documented validation commands and prerequisites are\ndiscoverable. Recommend a documentation change only when concrete repository\nevidence supports it; keep commands and prerequisites owned by their existing\ndocumentation.\n\n#### Domain conventions\n\nAssess whether established glossary\u002Fmap conventions (`GLOSSARY.md` \u002F\n`GLOSSARY-MAP.md` or `CONTEXT.md` \u002F `CONTEXT-MAP.md`) and ADR conventions are\ndiscoverable. Use [DOMAIN-CONVENTIONS.md](DOMAIN-CONVENTIONS.md) to inspect\nand route those conventions. Offer discovery or routing only; route requests\nto define terms or record decisions to `domain-modeling`.\n\n#### Optional small improvements\n\nAssess only small supporting changes justified by the evidence, such as a\nmissing local cross-link or an unclear ownership pointer. Defer broad rewrites\nand proposals without a demonstrated navigation gap.\n\n**Completion criterion:** The user has recorded an adopt, skip, or revise\nchoice for each section; skipped sections have no proposed edit.\n\n### 3. Confirm the selected edits\n\nCombine only adopted or revised recommendations into a concise draft that\nnames the affected files and exact guidance to add or change. Recheck every\nclaim against the evidence, identify any assumption, and ask the user for\nexplicit confirmation before writing.\n\n**Completion criterion:** The user has explicitly confirmed the displayed\ndraft, or the process ends with no changes when nothing is selected.\n\n### 4. Write and validate the confirmed harness\n\nApply only the confirmed local documentation edits, preserving surrounding\nwording and the existing source of truth for each concept. Validate that new\nlinks resolve, referenced paths exist, documented commands were already\nverified in repository materials, and each claim remains supported by the\nexploration evidence.\n\n**Completion criterion:** Every confirmed edit is present, locally valid, and\ntraceable to the user's approved draft and repository evidence.\n\n## Completion\n\nReport the selected sections, changed files, evidence used, validation results,\nand any deferred gaps. State when the repository has no justified harness\nchange rather than filling it with generic guidance.\n","# Improve Repo Harness\n\n**Harness** durable repository guidance so an agent can orient itself, find\ngoverning documents, and discover supported validation and bootstrap surfaces.\nMake small, evidence-based improvements; the repository remains the source of\ntruth for its own structure and conventions.\n\n## Scope\n\nThis skill improves durable, repository-local guidance. It does not author a\ndomain model or architecture decisions. Route material domain-model work to\n[domain-modeling](..\u002F..\u002F..\u002Fsoftware-architecture\u002Fskills\u002Fdomain-modeling\u002FSKILL.md).\n\n## Process\n\n### 1. Explore the existing harness\n\nRead the existing agent front door, repository README and documentation index,\nnearby contribution guidance, build or validation entry points, and enough\nsource and test structure to understand current navigation. Inspect existing\n`GLOSSARY.md` \u002F `GLOSSARY-MAP.md` or `CONTEXT.md` \u002F `CONTEXT-MAP.md`, ADR\nlocations, and requirements or design documents only as evidence of established conventions.\n\nRecord the paths and concise observations that support each possible\nrecommendation. Consult [HARNESS-RUBRIC.md](HARNESS-RUBRIC.md) for the evidence\nto collect for all five sections.\n\n**Completion criterion:** You can cite repository-local evidence for every\nrecommendation, and have identified any section with insufficient evidence.\n\n### 2. Review sections one at a time\n\nPresent the following sections in order. For the current section, show the\nobserved evidence, the smallest recommendation, and its benefit. Ask the user\nto **adopt**, **skip**, or **revise** that recommendation, then wait for the\nanswer before presenting the next section.\n\n#### Front door\n\nAssess whether the existing agent guidance clearly points to durable rules,\ndocumentation, and safe validation entry points. Preserve its established\nformat and make only the smallest navigation improvement.\n\n#### Navigation and repository map\n\nAssess whether a reader can find the relevant source, tests, documents, and\nentry points from existing guidance. When a concise map is selected, use the\noptional [REPO-MAP-FORMAT.md](REPO-MAP-FORMAT.md) reference rather than\ninventing a repository-wide inventory.\n\n#### Validation and bootstrap\n\nAssess whether existing, documented validation commands and prerequisites are\ndiscoverable. Recommend a documentation change only when concrete repository\nevidence supports it; keep commands and prerequisites owned by their existing\ndocumentation.\n\n#### Domain conventions\n\nAssess whether established glossary\u002Fmap conventions (`GLOSSARY.md` \u002F\n`GLOSSARY-MAP.md` or `CONTEXT.md` \u002F `CONTEXT-MAP.md`) and ADR conventions are\ndiscoverable. Use [DOMAIN-CONVENTIONS.md](DOMAIN-CONVENTIONS.md) to inspect\nand route those conventions. Offer discovery or routing only; route requests\nto define terms or record decisions to `domain-modeling`.\n\n#### Optional small improvements\n\nAssess only small supporting changes justified by the evidence, such as a\nmissing local cross-link or an unclear ownership pointer. Defer broad rewrites\nand proposals without a demonstrated navigation gap.\n\n**Completion criterion:** The user has recorded an adopt, skip, or revise\nchoice for each section; skipped sections have no proposed edit.\n\n### 3. Confirm the selected edits\n\nCombine only adopted or revised recommendations into a concise draft that\nnames the affected files and exact guidance to add or change. Recheck every\nclaim against the evidence, identify any assumption, and ask the user for\nexplicit confirmation before writing.\n\n**Completion criterion:** The user has explicitly confirmed the displayed\ndraft, or the process ends with no changes when nothing is selected.\n\n### 4. Write and validate the confirmed harness\n\nApply only the confirmed local documentation edits, preserving surrounding\nwording and the existing source of truth for each concept. Validate that new\nlinks resolve, referenced paths exist, documented commands were already\nverified in repository materials, and each claim remains supported by the\nexploration evidence.\n\n**Completion criterion:** Every confirmed edit is present, locally valid, and\ntraceable to the user's approved draft and repository evidence.\n\n## Completion\n\nReport the selected sections, changed files, evidence used, validation results,\nand any deferred gaps. State when the repository has no justified harness\nchange rather than filling it with generic guidance.\n",{"name":5,"description":7,"disable-model-invocation":24},true,"main","d9e185f133b5cbcd785341095a241d0c64d8310d","plugins\u002Fexperimental\u002Fskills\u002Fimprove-repo-harness",0,"https:\u002F\u002Fgithub.com\u002FJanMichaelSE\u002Fagentic-marketplace","https:\u002F\u002Fgithub.com\u002FJanMichaelSE","Software Developer | B.S. Computer Science ","2026-11-14 06:36:51",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":24},[35,38,41],{"tool":36,"command":37},"npx","npx skills add JanMichaelSE\u002Fagentic-marketplace --skill improve-repo-harness",{"tool":39,"command":40},"bunx","bunx skills add JanMichaelSE\u002Fagentic-marketplace --skill improve-repo-harness",{"tool":42,"command":43},"pnpm","pnpm dlx skills add JanMichaelSE\u002Fagentic-marketplace --skill improve-repo-harness","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FJanMichaelSE\u002Fagentic-marketplace\u002Fblob\u002Fmain\u002Fplugins\u002Fexperimental\u002Fskills\u002Fimprove-repo-harness\u002FSKILL.md",[46,52,56,60],{"path":47,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":50,"sourceHtmlUrl":51},"agents\u002Fopenai.yaml","REFERENCE","参考文档",167,"https:\u002F\u002Fgithub.com\u002FJanMichaelSE\u002Fagentic-marketplace\u002Fblob\u002Fmain\u002Fplugins\u002Fexperimental\u002Fskills\u002Fimprove-repo-harness\u002Fagents\u002Fopenai.yaml",{"path":53,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":54,"sourceHtmlUrl":55},"DOMAIN-CONVENTIONS.md",1581,"https:\u002F\u002Fgithub.com\u002FJanMichaelSE\u002Fagentic-marketplace\u002Fblob\u002Fmain\u002Fplugins\u002Fexperimental\u002Fskills\u002Fimprove-repo-harness\u002FDOMAIN-CONVENTIONS.md",{"path":57,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":58,"sourceHtmlUrl":59},"HARNESS-RUBRIC.md",2093,"https:\u002F\u002Fgithub.com\u002FJanMichaelSE\u002Fagentic-marketplace\u002Fblob\u002Fmain\u002Fplugins\u002Fexperimental\u002Fskills\u002Fimprove-repo-harness\u002FHARNESS-RUBRIC.md",{"path":61,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":62,"sourceHtmlUrl":63},"REPO-MAP-FORMAT.md",1444,"https:\u002F\u002Fgithub.com\u002FJanMichaelSE\u002Fagentic-marketplace\u002Fblob\u002Fmain\u002Fplugins\u002Fexperimental\u002Fskills\u002Fimprove-repo-harness\u002FREPO-MAP-FORMAT.md",[65,72,79,86,93,100],{"skillNo":66,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":71,"publishedAt":19},"01M79D1SP72BJKFZDHH2W0VT9G","ui-ux-pro-max","UI\u002FUX design intelligence for web and mobile. Local database with 79 searchable styles (88 catalog entries), 192 color palettes, 74 font pairings, 192 product types, 119 UX guidelines, 105 curated icon entries, 17 GSAP motion presets, and 25 chart types across 22 stacks (React, Next.js, Vue, Nuxt, Svelte, Astro, SwiftUI, React Native, Flutter, Tailwind, shadcn\u002Fui, Jetpack Compose, Angular, Laravel, JavaFX, WPF, WinUI, Avalonia, Uno Platform, UWP, Three.js, and HTML\u002FCSS). Use when designing, building, or reviewing UI: pages, components, color schemes, typography, layout, accessibility, animation, or data visualization.","https:\u002F\u002Fgithub.com\u002FJanMichaelSE\u002Fagentic-marketplace\u002Fblob\u002Fmain\u002Fplugins\u002Fui-ux\u002Fskills\u002Fui-ux-pro-max\u002FSKILL.md",[],[],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":19},"01M79D1NPRNKYC0GNSPQBG02AD","figma-mcp","Implement or compare UI against Figma designs using an available Figma MCP integration. Use for Figma-backed implementation, design-token extraction, or visual-parity gap analysis; Figma MCP access is optional and must already be configured by the user.","https:\u002F\u002Fgithub.com\u002FJanMichaelSE\u002Fagentic-marketplace\u002Fblob\u002Fmain\u002Fplugins\u002Fui-ux\u002Fskills\u002Ffigma-mcp\u002FSKILL.md",[],[],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":19},"01M79D1HW8E8EBKHYD0VRPAGDB","improve-codebase-architecture","Find evidence-based, active-change architecture improvements using shared design and domain-modeling guidance. Use when a user wants to reduce architectural friction, deepen a module, or make a current change safer, more testable, and easier to navigate.","https:\u002F\u002Fgithub.com\u002FJanMichaelSE\u002Fagentic-marketplace\u002Fblob\u002Fmain\u002Fplugins\u002Fsoftware-architecture\u002Fskills\u002Fimprove-codebase-architecture\u002FSKILL.md",[],[],{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":19},"01M79D1E9DJ22BZN68FGNEY6H9","domain-modeling","Build and sharpen a project's domain model. Use when discussing codebase terminology, writing or editing GLOSSARY.md or CONTEXT.md, or recording or editing an ADR.","https:\u002F\u002Fgithub.com\u002FJanMichaelSE\u002Fagentic-marketplace\u002Fblob\u002Fmain\u002Fplugins\u002Fsoftware-architecture\u002Fskills\u002Fdomain-modeling\u002FSKILL.md",[],[],{"skillNo":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":97,"categories":98,"keywords":99,"publishedAt":19},"01M79D1BWY6DT3SDNRVRJV73PH","codebase-design","Provide the shared vocabulary and discipline for designing deep modules with clear interfaces and seams. Use when a user wants to design or improve a module, find deepening opportunities, choose a seam, or make code more testable and AI-navigable.","https:\u002F\u002Fgithub.com\u002FJanMichaelSE\u002Fagentic-marketplace\u002Fblob\u002Fmain\u002Fplugins\u002Fsoftware-architecture\u002Fskills\u002Fcodebase-design\u002FSKILL.md",[],[],{"skillNo":101,"name":102,"nameZh":6,"description":103,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":104,"categories":105,"keywords":106,"publishedAt":19},"01M79D176DSM0779MS5PCW022A","test-coverage-review","MUST invoke to review whether added or updated tests cover code changes in a diff. Checks new logic, branches, error paths, and regression risk, producing a change-to-test matrix. Use requirements-to-tests-traceability for acceptance-criteria mapping and orchestrated-review for bundled reviews.","https:\u002F\u002Fgithub.com\u002FJanMichaelSE\u002Fagentic-marketplace\u002Fblob\u002Fmain\u002Fplugins\u002Freview-toolkit\u002Fskills\u002Ftest-coverage-review\u002FSKILL.md",[],[]]