Name: carryctx-docs
Author: Xuepoo

Imported from Xuepoo/carryctx-docs (AGENTS.md). Install upstream with npx skills add Xuepoo/carryctx-docs. Copyright stays with the author.

CarryCtx Documentation Repository Instructions

Scope

This repository is the source of truth for the CarryCtx product, CLI contracts, storage model, engineering rules, delivery plans, workflows, roadmaps, and verification reports.

Authoring rules

Keep requirements, CLI behavior, configuration, architecture, and implementation aligned.
Resolve contradictions instead of documenting both variants as valid.
Use config.toml and config.local.toml; runtime project state belongs in the Git common directory.
Treat JSON envelopes, exit codes, command names, and configuration keys as public contracts.
Label features as v0.1, P1, P2, experimental, or future consistently across documents.
Prefer concrete examples, explicit invariants, and testable acceptance criteria.
Do not store temporary logs or generated package artifacts here; place them in ../recording/.
Test reports committed under reports/ must include commands, dates, tool versions, outcomes, and any known gaps.

Change coupling

When CLI implementation changes documented behavior, update the affected document in the same workstream. Architecture decisions and implementation plans belong in this repository even though code lives in ../carryctx-cli/.

# after Install: the listing is in your workspace's routing pool - a plan picks it for its slot curl -s -X POST https://api.opensmartroute.ai/api/v1/route -H 'Authorization: Bearer $OSR_API_KEY' -H 'Content-Type: application/json' -d '{"text": "...", "plan": true}'

Install carryctx-docs and it becomes one more candidate the router can pick - when it fits.

A listing is a routing target with a manifest: what it does, which domains it covers, what it costs and who publishes it. Once installed it sits beside your own models and tools, is scored like any other candidate for each request, and shows up in the trace when it wins. Ratings come from workspaces that installed it, one per account.

{ "ocm": "1", "id": "xuepoo-carryctx-docs-carryctx-docs", "kind": "skill", "name": "carryctx-docs", "description": "This repository is the source of truth for the CarryCtx product, CLI contracts, storage model, engineering rules, delivery plans, workflows, roadmaps, and verification reports.", "publisher": "Xuepoo", "version": "1.0.0", "capabilities": { "domains": [ "customer_support" ], "tags": [ "skill-md", "github-agents" ], "languages": [ "en" ] }, "quality_prior": 0.6, "examples": [ "This repository is the source of truth for the CarryCtx product, CLI contracts, storage model, engineering rules, delivery plans, workflows, roadmaps, and verification reports." ], "primary": false, "metadata": { "source": { "provider": "github-agents", "repository": "https://github.com/Xuepoo/carryctx-docs", "path": "AGENTS.md", "ref": "a2dad95dcce862a01b9ec9577d3a9edf2d4ead6e", "url": "https://github.com/Xuepoo/carryctx-docs/blob/a2dad95dcce862a01b9ec9577d3a9edf2d4ead6e/AGENTS.md", "key": "Xuepoo/carryctx-docs/AGENTS.md" } }, "instructions": "# CarryCtx Documentation Repository Instructions\n\n## Scope\n\nThis repository is the source of truth for the CarryCtx product, CLI contracts, storage model, engineering rules, delivery plans, workflows, roadmaps, and verification reports.\n\n## Authoring rules\n\n- Keep requirements, CLI behavior, configuration, architecture, and implementation aligned.\n- Resolve contradictions instead of documenting both variants as valid.\n- Use `config.toml` and `config.local.toml`; runtime project state belongs in the Git common directory.\n- Treat JSON envelopes, exit codes, command names, and configuration keys ", "cost": { "context_tokens": 313 } }

carryctx-docs

About

CarryCtx Documentation Repository Instructions

Scope

Authoring rules

Change coupling

Use it

Install carryctx-docs and it becomes one more candidate the router can pick - when it fits.

Manifest

Reviews