[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71RFS7R23RGHE5EX4Y1TXFF":3,"skill-same:01M71RFS7R23RGHE5EX4Y1TXFF":87},{"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":36,"linkOnly":37,"markdownContent":38,"markdownBody":39,"frontMatter":40,"refName":41,"commitSha":42,"skillDirectory":43,"forksCount":44,"repositoryHtmlUrl":45,"repositoryHomepageUrl":6,"ownerHtmlUrl":46,"ownerBlogUrl":6,"ownerDescription":47,"updatedAt":48,"install":49,"resources":62},"01M71RFS7R23RGHE5EX4Y1TXFF","autospec-monitor",null,"Observe a live autospec-autonomous conductor read-only by summarizing typed status, timeline, launch, heartbeat, tier, and discovery artifact surfaces.","berlinguyinca\u002Fautospec","berlinguyinca","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F16364?v=4","01M71R7C0SWBG05FNHQE4XQ7Y3","Gert Wohlgemuth","01M71R7C1VY5K3Q715RNDDBVGQ",3,"MIT","https:\u002F\u002Fgithub.com\u002Fberlinguyinca\u002Fautospec\u002Fblob\u002Fmain\u002Fskills\u002Fautospec-monitor\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35],"autospec monitor","autospec","monitor","timeline","heartbeat","live","autonomous","only","status","launch","surfaces","read","conductor","discovery","observe","read-only","artifact","2026-11-10 13:02:02",false,"---\nname: autospec-monitor\ndescription: Observe a live autospec-autonomous conductor read-only by summarizing typed status, timeline, launch, heartbeat, tier, and discovery artifact surfaces.\n---\n# autospec-monitor\n\nUse this skill when the operator asks for live observability into an `autospec-autonomous`\nrun: what conductor is running, whether it was launched in real mode or `--dry-run`,\nwhich cycle\u002Ftier\u002Faction is current, how fresh the heartbeat is, what stop flag is set,\nand what discovery artifacts were produced.\n\nAutospec monitor is read-only by default. It must not mutate repository state or GitHub\nstate unless the operator explicitly asks it to file a monitor-related issue.\n\n## Operating Rules\n\n- Prefer the typed Rust command surfaces over raw log parsing.\n- Use `autospec autonomous monitor --once` for a concise operator snapshot.\n- Use `autospec autonomous status --json` and `autospec autonomous timeline --lines N`\n  for follow-up detail; do not hand-parse logs unless those typed fields are missing.\n- Always distinguish launch mode from tier result:\n  - `run_mode=dry-run` means the conductor launch argv included `--dry-run`.\n  - `tier_dry_result.dry=true` means that tier filed no candidates in that cycle;\n    it does not by itself mean the conductor was launched with `--dry-run`.\n- Accept and pass through `--repo OWNER\u002FREPO` and `--repo-dir DIR` using the same\n  conventions as `autospec-autonomous` \u002F `autospec autonomous`.\n- Stay useful when fields are partially empty by reporting `-`, `null`, or an empty\n  artifact list rather than inventing state.\n- GitHub issue writes require explicit operator confirmation and must be limited to\n  monitor-related defects or enhancement requests.\n\n## Command Shape\n\n```bash\nautospec autonomous monitor --once --repo OWNER\u002FREPO --repo-dir DIR\n```\n\nFor machine-readable output:\n\n```bash\nautospec autonomous monitor --once --json --repo OWNER\u002FREPO --repo-dir DIR\n```\n\nFor a broader timeline after the snapshot:\n\n```bash\nautospec autonomous status --json --repo OWNER\u002FREPO --repo-dir DIR\nautospec autonomous timeline --lines 80 --repo OWNER\u002FREPO --repo-dir DIR\n```\n\n## What To Report\n\nSummarize these fields when present:\n\n- conductor identity: repo, PID, log path, launch argv, stop flag path\u002Fmode;\n- launch mode: `real` versus `dry-run` from launch argv;\n- current work: cycle, tier, action, state status, and heartbeat age;\n- tier dry result: explain `dry=true` as a no-filed-candidates tier result, not as\n  proof of launch `--dry-run` mode;\n- discovery artifacts: `.autospec\u002Fexplore-once-*` metadata, proposal counts,\n  candidate\u002Ffiled issue titles, and verification mode.\n\n## Intent Mapping\n\n| Operator asks | Do this |\n| --- | --- |\n| What is autospec-autonomous doing? | Run `autospec autonomous monitor --once --repo OWNER\u002FREPO --repo-dir DIR`. |\n| Is this a real run or dry-run? | Report `run_mode` from monitor output and quote the launch argv evidence. |\n| Did Tier 2\u002F4 dry mean dry-run? | Explain that tier `dry=true` means no filed candidates for that tier cycle. |\n| What did discovery find? | Report `.autospec\u002Fexplore-once-*` proposal\u002Fcandidate counts and titles. |\n| Fields are missing or empty. | Fall back to status\u002Ftimeline\u002Fartifact summaries and mark unknown fields as `-` or `null`. |\n| File an issue about monitor output. | Confirm the requested write, then file only that monitor-related issue. |\n","# autospec-monitor\n\nUse this skill when the operator asks for live observability into an `autospec-autonomous`\nrun: what conductor is running, whether it was launched in real mode or `--dry-run`,\nwhich cycle\u002Ftier\u002Faction is current, how fresh the heartbeat is, what stop flag is set,\nand what discovery artifacts were produced.\n\nAutospec monitor is read-only by default. It must not mutate repository state or GitHub\nstate unless the operator explicitly asks it to file a monitor-related issue.\n\n## Operating Rules\n\n- Prefer the typed Rust command surfaces over raw log parsing.\n- Use `autospec autonomous monitor --once` for a concise operator snapshot.\n- Use `autospec autonomous status --json` and `autospec autonomous timeline --lines N`\n  for follow-up detail; do not hand-parse logs unless those typed fields are missing.\n- Always distinguish launch mode from tier result:\n  - `run_mode=dry-run` means the conductor launch argv included `--dry-run`.\n  - `tier_dry_result.dry=true` means that tier filed no candidates in that cycle;\n    it does not by itself mean the conductor was launched with `--dry-run`.\n- Accept and pass through `--repo OWNER\u002FREPO` and `--repo-dir DIR` using the same\n  conventions as `autospec-autonomous` \u002F `autospec autonomous`.\n- Stay useful when fields are partially empty by reporting `-`, `null`, or an empty\n  artifact list rather than inventing state.\n- GitHub issue writes require explicit operator confirmation and must be limited to\n  monitor-related defects or enhancement requests.\n\n## Command Shape\n\n```bash\nautospec autonomous monitor --once --repo OWNER\u002FREPO --repo-dir DIR\n```\n\nFor machine-readable output:\n\n```bash\nautospec autonomous monitor --once --json --repo OWNER\u002FREPO --repo-dir DIR\n```\n\nFor a broader timeline after the snapshot:\n\n```bash\nautospec autonomous status --json --repo OWNER\u002FREPO --repo-dir DIR\nautospec autonomous timeline --lines 80 --repo OWNER\u002FREPO --repo-dir DIR\n```\n\n## What To Report\n\nSummarize these fields when present:\n\n- conductor identity: repo, PID, log path, launch argv, stop flag path\u002Fmode;\n- launch mode: `real` versus `dry-run` from launch argv;\n- current work: cycle, tier, action, state status, and heartbeat age;\n- tier dry result: explain `dry=true` as a no-filed-candidates tier result, not as\n  proof of launch `--dry-run` mode;\n- discovery artifacts: `.autospec\u002Fexplore-once-*` metadata, proposal counts,\n  candidate\u002Ffiled issue titles, and verification mode.\n\n## Intent Mapping\n\n| Operator asks | Do this |\n| --- | --- |\n| What is autospec-autonomous doing? | Run `autospec autonomous monitor --once --repo OWNER\u002FREPO --repo-dir DIR`. |\n| Is this a real run or dry-run? | Report `run_mode` from monitor output and quote the launch argv evidence. |\n| Did Tier 2\u002F4 dry mean dry-run? | Explain that tier `dry=true` means no filed candidates for that tier cycle. |\n| What did discovery find? | Report `.autospec\u002Fexplore-once-*` proposal\u002Fcandidate counts and titles. |\n| Fields are missing or empty. | Fall back to status\u002Ftimeline\u002Fartifact summaries and mark unknown fields as `-` or `null`. |\n| File an issue about monitor output. | Confirm the requested write, then file only that monitor-related issue. |\n",{"name":5,"description":7},"main","9e7f04357ff46ab731d4f56a4ac5ca5449c13bb0","skills\u002Fautospec-monitor",1,"https:\u002F\u002Fgithub.com\u002Fberlinguyinca\u002Fautospec","https:\u002F\u002Fgithub.com\u002Fberlinguyinca","Love to lead, code, cook and contribute to open source and believe that you can learn anything you set your mind too.\r\n","2026-11-11 07:09:35",{"source":8,"skillName":5,"commands":50,"prompt":60,"zipAvailable":61},[51,54,57],{"tool":52,"command":53},"npx","npx skills add berlinguyinca\u002Fautospec --skill autospec-monitor",{"tool":55,"command":56},"bunx","bunx skills add berlinguyinca\u002Fautospec --skill autospec-monitor",{"tool":58,"command":59},"pnpm","pnpm dlx skills add berlinguyinca\u002Fautospec --skill autospec-monitor","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fberlinguyinca\u002Fautospec\u002Fblob\u002Fmain\u002Fskills\u002Fautospec-monitor\u002FSKILL.md",true,[63,69,75,79,83],{"path":64,"resourceType":65,"resourceTypeDesc":66,"sizeBytes":67,"sourceHtmlUrl":68},"codex\u002Fprompt.md","REFERENCE","参考文档",3194,"https:\u002F\u002Fgithub.com\u002Fberlinguyinca\u002Fautospec\u002Fblob\u002Fmain\u002Fskills\u002Fautospec-monitor\u002Fcodex\u002Fprompt.md",{"path":70,"resourceType":71,"resourceTypeDesc":72,"sizeBytes":73,"sourceHtmlUrl":74},"install.sh","SCRIPT","脚本",2651,"https:\u002F\u002Fgithub.com\u002Fberlinguyinca\u002Fautospec\u002Fblob\u002Fmain\u002Fskills\u002Fautospec-monitor\u002Finstall.sh",{"path":76,"resourceType":65,"resourceTypeDesc":66,"sizeBytes":77,"sourceHtmlUrl":78},"opencode\u002Fagent.md",3404,"https:\u002F\u002Fgithub.com\u002Fberlinguyinca\u002Fautospec\u002Fblob\u002Fmain\u002Fskills\u002Fautospec-monitor\u002Fopencode\u002Fagent.md",{"path":80,"resourceType":65,"resourceTypeDesc":66,"sizeBytes":81,"sourceHtmlUrl":82},"README.md",619,"https:\u002F\u002Fgithub.com\u002Fberlinguyinca\u002Fautospec\u002Fblob\u002Fmain\u002Fskills\u002Fautospec-monitor\u002FREADME.md",{"path":84,"resourceType":71,"resourceTypeDesc":72,"sizeBytes":85,"sourceHtmlUrl":86},"uninstall.sh",1354,"https:\u002F\u002Fgithub.com\u002Fberlinguyinca\u002Fautospec\u002Fblob\u002Fmain\u002Fskills\u002Fautospec-monitor\u002Funinstall.sh",[88,101,110,119,146,170],{"skillNo":89,"name":90,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":98,"publishedAt":36},"01M71RJHYMKPTC9AAPXWQ6F4RT","trio-pass-skill","https:\u002F\u002Fgithub.com\u002Fberlinguyinca\u002Fautospec\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Flockstep-trio-pass\u002FSKILL.md",[93],{"categoryNo":94,"categoryName":95,"taxonomyType":96,"taxonomyTypeDesc":97},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[99,100],"trio","trio pass skill",{"skillNo":102,"name":103,"nameZh":6,"description":6,"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":107,"publishedAt":36},"01M71RJFBQ1KAF9XM3T3Y4VMSK","duo-pass-skill","https:\u002F\u002Fgithub.com\u002Fberlinguyinca\u002Fautospec\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Flockstep-duo-pass\u002FSKILL.md",[106],{"categoryNo":94,"categoryName":95,"taxonomyType":96,"taxonomyTypeDesc":97},[108,109],"duo pass skill","duo",{"skillNo":111,"name":112,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":113,"categories":114,"keywords":116,"publishedAt":36},"01M71RJDT1TB3P9TRWR6A534FB","duo-divergence-skill","https:\u002F\u002Fgithub.com\u002Fberlinguyinca\u002Fautospec\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Flockstep-duo-divergence\u002FSKILL.md",[115],{"categoryNo":94,"categoryName":95,"taxonomyType":96,"taxonomyTypeDesc":97},[117,109,118],"duo divergence skill","divergence",{"skillNo":120,"name":20,"nameZh":6,"description":121,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":122,"categories":123,"keywords":127,"publishedAt":36},"01M71RJAC4NNEQSYBDSY3NZS73","Use when the user wants to ship a feature end-to-end across multiple commits — bootstraps repo if missing, brainstorms a design spec, decomposes into linked GitHub issues, or splits an existing spec into issues, then runs an autonomous implementation loop with auto-merge.","https:\u002F\u002Fgithub.com\u002Fberlinguyinca\u002Fautospec\u002Fblob\u002Fmain\u002Fskills\u002Fautospec\u002FSKILL.md",[124],{"categoryNo":125,"categoryName":126,"taxonomyType":96,"taxonomyTypeDesc":97},"01JBSEEDCAT000000000000015","视觉设计",[20,128,129,130,131,25,132,133,134,135,136,137,138,139,140,141,142,143,144,145],"ship a feature","end","issues","design","auto","loop","when","across","design spec","merge","ship","implementation loop","github issues","feature","commits","repo","missing","use",{"skillNo":147,"name":148,"nameZh":6,"description":149,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":150,"categories":151,"keywords":152,"publishedAt":36},"01M71RJ4F9HT8PT26CKNM9XE1M","autospec-upgrade","Use when the user wants to upgrade an Angular, Next.js, or React project to the latest official versions safely — by locking observable behavior before touching versions, upgrading one major at a time with official codemods, and gating completion on mutation score rather than coverage theater.","https:\u002F\u002Fgithub.com\u002Fberlinguyinca\u002Fautospec\u002Fblob\u002Fmain\u002Fskills\u002Fautospec-upgrade\u002FSKILL.md",[],[153,20,154,155,156,157,158,159,160,134,161,162,163,164,145,165,166,167,168,169],"autospec upgrade","upgrade","mutation","coverage","official","project","time","gating","angular","react","next","at","Next.js","one","with","behavior","latest",{"skillNo":171,"name":172,"nameZh":6,"description":173,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":174,"categories":175,"keywords":181,"publishedAt":36},"01M71RJ28FJ4PM6DXHB7T5CF8H","autospec-ui-audit","Use when a React Router application needs a deterministic whole-site route inventory before UI, UX, navigation, or evidence auditing begins.","https:\u002F\u002Fgithub.com\u002Fberlinguyinca\u002Fautospec\u002Fblob\u002Fmain\u002Fskills\u002Fautospec-ui-audit\u002FSKILL.md",[176],{"categoryNo":177,"categoryName":178,"taxonomyType":179,"taxonomyTypeDesc":180},"01JBSEEDCAT000000000000032","设计师","PROFESSION","适用职业",[182,20,183,184,185,145,186,187,188,189,190,191,192,193,194,162,195,134,196],"ui audit","audit","autospec ui audit","ui","inventory","evidence","deterministic","route","ux","site","react router","navigation","application","needs","router"]