[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M77WDHP88VBDYK1N5NH2R32N":3,"skill-same:01M77WDHP88VBDYK1N5NH2R32N":47},{"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":31,"updatedAt":32,"install":33,"resources":46},"01M77WDHP88VBDYK1N5NH2R32N","create-connector",null,"Build or repair a Collection Profile connector with the current agent and shared Factory checks. Use when a requested source has no connector or a connector needs implementation. Export evidence and API preparation are supported.","vana-com\u002Fvana-cli","vana-com","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F123112561?v=4","01M77WCAG7S42PDY7VTEVWXQD1","Vana","01M77WCAGV436KWGZWHNHZXGVH",2,"MIT","https:\u002F\u002Fgithub.com\u002Fvana-com\u002Fvana-cli\u002Fblob\u002Fmain\u002Fskills\u002Fcreate-connector\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: create-connector\ndescription: >\n  Build or repair a Collection Profile connector with the current agent and\n  shared Factory checks. Use when a requested source has no connector or a\n  connector needs implementation. Export evidence and API preparation are supported.\n---\n\n# Create a connector\n\nRead workflows with `vana skills show \u003Cid> --json`. The response includes full\ninstructions and required reference content; installation into the agent's\nharness is optional. Use `connect-data`, `create-connector` or `builder` as the\nrequested goal needs them.\n\nTake the user's source and data goal through implementation, checks, one real\nCLI collection, and a check that the intended Personal Server stored it.\nContinue through those steps from one request. Ask for source\u002Faccount choices,\nhuman authentication, or an action that needs the user's decision. The\n[walkthrough](https:\u002F\u002Fgithub.com\u002Fvana-com\u002Fvana-cli\u002Fblob\u002Fmain\u002Fskills\u002FREADME.md)\nshows the commands beside the user's part of each step.\n\nReuse completed discovery from the current task. Otherwise check both\n`vana sources --json` and upstream's current connectors before creating one.\nA catalog failure is not evidence of an unsupported provider. Use an existing\nimplementation when it satisfies the requested data goal.\n\nStart with the instructions bundled in the installed Vana CLI. This command\nworks offline without installing an agent skill or Factory.\n\n```bash\nvana connectors build --instructions --json\n```\n\nThe current agent writes and repairs the connector. Factory supplies the\nexplicit job, private work instructions and executable checks. Do not launch\nanother coding agent or service.\n\n1. Read the bundled instructions. They include the public data-connectors\n   checkout, its locked dependency installation and how to select a compatible\n   Factory executable. Use synthetic or explicitly\n   reviewed evidence and a real Node 24 runtime on macOS or Linux; Node 24.22.1\n   is recommended for both Factory and the checkout.\n2. Save a version 1 request file with absolute checkout\u002Fevidence paths, source\n   identity, directory key, exact manifest key, requested streams, and export\n   environment variable name or API preparation plan. The bundled instructions\n   include a source-general API example. Declare names rather than credential\n   values.\n   Directory and manifest keys must match after underscore\u002Fhyphen normalization.\n   Run `\"${VANA_FACTORY_BUILD-factory-build}\" capabilities --include-fixtures --json`\n   before building. This probes the configured executable or uses PATH when the\n   override is unset.\n   When it reports `fixtureTestsVersion: 1`, declare `fixtureTests` in the initial request.\n   Name the connector-local tests that will prove collection with synthetic data.\n   The names are fixed for the job. Write the files before running check and\n   register at least one passing `node:test` case directly in each named file.\n3. Run `vana connectors build --request \u002Fabsolute\u002Fpath\u002Fto\u002Frequest.json --json`.\n   Read the returned private `workFile`. For an API, run `actions.prepare.argv`\n   for the same UUID and state directory. Explicit prepare acquires only declared\n   fetch or GET inputs. Supplied synthetic or reviewed research and responses\n   also work offline without credential values. Missing inputs preserve the job.\n   Supply them and prepare again. Successful repeated preparation verifies its\n   accepted artifacts without network. Changed accepted inputs need a new job.\n   Read safe `api.md`, research, profiles and fixtures, then implement in the\n   named checkout. Raw captures are private and are not linked for the agent.\n   Factory validates stream schemas with `type`, `properties`, `required`,\n   `items`, `enum`, `format: date-time`, `minLength` and boolean\n   `additionalProperties`. Other assertions need explicit unsupported handling;\n   do not remove constraints to obtain a pass.\n4. Run the returned `actions.check.argv`. Repair failures and check the same\n   job again. Use `actions.resume.argv` to refresh work or continue after\n   export prerequisites. Resume and check never acquire API evidence. An API\n   check before preparation returns `agent_work` with reason `prepare`. Use\n   prepare after supplying API prerequisites. All commands retain the explicit\n   UUID and canonical state directory. Never infer a latest job or read private job state as an API.\n5. A `checks_passed` result covers `static_and_fixture` checks. Live\n   verification remains `pending`; ingestion remains `not_run`. The returned\n   connect action verifies the same Vana run before result\u002Fcheckpoint writes\n   and ingestion. Independent server readback remains a separate proof.\n6. Only a pass offers `actions.connect.argv`. Preserve its exact directory\n   spelling, checkout and requested streams. Supply the required environment\n   names derived from `collectionContext.access` when needed. Continue the\n   original authorized collection request; ask only for missing account, scope, authentication or a\n   blocked decision. Collection and registration are never started by a build.\n\nAPI preparation supports bounded JSON GET samples and public documentation,\nwith none, named-header, Bearer or Token auth references. It has no discovery,\nautomatic retries or pagination. Review declared structural fields and tokens.\nPrepared synthetic fixtures still require review before publication. Browser\npreparation remains unsupported. Do not imply live provider proof. Missing\nprerequisites need a person; global `--yes`, `--no-input`, `--ipc` and `--network` do not grant\nnew source access. `--detach` is unsupported; `--quiet` hides progress only.\n\n## Collect once through Vana\n\nRead Connect Data with `vana skills show connect-data --json` for discovery,\nidentity, server readiness, authentication and result inspection. Preserve the\nperson's owner, network, `VANA_HOME` and Account deployment, and use the same\nCLI entry point throughout. For local CLI work, build the actual checkout with\n`pnpm build` and use its absolute `dist\u002Fcli\u002Fbin.js` path in place of `vana`.\n\nWriting and checking the connector does not require Vana sign-in. Before a\nreal-account collection, follow Connect Data's account\u002Fserver preparation:\nVana sign-in, server readiness and CLI approval precede source-token entry or\nprovider reads. Readiness failures include a recovery command; preserve the\noriginal source, checkout path and streams through that recovery.\n\nHave the person use the interactive CLI for secrets. Supply the exact command\nwith the real key, checkout, streams and selected network, not a token\nplaceholder they might paste into chat. Keep credentials out of chat, shell\narguments, scripts and logs. Inspect `vana data show \u003Ckey> --json`,\n`vana data path \u003Ckey>` and `vana logs \u003Ckey>` without another provider run, and\ndistinguish `connected_and_ingested` from `connected_local_only`; checks alone\nestablish neither.\n\nRepeated development may use `vana connectors add \u003Ckey> --from \u003Ccheckout>`.\nThat saves a persistent override which also affects collect, schedules and\nMCP; one-off acceptance needs only `--from`. Remove an unwanted override with\n`vana connectors remove \u003Ckey>`. App consent, reading and delivery belong to\nthe Builder workflow. Native availability, signed release and publication are\nseparate work, not a side effect of a local test.\n","# Create a connector\n\nRead workflows with `vana skills show \u003Cid> --json`. The response includes full\ninstructions and required reference content; installation into the agent's\nharness is optional. Use `connect-data`, `create-connector` or `builder` as the\nrequested goal needs them.\n\nTake the user's source and data goal through implementation, checks, one real\nCLI collection, and a check that the intended Personal Server stored it.\nContinue through those steps from one request. Ask for source\u002Faccount choices,\nhuman authentication, or an action that needs the user's decision. The\n[walkthrough](https:\u002F\u002Fgithub.com\u002Fvana-com\u002Fvana-cli\u002Fblob\u002Fmain\u002Fskills\u002FREADME.md)\nshows the commands beside the user's part of each step.\n\nReuse completed discovery from the current task. Otherwise check both\n`vana sources --json` and upstream's current connectors before creating one.\nA catalog failure is not evidence of an unsupported provider. Use an existing\nimplementation when it satisfies the requested data goal.\n\nStart with the instructions bundled in the installed Vana CLI. This command\nworks offline without installing an agent skill or Factory.\n\n```bash\nvana connectors build --instructions --json\n```\n\nThe current agent writes and repairs the connector. Factory supplies the\nexplicit job, private work instructions and executable checks. Do not launch\nanother coding agent or service.\n\n1. Read the bundled instructions. They include the public data-connectors\n   checkout, its locked dependency installation and how to select a compatible\n   Factory executable. Use synthetic or explicitly\n   reviewed evidence and a real Node 24 runtime on macOS or Linux; Node 24.22.1\n   is recommended for both Factory and the checkout.\n2. Save a version 1 request file with absolute checkout\u002Fevidence paths, source\n   identity, directory key, exact manifest key, requested streams, and export\n   environment variable name or API preparation plan. The bundled instructions\n   include a source-general API example. Declare names rather than credential\n   values.\n   Directory and manifest keys must match after underscore\u002Fhyphen normalization.\n   Run `\"${VANA_FACTORY_BUILD-factory-build}\" capabilities --include-fixtures --json`\n   before building. This probes the configured executable or uses PATH when the\n   override is unset.\n   When it reports `fixtureTestsVersion: 1`, declare `fixtureTests` in the initial request.\n   Name the connector-local tests that will prove collection with synthetic data.\n   The names are fixed for the job. Write the files before running check and\n   register at least one passing `node:test` case directly in each named file.\n3. Run `vana connectors build --request \u002Fabsolute\u002Fpath\u002Fto\u002Frequest.json --json`.\n   Read the returned private `workFile`. For an API, run `actions.prepare.argv`\n   for the same UUID and state directory. Explicit prepare acquires only declared\n   fetch or GET inputs. Supplied synthetic or reviewed research and responses\n   also work offline without credential values. Missing inputs preserve the job.\n   Supply them and prepare again. Successful repeated preparation verifies its\n   accepted artifacts without network. Changed accepted inputs need a new job.\n   Read safe `api.md`, research, profiles and fixtures, then implement in the\n   named checkout. Raw captures are private and are not linked for the agent.\n   Factory validates stream schemas with `type`, `properties`, `required`,\n   `items`, `enum`, `format: date-time`, `minLength` and boolean\n   `additionalProperties`. Other assertions need explicit unsupported handling;\n   do not remove constraints to obtain a pass.\n4. Run the returned `actions.check.argv`. Repair failures and check the same\n   job again. Use `actions.resume.argv` to refresh work or continue after\n   export prerequisites. Resume and check never acquire API evidence. An API\n   check before preparation returns `agent_work` with reason `prepare`. Use\n   prepare after supplying API prerequisites. All commands retain the explicit\n   UUID and canonical state directory. Never infer a latest job or read private job state as an API.\n5. A `checks_passed` result covers `static_and_fixture` checks. Live\n   verification remains `pending`; ingestion remains `not_run`. The returned\n   connect action verifies the same Vana run before result\u002Fcheckpoint writes\n   and ingestion. Independent server readback remains a separate proof.\n6. Only a pass offers `actions.connect.argv`. Preserve its exact directory\n   spelling, checkout and requested streams. Supply the required environment\n   names derived from `collectionContext.access` when needed. Continue the\n   original authorized collection request; ask only for missing account, scope, authentication or a\n   blocked decision. Collection and registration are never started by a build.\n\nAPI preparation supports bounded JSON GET samples and public documentation,\nwith none, named-header, Bearer or Token auth references. It has no discovery,\nautomatic retries or pagination. Review declared structural fields and tokens.\nPrepared synthetic fixtures still require review before publication. Browser\npreparation remains unsupported. Do not imply live provider proof. Missing\nprerequisites need a person; global `--yes`, `--no-input`, `--ipc` and `--network` do not grant\nnew source access. `--detach` is unsupported; `--quiet` hides progress only.\n\n## Collect once through Vana\n\nRead Connect Data with `vana skills show connect-data --json` for discovery,\nidentity, server readiness, authentication and result inspection. Preserve the\nperson's owner, network, `VANA_HOME` and Account deployment, and use the same\nCLI entry point throughout. For local CLI work, build the actual checkout with\n`pnpm build` and use its absolute `dist\u002Fcli\u002Fbin.js` path in place of `vana`.\n\nWriting and checking the connector does not require Vana sign-in. Before a\nreal-account collection, follow Connect Data's account\u002Fserver preparation:\nVana sign-in, server readiness and CLI approval precede source-token entry or\nprovider reads. Readiness failures include a recovery command; preserve the\noriginal source, checkout path and streams through that recovery.\n\nHave the person use the interactive CLI for secrets. Supply the exact command\nwith the real key, checkout, streams and selected network, not a token\nplaceholder they might paste into chat. Keep credentials out of chat, shell\narguments, scripts and logs. Inspect `vana data show \u003Ckey> --json`,\n`vana data path \u003Ckey>` and `vana logs \u003Ckey>` without another provider run, and\ndistinguish `connected_and_ingested` from `connected_local_only`; checks alone\nestablish neither.\n\nRepeated development may use `vana connectors add \u003Ckey> --from \u003Ccheckout>`.\nThat saves a persistent override which also affects collect, schedules and\nMCP; one-off acceptance needs only `--from`. Remove an unwanted override with\n`vana connectors remove \u003Ckey>`. App consent, reading and delivery belong to\nthe Builder workflow. Native availability, signed release and publication are\nseparate work, not a side effect of a local test.\n",{"name":5,"description":7},"main","a55d0a0006da6a743b6452796435afa6ed177dd8","skills\u002Fcreate-connector",0,"https:\u002F\u002Fgithub.com\u002Fvana-com\u002Fvana-cli","https:\u002F\u002Fgithub.com\u002Fvana-com","https:\u002F\u002Fvana.org","The first open protocol for data sovereignty.","2026-11-13 18:19:18",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add vana-com\u002Fvana-cli --skill create-connector",{"tool":39,"command":40},"bunx","bunx skills add vana-com\u002Fvana-cli --skill create-connector",{"tool":42,"command":43},"pnpm","pnpm dlx skills add vana-com\u002Fvana-cli --skill create-connector","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fvana-com\u002Fvana-cli\u002Fblob\u002Fmain\u002Fskills\u002Fcreate-connector\u002FSKILL.md",true,[],[48,55,62,69,76,83],{"skillNo":49,"name":50,"nameZh":6,"description":51,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":52,"categories":53,"keywords":54,"publishedAt":19},"01M7BD5YJ16KD0X3M379XA2A4A","verify-setup-resume","Verify BUI-936 setup\u002Fresume identities, funding readiness and overlapping resumes. Use when changing app request, test-credit transport or the request journal. Runs bounded TLA+ checks and offline real-code replays without live funding or paid reads.","https:\u002F\u002Fgithub.com\u002Fvana-com\u002Fvana-cli\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fverify-setup-resume\u002FSKILL.md",[],[],{"skillNo":56,"name":57,"nameZh":6,"description":58,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":59,"categories":60,"keywords":61,"publishedAt":19},"01M7BD5V2155AM7W1PWRBY237Y","verify-server-supervision","Verify the local Personal Server stop and restart boundary. Use when changing the supervisor's backoff, port probing, replacement launch or Stop handling.","https:\u002F\u002Fgithub.com\u002Fvana-com\u002Fvana-cli\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fverify-server-supervision\u002FSKILL.md",[],[],{"skillNo":63,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":66,"categories":67,"keywords":68,"publishedAt":19},"01M7BD5PPVKFVVGS9B846B99ES","verify-paid-read-recovery","Verify interrupted and overlapping CLI paid reads, receipt-file writers and dead-owner recovery. Use when changing src\u002Fcli\u002Fapp\u002Fread.ts, src\u002Fcore\u002Freceipts.ts or src\u002Fcore\u002Freceipts-lock.ts. Runs TLA+ models and offline real-code replays without live paid reads.","https:\u002F\u002Fgithub.com\u002Fvana-com\u002Fvana-cli\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fverify-paid-read-recovery\u002FSKILL.md",[],[],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":19},"01M7BD5JDEGV165NFZJWSWJBN4","verify-mainnet-registration","Verify mainnet app registration and Account association recovery. Use for the registration journal, gateway confirmation, retry, or ownership check.","https:\u002F\u002Fgithub.com\u002Fvana-com\u002Fvana-cli\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fverify-mainnet-registration\u002FSKILL.md",[],[],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":19},"01M7BD5ETK33JAD1F1XQXGPYYG","verify-hosted-provisioning","Verify hosted Personal Server resource ownership across create and delete. Use for Connect's server API, provisioning-row updates, or deprovisioning admission.","https:\u002F\u002Fgithub.com\u002Fvana-com\u002Fvana-cli\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fverify-hosted-provisioning\u002FSKILL.md",[],[],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":19},"01M7BD5BBKFHJ86JFBE8KT1S78","verify-export-settlement","Verify queued export owner binding and generation settlement. Use for result publication, pending upload receipts, or retry and sync changes.","https:\u002F\u002Fgithub.com\u002Fvana-com\u002Fvana-cli\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fverify-export-settlement\u002FSKILL.md",[],[]]