[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7DM6VMSSTR8Y1TQCQNHMY5E":3,"skill-same:01M7DM6VMSSTR8Y1TQCQNHMY5E":46},{"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":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":30,"ownerDescription":6,"updatedAt":31,"install":32,"resources":45},"01M7DM6VMSSTR8Y1TQCQNHMY5E","fixture-harness",null,"Test fixture for probe P7 only. Runs a one-worker harness whose worker needs a connector called fixture. Use when the user says \"run the fixture harness\", \"re-run the fixture harness\" or \"redo the fixture check\". Not for real work.","danielnguyenfinhub\u002Ffinhub-harness","danielnguyenfinhub","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F264356854?v=4","01M7DM55XETDR9HF92FWC28SBN","Daniel Nguyen","01M7DM55YGJYBWW488JZSQYEJ4",1,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fdanielnguyenfinhub\u002Ffinhub-harness\u002Fblob\u002Fmain\u002Fdocs\u002Ffixtures\u002Fp7-fixture-harness\u002F.claude\u002Fskills\u002Ffixture-harness\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: fixture-harness\ndescription: Test fixture for probe P7 only. Runs a one-worker harness whose worker needs a connector called fixture. Use when the user says \"run the fixture harness\", \"re-run the fixture harness\" or \"redo the fixture check\". Not for real work.\n---\n\n# Fixture harness (probe P7)\n\n**Target surface:** Claude Code, Claude chat, Claude Cowork. **Execution mode:** Mode C, one worker; on chat and Cowork run it in one context (see the fallback).\n\n## Delegation gate\n\n1. Independent units: one. 2. Splitting buys nothing. 3. Writes: none. 4. The worker needs only Read. 5. This skill accepts the result. 6. A missing connector is reported, never filled in.\nOutcome: **single agent**.\n\n## Step 0: Context check and connector preflight\n\nNo `_workspace\u002F` is used. Run the connector preflight before any agent call.\n\n| Agent | Required connector |\n|-------|--------------------|\n| fixture-checker | fixture |\n\nA connector counts as present when your tool list, deferred listings included, has at least one tool whose name begins with `mcp__fixture__`.\n\n- Claude Code: if the row is absent, make no further calls. Reply with one line: `Missing connector fixture for agent fixture-checker. Attach or authorise it, then run again. Nothing was started.`\n- Claude chat or Cowork: an attached connector can stay hidden until its schema is loaded, so absence is not proof. Search for the server name with the tool-search step if there is one. If it is still absent, say `Missing connector fixture for agent fixture-checker.` and ask whether to attach it and continue, continue without it (report the worker's phase as skipped), or stop. Do not stop without asking.\n\n## Step 1: Run the worker\n\nThe worker is `fixture-checker`: its whole job is to reply `ok`. On Claude Code, call it as a sub-agent. On chat and Cowork, play the role yourself in this context, labelled `[fixture-checker]`. On chat and Cowork, delegation is unverified: do not claim a separate agent ran.\n\n## Step 2: Report\n\nFirst line: `Done` if the worker ran, `Partial` if it was skipped. Then one line saying whether the connector was present.\n\n## Single-context fallback\n\nSteps 0 to 2 run in this one context, as above. Nothing here sends, writes or publishes.\n\n## Test scenarios\n\n- Happy path: connector `fixture` attached, first line `Done`.\n- Error path (the probe): no connector attached. The skill names `fixture` and `fixture-checker`, then asks attach, continue or stop. It does not stop by itself on chat or Cowork.\n","# Fixture harness (probe P7)\n\n**Target surface:** Claude Code, Claude chat, Claude Cowork. **Execution mode:** Mode C, one worker; on chat and Cowork run it in one context (see the fallback).\n\n## Delegation gate\n\n1. Independent units: one. 2. Splitting buys nothing. 3. Writes: none. 4. The worker needs only Read. 5. This skill accepts the result. 6. A missing connector is reported, never filled in.\nOutcome: **single agent**.\n\n## Step 0: Context check and connector preflight\n\nNo `_workspace\u002F` is used. Run the connector preflight before any agent call.\n\n| Agent | Required connector |\n|-------|--------------------|\n| fixture-checker | fixture |\n\nA connector counts as present when your tool list, deferred listings included, has at least one tool whose name begins with `mcp__fixture__`.\n\n- Claude Code: if the row is absent, make no further calls. Reply with one line: `Missing connector fixture for agent fixture-checker. Attach or authorise it, then run again. Nothing was started.`\n- Claude chat or Cowork: an attached connector can stay hidden until its schema is loaded, so absence is not proof. Search for the server name with the tool-search step if there is one. If it is still absent, say `Missing connector fixture for agent fixture-checker.` and ask whether to attach it and continue, continue without it (report the worker's phase as skipped), or stop. Do not stop without asking.\n\n## Step 1: Run the worker\n\nThe worker is `fixture-checker`: its whole job is to reply `ok`. On Claude Code, call it as a sub-agent. On chat and Cowork, play the role yourself in this context, labelled `[fixture-checker]`. On chat and Cowork, delegation is unverified: do not claim a separate agent ran.\n\n## Step 2: Report\n\nFirst line: `Done` if the worker ran, `Partial` if it was skipped. Then one line saying whether the connector was present.\n\n## Single-context fallback\n\nSteps 0 to 2 run in this one context, as above. Nothing here sends, writes or publishes.\n\n## Test scenarios\n\n- Happy path: connector `fixture` attached, first line `Done`.\n- Error path (the probe): no connector attached. The skill names `fixture` and `fixture-checker`, then asks attach, continue or stop. It does not stop by itself on chat or Cowork.\n",{"name":5,"description":7},"main","dda161ff9daf0d9bccbdba26e34bbee0438a18b0","docs\u002Ffixtures\u002Fp7-fixture-harness\u002F.claude\u002Fskills\u002Ffixture-harness",0,"https:\u002F\u002Fgithub.com\u002Fdanielnguyenfinhub\u002Ffinhub-harness","https:\u002F\u002Fgithub.com\u002Fdanielnguyenfinhub","www.finhub.net.au","2026-11-12 17:07:32",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add danielnguyenfinhub\u002Ffinhub-harness --skill fixture-harness",{"tool":38,"command":39},"bunx","bunx skills add danielnguyenfinhub\u002Ffinhub-harness --skill fixture-harness",{"tool":41,"command":42},"pnpm","pnpm dlx skills add danielnguyenfinhub\u002Ffinhub-harness --skill fixture-harness","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fdanielnguyenfinhub\u002Ffinhub-harness\u002Fblob\u002Fmain\u002Fdocs\u002Ffixtures\u002Fp7-fixture-harness\u002F.claude\u002Fskills\u002Ffixture-harness\u002FSKILL.md",true,[],[47,54,61,67,73,80],{"skillNo":48,"name":49,"nameZh":6,"description":50,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":51,"categories":52,"keywords":53,"publishedAt":19},"01M7DMBP1MQ9X39BGJ9VF62M9P","linky","Fixture whose links and bundled-file mentions all resolve. Use to prove no false errors.","https:\u002F\u002Fgithub.com\u002Fdanielnguyenfinhub\u002Ffinhub-harness\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fharness_links_ok\u002Fskills\u002Flinky\u002FSKILL.md",[],[],{"skillNo":55,"name":56,"nameZh":6,"description":57,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":58,"categories":59,"keywords":60,"publishedAt":19},"01M7DMBK70KXF6A3V1VDRHYGVT","dup-one","Second owner of the name. Use for the duplicate fixture.","https:\u002F\u002Fgithub.com\u002Fdanielnguyenfinhub\u002Ffinhub-harness\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fharness_links_bad\u002Fskills\u002Fdup-two\u002FSKILL.md",[],[],{"skillNo":62,"name":56,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":19},"01M7DMBFWK8HD4AWNK89KGE89P","First owner of the name. Use for the duplicate fixture.","https:\u002F\u002Fgithub.com\u002Fdanielnguyenfinhub\u002Ffinhub-harness\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fharness_links_bad\u002Fskills\u002Fdup-one\u002FSKILL.md",[],[],{"skillNo":68,"name":69,"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":70,"categories":71,"keywords":72,"publishedAt":19},"01M7DMBETX7172TFNBAA3BVREQ","nested","https:\u002F\u002Fgithub.com\u002Fdanielnguyenfinhub\u002Ffinhub-harness\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fharness_links_bad\u002Fskills\u002Fbroken\u002Fnested\u002FSKILL.md",[],[],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":19},"01M7DMBDCH5G61QVAB1QFMQA55","broken","Fixture with one defect per rule. Use to prove each rule fires.","https:\u002F\u002Fgithub.com\u002Fdanielnguyenfinhub\u002Ffinhub-harness\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fharness_links_bad\u002Fskills\u002Fbroken\u002FSKILL.md",[],[],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":19},"01M7DMBAQHY0Z2PTYGCPM8H7MT","notes-style","House style for client notes. Use when writing or editing a client note.","https:\u002F\u002Fgithub.com\u002Fdanielnguyenfinhub\u002Ffinhub-harness\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fharness_good\u002Fskills\u002Fnotes-style\u002FSKILL.md",[],[]]