[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M73B6DAS71JY33H0J64NNP4D":3,"skill-same:01M73B6DAS71JY33H0J64NNP4D":89},{"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":26,"commitSha":27,"skillDirectory":28,"forksCount":29,"repositoryHtmlUrl":30,"repositoryHomepageUrl":6,"ownerHtmlUrl":31,"ownerBlogUrl":32,"ownerDescription":33,"updatedAt":34,"install":35,"resources":48},"01M73B6DAS71JY33H0J64NNP4D","beautify-github-readme",null,"Use when improving a GitHub repository README visually, creating GitHub-safe README SVG assets, or auditing README presentation; not general website UI or ordinary documentation maintenance.","TrebuchetDynamics\u002Fpi-toolset","TrebuchetDynamics","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F131306559?v=4","01M73B3AA92AQHVRYPW64WJSZ5","Trebuchet Dynamics","01M73B3ABCZH5W4YDBMD7CP7ZV",5,"MIT","https:\u002F\u002Fgithub.com\u002FTrebuchetDynamics\u002Fpi-toolset\u002Fblob\u002Fmain\u002Fskills\u002Ffrontend\u002Fbeautify-github-readme\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: beautify-github-readme\ndescription: Use when improving a GitHub repository README visually, creating GitHub-safe README SVG assets, or auditing README presentation; not general website UI or ordinary documentation maintenance.\nlicense: MIT\nsource: https:\u002F\u002Fgithub.com\u002Foil-oil\u002Fbeautify-github-readme\nsource_commit: 4119e6a7c58d1b48fe883784133413391b148180\n---\n\n# Beautify GitHub README\n\nMake the project easier to understand, trust, and try. Use repository evidence as the visual material, SVG\u002Fraster as the visual layer, and Markdown as the usable content layer. Fewer, more informative visuals beat more decoration.\n\n## Setup and scope\n\nSet `SKILL_DIR` to the directory containing this `SKILL.md`. Resolve bundled references and scripts there, not in the target repository. The read-only audit uses Python 3.10+ and its standard library; it does not install anything or fetch remote resources.\n\nSelect scope from the user's request; reuse explicit decisions:\n\n| Mode | Allowed changes | Required handoff |\n| --- | --- | --- |\n| **Audit** | None | Prioritized findings with file\u002Fsection evidence |\n| **README mode** | Requested README and supporting assets | Diff, asset paths, validation evidence |\n| **SVG-only mode** | Requested SVG assets only | Asset paths, previews, optional embed snippets |\n\nFor an ambiguous request such as “beautify it,” ask once: “Whole-README improvement or SVG-only assets?” A repository path or invoking this skill alone does not authorize a whole-README rewrite. Explicit audits need no mode question. Read-only inspection may precede clarification.\n\nIn README mode, distinguish a **visual refresh** (preserve section order and content structure) from a **full redesign** (restructure the story). Use the smallest change that meets the request. In SVG-only mode, do not edit README text, links, embeds, or ordering without new authorization.\n\n## 1. Inspect and establish the story\n\nRead the relevant README, tree, metadata, usage examples, screenshots, output, logos, and design tokens. For a GitHub URL, inspect the current remote README and default branch; do not assume local content is current. Keep SVG-only inspection proportional to the asset request.\n\nRecord a compact brief before drawing:\n\n```text\nMode \u002F depth \u002F files allowed to change:\nAudience \u002F one-sentence value:\nPrimary proof \u002F exact source path or URL:\nFirst successful action \u002F source for the command:\nExisting identity to preserve:\n```\n\nClaims need evidence: never invent features, adoption, benchmarks, compatibility, testimonials, or output. Label conceptual diagrams as conceptual. With no honest visual proof, choose a typographic opening and a real example rather than fabricate a screenshot. Preserve existing notices, useful links, limitations, and unrelated user changes.\n\n## 2. Choose art direction from the project\n\nRead [visual-direction.md](references\u002Fvisual-direction.md) and [project-native-hero.md](references\u002Fproject-native-hero.md). Choose one composition and explain which project evidence makes it fit; consider a second direction only when the brief leaves a meaningful choice.\n\n```text\nComposition \u002F evidence-based reason:\nPalette: explicit background \u002F foreground \u002F primary \u002F muted colors\nType: available system stacks \u002F hierarchy \u002F minimum displayed text size\nShape and spacing: edge treatment \u002F stroke \u002F spacing unit\nMotif: one cue derived from the project's material\nProof treatment: SVG diagram \u002F separate screenshot \u002F composed raster\n```\n\nExisting identity wins over fashionable defaults. Neither rounded dark cards, a split hero, nor a monochrome grid is mandatory. Prototype the hero before producing a whole asset set. Test at desktop and narrow **display widths**, not only at SVG source size; simplify or move dense proof into Markdown\u002Fseparate images when it fails.\n\n## 3. Build only what helps the reader\n\n**README mode:** read [content-architecture.md](references\u002Fcontent-architecture.md). A useful default is value → proof → mechanism → first use → details. Preserve the existing sequence for a visual refresh. Keep real Markdown headings, copyable commands, searchable explanations, links, and limitations. Check existing anchors when renaming\u002Freordering headings; an image-only heading is not a replacement.\n\n**SVG-only mode:** confirm the requested asset types\u002Fcount when missing, create them under `assets\u002Freadme\u002F` or the agreed path, and keep all outputs vector. Offer raster proof separately if useful; do not silently change format or embed assets. Capture the README's starting bytes\u002Fhash and compare at handoff, including any pre-existing user edits.\n\nBefore creating assets, read [github-readme-canvas.md](references\u002Fgithub-readme-canvas.md) and [svg-production.md](references\u002Fsvg-production.md):\n\n- Use SVG for maintainable typography, geometry, and diagrams; PNG\u002FWebP for screenshots, photos, and complex compositing in README mode.\n- Choose one strong proof composition; add section banners only when they improve scanning rather than duplicate headings.\n- Keep essential meaning available without images. Use informative alt text; genuinely decorative images may have empty alt, with that choice reviewed explicitly.\n- Reuse palette, spacing, and motif across the set, not the same layout everywhere. Let proof legibility decide whether title and proof share a board.\n- Keep assets self-contained: no scripts, event handlers, `foreignObject`, external fonts\u002Fresources, or essential animation. Do not rasterize the README itself.\n\n## 4. Verify in two separate passes\n\nRead [verification.md](references\u002Fverification.md) for commands, preview checks, limitations, and the missing-tool fallback.\n\n1. **Static:** in README mode or an audit, run:\n\n   ```bash\n   python3 \"$SKILL_DIR\u002Fscripts\u002Faudit_readme.py\" \u002Fpath\u002Fto\u002Frepository\u002FREADME.md\n   ```\n\n   Review every finding; exit `0` means only the supported local checks passed, `1` means findings, and `2` means input\u002Fusage failure. In SVG-only mode, audit assets through the temporary manifest procedure without editing the target README.\n2. **Rendered:** inspect each asset and the README composition at approximately 800 px and 320 px content widths, with light and dark surroundings. Check actual type size, clipping, hierarchy, contrast, proof legibility, and image-free usability. These widths are test cases, not a promise of GitHub's layout. Fix the highest-impact issue and render again.\n\nA local renderer is not GitHub's sanitizer. Disclose any GitHub-specific behavior not checked. If rendering tools are unavailable, finish independent work and label the result **static-checked; visual verification pending**. Give precise preview steps; never substitute lint output for a visual receipt or install tooling without approval.\n\n## 5. Hand off without publishing\n\nShow the diff and available previews. Do not commit, push, open a PR, merge, rename a repository, or publish assets unless explicitly requested.\n\n## Output contract\n\n- **Audit:** prioritized clarity, hierarchy, trust, accessibility, and maintenance findings with evidence; no edits.\n- **README mode:** concise story\u002Fdirection rationale, changed paths, README diff, static command and exit status, rendered preview evidence or pending checks, intentionally untouched files.\n- **SVG-only mode:** created asset paths, static\u002Frendered evidence or pending checks, optional embed snippets, and before\u002Fafter README comparison.\n- Distinguish **verified**, **not checked**, and **requires owner approval**. Never imply that a remote source was fetched, a preview inspected, or a claim verified when it was not.\n\n## Optional attribution and showcase\n\nOnly after explicit satisfaction with the final result, offer once: an optional project-native “README MADE WITH” signature, a showcase proposal for a public repository the user owns\u002Fmaintains, both, or neither. Do not infer satisfaction from silence or passing checks, repeat a declined offer, or make attribution a condition of delivery\u002Fshowcase eligibility.\n\n- **Signature opt-in:** follow [svg-production.md](references\u002Fsvg-production.md), show a rendered badge first, and get separate approval before embedding. No unsolicited backlinks in third-party repositories.\n- **Showcase opt-in:** follow [showcase-contribution.md](references\u002Fshowcase-contribution.md). Verify eligibility, draft exact upstream listing\u002Fdiff, then obtain authorization for each external action. Opt-in does not itself authorize a fork, push, or PR.\n\nAn earlier explicit request for either option can be handled within its stated scope.\n\n## Invocation examples\n\n```text\nUse beautify-github-readme to refresh this README without changing its section order.\nUse beautify-github-readme to create one SVG hero; leave the README unchanged.\nUse beautify-github-readme to audit this README without editing files.\n```\n\n## Shared contract\n\nFollow [the shared skill contract](..\u002F..\u002Fshared\u002FCOMMON-CONTRACT.md) for repo study, dirty-worktree hygiene, bundled resource paths, verification evidence, safe handoffs, and safety defaults.\n","# Beautify GitHub README\n\nMake the project easier to understand, trust, and try. Use repository evidence as the visual material, SVG\u002Fraster as the visual layer, and Markdown as the usable content layer. Fewer, more informative visuals beat more decoration.\n\n## Setup and scope\n\nSet `SKILL_DIR` to the directory containing this `SKILL.md`. Resolve bundled references and scripts there, not in the target repository. The read-only audit uses Python 3.10+ and its standard library; it does not install anything or fetch remote resources.\n\nSelect scope from the user's request; reuse explicit decisions:\n\n| Mode | Allowed changes | Required handoff |\n| --- | --- | --- |\n| **Audit** | None | Prioritized findings with file\u002Fsection evidence |\n| **README mode** | Requested README and supporting assets | Diff, asset paths, validation evidence |\n| **SVG-only mode** | Requested SVG assets only | Asset paths, previews, optional embed snippets |\n\nFor an ambiguous request such as “beautify it,” ask once: “Whole-README improvement or SVG-only assets?” A repository path or invoking this skill alone does not authorize a whole-README rewrite. Explicit audits need no mode question. Read-only inspection may precede clarification.\n\nIn README mode, distinguish a **visual refresh** (preserve section order and content structure) from a **full redesign** (restructure the story). Use the smallest change that meets the request. In SVG-only mode, do not edit README text, links, embeds, or ordering without new authorization.\n\n## 1. Inspect and establish the story\n\nRead the relevant README, tree, metadata, usage examples, screenshots, output, logos, and design tokens. For a GitHub URL, inspect the current remote README and default branch; do not assume local content is current. Keep SVG-only inspection proportional to the asset request.\n\nRecord a compact brief before drawing:\n\n```text\nMode \u002F depth \u002F files allowed to change:\nAudience \u002F one-sentence value:\nPrimary proof \u002F exact source path or URL:\nFirst successful action \u002F source for the command:\nExisting identity to preserve:\n```\n\nClaims need evidence: never invent features, adoption, benchmarks, compatibility, testimonials, or output. Label conceptual diagrams as conceptual. With no honest visual proof, choose a typographic opening and a real example rather than fabricate a screenshot. Preserve existing notices, useful links, limitations, and unrelated user changes.\n\n## 2. Choose art direction from the project\n\nRead [visual-direction.md](references\u002Fvisual-direction.md) and [project-native-hero.md](references\u002Fproject-native-hero.md). Choose one composition and explain which project evidence makes it fit; consider a second direction only when the brief leaves a meaningful choice.\n\n```text\nComposition \u002F evidence-based reason:\nPalette: explicit background \u002F foreground \u002F primary \u002F muted colors\nType: available system stacks \u002F hierarchy \u002F minimum displayed text size\nShape and spacing: edge treatment \u002F stroke \u002F spacing unit\nMotif: one cue derived from the project's material\nProof treatment: SVG diagram \u002F separate screenshot \u002F composed raster\n```\n\nExisting identity wins over fashionable defaults. Neither rounded dark cards, a split hero, nor a monochrome grid is mandatory. Prototype the hero before producing a whole asset set. Test at desktop and narrow **display widths**, not only at SVG source size; simplify or move dense proof into Markdown\u002Fseparate images when it fails.\n\n## 3. Build only what helps the reader\n\n**README mode:** read [content-architecture.md](references\u002Fcontent-architecture.md). A useful default is value → proof → mechanism → first use → details. Preserve the existing sequence for a visual refresh. Keep real Markdown headings, copyable commands, searchable explanations, links, and limitations. Check existing anchors when renaming\u002Freordering headings; an image-only heading is not a replacement.\n\n**SVG-only mode:** confirm the requested asset types\u002Fcount when missing, create them under `assets\u002Freadme\u002F` or the agreed path, and keep all outputs vector. Offer raster proof separately if useful; do not silently change format or embed assets. Capture the README's starting bytes\u002Fhash and compare at handoff, including any pre-existing user edits.\n\nBefore creating assets, read [github-readme-canvas.md](references\u002Fgithub-readme-canvas.md) and [svg-production.md](references\u002Fsvg-production.md):\n\n- Use SVG for maintainable typography, geometry, and diagrams; PNG\u002FWebP for screenshots, photos, and complex compositing in README mode.\n- Choose one strong proof composition; add section banners only when they improve scanning rather than duplicate headings.\n- Keep essential meaning available without images. Use informative alt text; genuinely decorative images may have empty alt, with that choice reviewed explicitly.\n- Reuse palette, spacing, and motif across the set, not the same layout everywhere. Let proof legibility decide whether title and proof share a board.\n- Keep assets self-contained: no scripts, event handlers, `foreignObject`, external fonts\u002Fresources, or essential animation. Do not rasterize the README itself.\n\n## 4. Verify in two separate passes\n\nRead [verification.md](references\u002Fverification.md) for commands, preview checks, limitations, and the missing-tool fallback.\n\n1. **Static:** in README mode or an audit, run:\n\n   ```bash\n   python3 \"$SKILL_DIR\u002Fscripts\u002Faudit_readme.py\" \u002Fpath\u002Fto\u002Frepository\u002FREADME.md\n   ```\n\n   Review every finding; exit `0` means only the supported local checks passed, `1` means findings, and `2` means input\u002Fusage failure. In SVG-only mode, audit assets through the temporary manifest procedure without editing the target README.\n2. **Rendered:** inspect each asset and the README composition at approximately 800 px and 320 px content widths, with light and dark surroundings. Check actual type size, clipping, hierarchy, contrast, proof legibility, and image-free usability. These widths are test cases, not a promise of GitHub's layout. Fix the highest-impact issue and render again.\n\nA local renderer is not GitHub's sanitizer. Disclose any GitHub-specific behavior not checked. If rendering tools are unavailable, finish independent work and label the result **static-checked; visual verification pending**. Give precise preview steps; never substitute lint output for a visual receipt or install tooling without approval.\n\n## 5. Hand off without publishing\n\nShow the diff and available previews. Do not commit, push, open a PR, merge, rename a repository, or publish assets unless explicitly requested.\n\n## Output contract\n\n- **Audit:** prioritized clarity, hierarchy, trust, accessibility, and maintenance findings with evidence; no edits.\n- **README mode:** concise story\u002Fdirection rationale, changed paths, README diff, static command and exit status, rendered preview evidence or pending checks, intentionally untouched files.\n- **SVG-only mode:** created asset paths, static\u002Frendered evidence or pending checks, optional embed snippets, and before\u002Fafter README comparison.\n- Distinguish **verified**, **not checked**, and **requires owner approval**. Never imply that a remote source was fetched, a preview inspected, or a claim verified when it was not.\n\n## Optional attribution and showcase\n\nOnly after explicit satisfaction with the final result, offer once: an optional project-native “README MADE WITH” signature, a showcase proposal for a public repository the user owns\u002Fmaintains, both, or neither. Do not infer satisfaction from silence or passing checks, repeat a declined offer, or make attribution a condition of delivery\u002Fshowcase eligibility.\n\n- **Signature opt-in:** follow [svg-production.md](references\u002Fsvg-production.md), show a rendered badge first, and get separate approval before embedding. No unsolicited backlinks in third-party repositories.\n- **Showcase opt-in:** follow [showcase-contribution.md](references\u002Fshowcase-contribution.md). Verify eligibility, draft exact upstream listing\u002Fdiff, then obtain authorization for each external action. Opt-in does not itself authorize a fork, push, or PR.\n\nAn earlier explicit request for either option can be handled within its stated scope.\n\n## Invocation examples\n\n```text\nUse beautify-github-readme to refresh this README without changing its section order.\nUse beautify-github-readme to create one SVG hero; leave the README unchanged.\nUse beautify-github-readme to audit this README without editing files.\n```\n\n## Shared contract\n\nFollow [the shared skill contract](..\u002F..\u002Fshared\u002FCOMMON-CONTRACT.md) for repo study, dirty-worktree hygiene, bundled resource paths, verification evidence, safe handoffs, and safety defaults.\n",{"name":5,"source":24,"license":15,"description":7,"source_commit":25},"https:\u002F\u002Fgithub.com\u002Foil-oil\u002Fbeautify-github-readme","4119e6a7c58d1b48fe883784133413391b148180","main","5e9aa8398adb6812fb816bf887d1ad10f12c55db","skills\u002Ffrontend\u002Fbeautify-github-readme",0,"https:\u002F\u002Fgithub.com\u002FTrebuchetDynamics\u002Fpi-toolset","https:\u002F\u002Fgithub.com\u002FTrebuchetDynamics","https:\u002F\u002Ftrebuchetdynamics.com","Serious engineering for systems that cannot fail quietly","2026-10-17 04:37:36",{"source":8,"skillName":5,"commands":36,"prompt":46,"zipAvailable":47},[37,40,43],{"tool":38,"command":39},"npx","npx skills add TrebuchetDynamics\u002Fpi-toolset --skill beautify-github-readme",{"tool":41,"command":42},"bunx","bunx skills add TrebuchetDynamics\u002Fpi-toolset --skill beautify-github-readme",{"tool":44,"command":45},"pnpm","pnpm dlx skills add TrebuchetDynamics\u002Fpi-toolset --skill beautify-github-readme","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FTrebuchetDynamics\u002Fpi-toolset\u002Fblob\u002Fmain\u002Fskills\u002Ffrontend\u002Fbeautify-github-readme\u002FSKILL.md",true,[49,55,59,63,67,71,75,79,83],{"path":50,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":53,"sourceHtmlUrl":54},"agents\u002Fopenai.yaml","REFERENCE","参考文档",321,"https:\u002F\u002Fgithub.com\u002FTrebuchetDynamics\u002Fpi-toolset\u002Fblob\u002Fmain\u002Fskills\u002Ffrontend\u002Fbeautify-github-readme\u002Fagents\u002Fopenai.yaml",{"path":56,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":57,"sourceHtmlUrl":58},"references\u002Fcontent-architecture.md",1311,"https:\u002F\u002Fgithub.com\u002FTrebuchetDynamics\u002Fpi-toolset\u002Fblob\u002Fmain\u002Fskills\u002Ffrontend\u002Fbeautify-github-readme\u002Freferences\u002Fcontent-architecture.md",{"path":60,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":61,"sourceHtmlUrl":62},"references\u002Fgithub-readme-canvas.md",4543,"https:\u002F\u002Fgithub.com\u002FTrebuchetDynamics\u002Fpi-toolset\u002Fblob\u002Fmain\u002Fskills\u002Ffrontend\u002Fbeautify-github-readme\u002Freferences\u002Fgithub-readme-canvas.md",{"path":64,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":65,"sourceHtmlUrl":66},"references\u002Fproject-native-hero.md",6238,"https:\u002F\u002Fgithub.com\u002FTrebuchetDynamics\u002Fpi-toolset\u002Fblob\u002Fmain\u002Fskills\u002Ffrontend\u002Fbeautify-github-readme\u002Freferences\u002Fproject-native-hero.md",{"path":68,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":69,"sourceHtmlUrl":70},"references\u002Fshowcase-contribution.md",2611,"https:\u002F\u002Fgithub.com\u002FTrebuchetDynamics\u002Fpi-toolset\u002Fblob\u002Fmain\u002Fskills\u002Ffrontend\u002Fbeautify-github-readme\u002Freferences\u002Fshowcase-contribution.md",{"path":72,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":73,"sourceHtmlUrl":74},"references\u002Fsvg-production.md",7000,"https:\u002F\u002Fgithub.com\u002FTrebuchetDynamics\u002Fpi-toolset\u002Fblob\u002Fmain\u002Fskills\u002Ffrontend\u002Fbeautify-github-readme\u002Freferences\u002Fsvg-production.md",{"path":76,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":77,"sourceHtmlUrl":78},"references\u002Fverification.md",6539,"https:\u002F\u002Fgithub.com\u002FTrebuchetDynamics\u002Fpi-toolset\u002Fblob\u002Fmain\u002Fskills\u002Ffrontend\u002Fbeautify-github-readme\u002Freferences\u002Fverification.md",{"path":80,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":81,"sourceHtmlUrl":82},"references\u002Fvisual-direction.md",5397,"https:\u002F\u002Fgithub.com\u002FTrebuchetDynamics\u002Fpi-toolset\u002Fblob\u002Fmain\u002Fskills\u002Ffrontend\u002Fbeautify-github-readme\u002Freferences\u002Fvisual-direction.md",{"path":84,"resourceType":85,"resourceTypeDesc":86,"sizeBytes":87,"sourceHtmlUrl":88},"scripts\u002Faudit_readme.py","SCRIPT","脚本",10512,"https:\u002F\u002Fgithub.com\u002FTrebuchetDynamics\u002Fpi-toolset\u002Fblob\u002Fmain\u002Fskills\u002Ffrontend\u002Fbeautify-github-readme\u002Fscripts\u002Faudit_readme.py",[90,99,106,113,120],{"skillNo":91,"name":92,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":94,"licenseFileUrl":95,"sourceHtmlUrl":96,"categories":97,"keywords":98,"publishedAt":19},"01M73B6VW40W876ZJH991GNECA","impeccable","Use when designing, building, redesigning, critiquing, auditing, or polishing a frontend interface, including websites, landing pages, dashboards, product UI, components, forms, onboarding, typography, color, layout, motion, UX copy, accessibility, responsive behavior, and design systems. Also for live browser variant iteration. Not for backend-only or non-UI tasks.","Apache-2.0","https:\u002F\u002Fgithub.com\u002FTrebuchetDynamics\u002Fpi-toolset\u002Fblob\u002Fmain\u002Fskills\u002Ffrontend\u002Fimpeccable\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FTrebuchetDynamics\u002Fpi-toolset\u002Fblob\u002Fmain\u002Fskills\u002Ffrontend\u002Fimpeccable\u002FSKILL.md",[],[],{"skillNo":100,"name":101,"nameZh":6,"description":102,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":103,"categories":104,"keywords":105,"publishedAt":19},"01M73B6RVWFDBP9XDF3EPC23BX","diagram-design","Create standalone architecture, sequence, and process diagrams as accessible HTML\u002FSVG. Use for shareable visual explanations; not app UI, scientific plots, or simple inline Mermaid diagrams.","https:\u002F\u002Fgithub.com\u002FTrebuchetDynamics\u002Fpi-toolset\u002Fblob\u002Fmain\u002Fskills\u002Ffrontend\u002Fdiagram-design\u002FSKILL.md",[],[],{"skillNo":107,"name":108,"nameZh":6,"description":109,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":110,"categories":111,"keywords":112,"publishedAt":19},"01M73B6830KQA1THCG9BZPKYR4","wayfinder","Plan work larger than one agent session as a shared map of decision tickets, then resolve them one at a time. Use when a large, unclear effort needs durable cross-session planning before implementation.","https:\u002F\u002Fgithub.com\u002FTrebuchetDynamics\u002Fpi-toolset\u002Fblob\u002Fmain\u002Fskills\u002Fengineering\u002Fwayfinder\u002FSKILL.md",[],[],{"skillNo":114,"name":115,"nameZh":6,"description":116,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":117,"categories":118,"keywords":119,"publishedAt":19},"01M73B4A7630WFKNQP8B9MSKWG","greploop","Iterate on an existing PR, MR, or shelved changelist until Greptile reaches 5\u002F5 with no unresolved comments. Use only when that review context, tooling, auth, and external-action approval exist.","https:\u002F\u002Fgithub.com\u002FTrebuchetDynamics\u002Fpi-toolset\u002Fblob\u002Fmain\u002Fskills\u002Fdelivery\u002Fgreploop\u002FSKILL.md",[],[],{"skillNo":121,"name":122,"nameZh":6,"description":123,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":124,"categories":125,"keywords":126,"publishedAt":19},"01M73B3WDJ75QXPFMY4V7YXWYV","ponytail","Persistent YAGNI and shortest-safe-diff implementation mode. Use when the user says ponytail, be lazy, simplest\u002Fminimal solution, do less, or complains about over-engineering. Do not use for non-coding requests or one-shot audits\u002Freviews.","https:\u002F\u002Fgithub.com\u002FTrebuchetDynamics\u002Fpi-toolset\u002Fblob\u002Fmain\u002Fskills\u002Fcommunication\u002Fponytail\u002FSKILL.md",[],[]]