[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M75EB52H9ASPJJSFKY4MREK1":3,"skill-same:01M75EB52H9ASPJJSFKY4MREK1":49},{"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":14,"repositoryHtmlUrl":30,"repositoryHomepageUrl":6,"ownerHtmlUrl":31,"ownerBlogUrl":32,"ownerDescription":33,"updatedAt":34,"install":35,"resources":48},"01M75EB52H9ASPJJSFKY4MREK1","comment-writer",null,"Write warm, direct collaboration comments. Trigger: PR feedback, issue replies, reviews, Slack messages, or GitHub comments.","AdrichDev\u002Fgru_orchestrator","AdrichDev","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F172129260?v=4","01M75DR1Z03617FFA846AG5JJ6","Adrián Chozas","01M75DR1ZMXV62W49NBFHAMQBT",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002FAdrichDev\u002Fgru_orchestrator\u002Fblob\u002Fmain\u002F.qwen\u002Fskills\u002Fcomment-writer\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: comment-writer\ndescription: \"Write warm, direct collaboration comments. Trigger: PR feedback, issue replies, reviews, Slack messages, or GitHub comments.\"\nlicense: Apache-2.0\nmetadata:\n  author: gentleman-programming\n  version: \"1.0\"\n---\n\n## When to Use\n\nLoad this skill whenever you write a comment that another human will read.\n\nUse it for:\n\n- GitHub PR or issue comments.\n- Review feedback and requested changes.\n- Maintainer replies.\n- Slack, Discord, or async project updates.\n\n## Voice Rules\n\n| Rule | Requirement |\n|------|-------------|\n| Be useful fast | Start with the actionable point. Do not recap the whole PR before feedback. |\n| Be warm and direct | Sound like a thoughtful teammate, not a corporate bot. |\n| Keep it short | Prefer 1 to 3 short paragraphs or a tight bullet list. |\n| Explain why | Give the technical reason when asking for a change. |\n| Avoid pile-ons | Comment on the highest-value issue, not every tiny preference. |\n| Match target context language | Write in the target context language by default: Spanish issue\u002Fthread -> Spanish comment, English issue\u002Fthread -> English comment, mixed context -> target message language. If the user explicitly requests a language or tone, follow that request. For Spanish comments, use neutral\u002Fprofessional Spanish by default unless the user or target context clearly calls for regional tone. |\n| No em dashes | Use commas, periods, or parentheses instead. |\n\n## Comment Formula\n\n```text\n\u003CDirect observation or request>\n\n\u003CWhy it matters, only if needed>\n\n\u003CConcrete next action>\n```\n\n## Examples\n\n### Request change\n\n```markdown\nGood approach overall. I'd split this into a separate commit because it mixes validation logic with UI wiring.\n\nThat keeps the reviewer's focus narrower and makes rollback cleaner if the integration fails.\n```\n\n### Approve with a note\n\n```markdown\nApproved. The scope is clear and the change is well-contained.\n\nFor the next PR, add links to the previous and following PRs so the chain stays navigable.\n```\n\n### Ask for split\n\n```markdown\nThis PR exceeds the 400-line budget, so we need to split it or justify `size:exception`.\n\nSuggested order: foundation + tests first, then integration, then docs. That gives each review a clear start and end.\n```\n\n## Commands\n\n```bash\n# Inspect a PR before writing review feedback\ngh pr view \u003CPR_NUMBER> --json title,body,additions,deletions,changedFiles\n```\n","## When to Use\n\nLoad this skill whenever you write a comment that another human will read.\n\nUse it for:\n\n- GitHub PR or issue comments.\n- Review feedback and requested changes.\n- Maintainer replies.\n- Slack, Discord, or async project updates.\n\n## Voice Rules\n\n| Rule | Requirement |\n|------|-------------|\n| Be useful fast | Start with the actionable point. Do not recap the whole PR before feedback. |\n| Be warm and direct | Sound like a thoughtful teammate, not a corporate bot. |\n| Keep it short | Prefer 1 to 3 short paragraphs or a tight bullet list. |\n| Explain why | Give the technical reason when asking for a change. |\n| Avoid pile-ons | Comment on the highest-value issue, not every tiny preference. |\n| Match target context language | Write in the target context language by default: Spanish issue\u002Fthread -> Spanish comment, English issue\u002Fthread -> English comment, mixed context -> target message language. If the user explicitly requests a language or tone, follow that request. For Spanish comments, use neutral\u002Fprofessional Spanish by default unless the user or target context clearly calls for regional tone. |\n| No em dashes | Use commas, periods, or parentheses instead. |\n\n## Comment Formula\n\n```text\n\u003CDirect observation or request>\n\n\u003CWhy it matters, only if needed>\n\n\u003CConcrete next action>\n```\n\n## Examples\n\n### Request change\n\n```markdown\nGood approach overall. I'd split this into a separate commit because it mixes validation logic with UI wiring.\n\nThat keeps the reviewer's focus narrower and makes rollback cleaner if the integration fails.\n```\n\n### Approve with a note\n\n```markdown\nApproved. The scope is clear and the change is well-contained.\n\nFor the next PR, add links to the previous and following PRs so the chain stays navigable.\n```\n\n### Ask for split\n\n```markdown\nThis PR exceeds the 400-line budget, so we need to split it or justify `size:exception`.\n\nSuggested order: foundation + tests first, then integration, then docs. That gives each review a clear start and end.\n```\n\n## Commands\n\n```bash\n# Inspect a PR before writing review feedback\ngh pr view \u003CPR_NUMBER> --json title,body,additions,deletions,changedFiles\n```\n",{"name":5,"license":15,"metadata":24,"description":7},{"author":25,"version":26},"gentleman-programming","1.0","main","6745e47ba2ea20f71dce9a8303c332ef63ef43b6",".qwen\u002Fskills\u002Fcomment-writer","https:\u002F\u002Fgithub.com\u002FAdrichDev\u002Fgru_orchestrator","https:\u002F\u002Fgithub.com\u002FAdrichDev","https:\u002F\u002Fwww.linkedin.com\u002Fin\u002Fadrichv\u002F","Software Junior Developer en continua formación y aprendizaje. Además , Trabajador social.\r\nIntentaré ir subiendo cositas!! \r\nFeliz día!!","2026-11-15 04:14:37",{"source":8,"skillName":5,"commands":36,"prompt":46,"zipAvailable":47},[37,40,43],{"tool":38,"command":39},"npx","npx skills add AdrichDev\u002Fgru_orchestrator --skill comment-writer",{"tool":41,"command":42},"bunx","bunx skills add AdrichDev\u002Fgru_orchestrator --skill comment-writer",{"tool":44,"command":45},"pnpm","pnpm dlx skills add AdrichDev\u002Fgru_orchestrator --skill comment-writer","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FAdrichDev\u002Fgru_orchestrator\u002Fblob\u002Fmain\u002F.qwen\u002Fskills\u002Fcomment-writer\u002FSKILL.md",true,[],[50,58,63,70,77,84],{"skillNo":51,"name":52,"nameZh":6,"description":53,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":54,"licenseFileUrl":6,"sourceHtmlUrl":55,"categories":56,"keywords":57,"publishedAt":19},"01M75ED2J1WS4B52JV2Q0R01CB","invocable-skill","Run a security audit on the specified target. Use when asked to audit, scan, or assess security posture.","MIT","https:\u002F\u002Fgithub.com\u002FAdrichDev\u002Fgru_orchestrator\u002Fblob\u002Fmain\u002Fpackages\u002Fkernel\u002Fsrc\u002Fadapters\u002F__tests__\u002Fmock-ac-root\u002Fskills\u002Finvocable-skill\u002FSKILL.md",[],[],{"skillNo":59,"name":52,"nameZh":6,"description":53,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":54,"licenseFileUrl":6,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":19},"01M75ECRCQFK3WY7Q990S3ZANF","https:\u002F\u002Fgithub.com\u002FAdrichDev\u002Fgru_orchestrator\u002Fblob\u002Fmain\u002Fpackages\u002Fkernel\u002Fsrc\u002Fadapters\u002F__tests__\u002Ffixtures-ac\u002Finvocable-skill\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},"01M75ECJTFT8NZXFX0M95XHBGJ","work-unit-commits","Plan commits as reviewable work units. Trigger: implementation, commit splitting, chained PRs, or keeping tests and docs with code.","https:\u002F\u002Fgithub.com\u002FAdrichDev\u002Fgru_orchestrator\u002Fblob\u002Fmain\u002F.qwen\u002Fskills\u002Fwork-unit-commits\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":54,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":19},"01M75ECHC0CRV7MCB19WVAPQZN","skill-registry","Trigger: update skills, skill registry, actualizar skills, after skill changes. Index available skills by trigger and path.","https:\u002F\u002Fgithub.com\u002FAdrichDev\u002Fgru_orchestrator\u002Fblob\u002Fmain\u002F.qwen\u002Fskills\u002Fskill-registry\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},"01M75ECFSPSZCFMA3BK74SN2M7","skill-improver","Trigger: improve skills, audit skills, refactor skills, skill quality. Audit and upgrade existing LLM-first skills.","https:\u002F\u002Fgithub.com\u002FAdrichDev\u002Fgru_orchestrator\u002Fblob\u002Fmain\u002F.qwen\u002Fskills\u002Fskill-improver\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},"01M75ECE874149EMN8ZEEMSAPM","skill-creator","Trigger: new skills, agent instructions, documenting AI usage patterns. Create LLM-first skills with valid frontmatter.","https:\u002F\u002Fgithub.com\u002FAdrichDev\u002Fgru_orchestrator\u002Fblob\u002Fmain\u002F.qwen\u002Fskills\u002Fskill-creator\u002FSKILL.md",[],[]]