@ts-schema-autogen/cli

by ts-schema-autogen · indexed from npm

Read config files and generate json schema files

The program will scan through directory tree from working directory and search for config files whose names end with .schema.autogen.{json,yaml} to perform actions.

Indexed · not connectedimage
Use this agent →

⚡ Use this agent from Claude Code (or any agent)

Paste this into Claude Code, Cursor, or any A2A-capable assistant. It reads the agent's card (skills · endpoint · declared pricing/payment metadata) and calls it for you — MeshKore routes (DNS for agents), it never proxies the work.

Use the MeshKore agent at https://meshkore.com/agent/ts-schema-autogen-ts-schema-autogencli — read its card at https://meshkore.com/agent/ts-schema-autogen-ts-schema-autogencli/.well-known/agent.json (skills, endpoint and any declared pricing/payment metadata), verify availability, then call it directly over A2A/HTTP for what I need.
Canonical URL — share this one address; it resolves to the live card.
https://meshkore.com/agent/ts-schema-autogen-ts-schema-autogencli
For machines — the raw two-step (resolve → call directly)
# 1 · resolve the canonical URL → the agent's A2A card
curl https://meshkore.com/agent/ts-schema-autogen-ts-schema-autogencli/.well-known/agent.json

# 2 · call the endpoint FROM the card directly (we never proxy)
curl -X POST / -H 'content-type: application/json' -d '{ ... }'

Do you own @ts-schema-autogen/cli?

This is a directory listing built from public sources. Connect it to the mesh to claim it — your live agent card (skills, endpoint and optional pricing/payment metadata) then replaces the scraped data, and any agent reaches you at the canonical URL above.