create-connector
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.
- License 许可
- MIT
- 最近更新
- 2026-11-13
- Stars
- ★ 2
- Forks
- 0
01 前言 Front Matter
- name
- create-connector
- description
- 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.
03 SKILL.md 正文
Create a connector
Read workflows with vana skills show <id> --json. The response includes full
instructions and required reference content; installation into the agent's
harness is optional. Use connect-data, create-connector or builder as the
requested goal needs them.
Take the user's source and data goal through implementation, checks, one real CLI collection, and a check that the intended Personal Server stored it. Continue through those steps from one request. Ask for source/account choices, human authentication, or an action that needs the user's decision. The walkthrough shows the commands beside the user's part of each step.
Reuse completed discovery from the current task. Otherwise check both
vana sources --json and upstream's current connectors before creating one.
A catalog failure is not evidence of an unsupported provider. Use an existing
implementation when it satisfies the requested data goal.
Start with the instructions bundled in the installed Vana CLI. This command works offline without installing an agent skill or Factory.
vana connectors build --instructions --json
The current agent writes and repairs the connector. Factory supplies the explicit job, private work instructions and executable checks. Do not launch another coding agent or service.
- Read the bundled instructions. They include the public data-connectors checkout, its locked dependency installation and how to select a compatible Factory executable. Use synthetic or explicitly reviewed evidence and a real Node 24 runtime on macOS or Linux; Node 24.22.1 is recommended for both Factory and the checkout.
- Save a version 1 request file with absolute checkout/evidence paths, source
identity, directory key, exact manifest key, requested streams, and export
environment variable name or API preparation plan. The bundled instructions
include a source-general API example. Declare names rather than credential
values.
Directory and manifest keys must match after underscore/hyphen normalization.
Run
"${VANA_FACTORY_BUILD-factory-build}" capabilities --include-fixtures --jsonbefore building. This probes the configured executable or uses PATH when the override is unset. When it reportsfixtureTestsVersion: 1, declarefixtureTestsin the initial request. Name the connector-local tests that will prove collection with synthetic data. The names are fixed for the job. Write the files before running check and register at least one passingnode:testcase directly in each named file. - Run
vana connectors build --request /absolute/path/to/request.json --json. Read the returned privateworkFile. For an API, runactions.prepare.argvfor the same UUID and state directory. Explicit prepare acquires only declared fetch or GET inputs. Supplied synthetic or reviewed research and responses also work offline without credential values. Missing inputs preserve the job. Supply them and prepare again. Successful repeated preparation verifies its accepted artifacts without network. Changed accepted inputs need a new job. Read safeapi.md, research, profiles and fixtures, then implement in the named checkout. Raw captures are private and are not linked for the agent. Factory validates stream schemas withtype,properties,required,items,enum,format: date-time,minLengthand booleanadditionalProperties. Other assertions need explicit unsupported handling; do not remove constraints to obtain a pass. - Run the returned
actions.check.argv. Repair failures and check the same job again. Useactions.resume.argvto refresh work or continue after export prerequisites. Resume and check never acquire API evidence. An API check before preparation returnsagent_workwith reasonprepare. Use prepare after supplying API prerequisites. All commands retain the explicit UUID and canonical state directory. Never infer a latest job or read private job state as an API. - A
checks_passedresult coversstatic_and_fixturechecks. Live verification remainspending; ingestion remainsnot_run. The returned connect action verifies the same Vana run before result/checkpoint writes and ingestion. Independent server readback remains a separate proof. - Only a pass offers
actions.connect.argv. Preserve its exact directory spelling, checkout and requested streams. Supply the required environment names derived fromcollectionContext.accesswhen needed. Continue the original authorized collection request; ask only for missing account, scope, authentication or a blocked decision. Collection and registration are never started by a build.
API preparation supports bounded JSON GET samples and public documentation,
with none, named-header, Bearer or Token auth references. It has no discovery,
automatic retries or pagination. Review declared structural fields and tokens.
Prepared synthetic fixtures still require review before publication. Browser
preparation remains unsupported. Do not imply live provider proof. Missing
prerequisites need a person; global --yes, --no-input, --ipc and --network do not grant
new source access. --detach is unsupported; --quiet hides progress only.
Collect once through Vana
Read Connect Data with vana skills show connect-data --json for discovery,
identity, server readiness, authentication and result inspection. Preserve the
person's owner, network, VANA_HOME and Account deployment, and use the same
CLI entry point throughout. For local CLI work, build the actual checkout with
pnpm build and use its absolute dist/cli/bin.js path in place of vana.
Writing and checking the connector does not require Vana sign-in. Before a real-account collection, follow Connect Data's account/server preparation: Vana sign-in, server readiness and CLI approval precede source-token entry or provider reads. Readiness failures include a recovery command; preserve the original source, checkout path and streams through that recovery.
Have the person use the interactive CLI for secrets. Supply the exact command
with the real key, checkout, streams and selected network, not a token
placeholder they might paste into chat. Keep credentials out of chat, shell
arguments, scripts and logs. Inspect vana data show <key> --json,
vana data path <key> and vana logs <key> without another provider run, and
distinguish connected_and_ingested from connected_local_only; checks alone
establish neither.
Repeated development may use vana connectors add <key> --from <checkout>.
That saves a persistent override which also affects collect, schedules and
MCP; one-off acceptance needs only --from. Remove an unwanted override with
vana connectors remove <key>. App consent, reading and delivery belong to
the Builder workflow. Native availability, signed release and publication are
separate work, not a side effect of a local test.
04 同仓库更多 Skills
verify-setup-resume
Verify BUI-936 setup/resume 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.
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.
verify-paid-read-recovery
Verify interrupted and overlapping CLI paid reads, receipt-file writers and dead-owner recovery. Use when changing src/cli/app/read.ts, src/core/receipts.ts or src/core/receipts-lock.ts. Runs TLA+ models and offline real-code replays without live paid reads.
verify-mainnet-registration
Verify mainnet app registration and Account association recovery. Use for the registration journal, gateway confirmation, retry, or ownership check.
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.
verify-export-settlement
Verify queued export owner binding and generation settlement. Use for result publication, pending upload receipts, or retry and sync changes.