Problem
Agents and scripts operating with Tink frequently need to know:
- The active
$TINK_HOME directory.
- The resolved path to the catalog (
$TINK_HOME/catalog/by-project and by-skillset).
- The resolved library path (
$TINK_HOME/skills).
- Whether the current working directory is inside an active project (
.agents/skills/), inside $TINK_HOME, or neither.
Currently, agents have to infer these locations or inspect internal directories directly, which violates encapsulation and can fail if environment variables or home directories differ.
Proposed change
Add a tink info (or tink env) command that outputs resolved configuration and paths:
$ tink info
Tink version: 1.0.7
Home: /Users/jondev/.tink
Catalog: /Users/jondev/.tink/catalog
Library: /Users/jondev/.tink/skills
Active project: /path/to/project (or None)
With --json, emit a structured payload suitable for scripts and agent context initialization:
{
"version": "1.0.7",
"home": "/Users/jondev/.tink",
"catalog": "/Users/jondev/.tink/catalog",
"library": "/Users/jondev/.tink/skills",
"activeProject": null
}
Acceptance
Problem
Agents and scripts operating with Tink frequently need to know:
$TINK_HOMEdirectory.$TINK_HOME/catalog/by-projectandby-skillset).$TINK_HOME/skills)..agents/skills/), inside$TINK_HOME, or neither.Currently, agents have to infer these locations or inspect internal directories directly, which violates encapsulation and can fail if environment variables or home directories differ.
Proposed change
Add a
tink info(ortink env) command that outputs resolved configuration and paths:With
--json, emit a structured payload suitable for scripts and agent context initialization:{ "version": "1.0.7", "home": "/Users/jondev/.tink", "catalog": "/Users/jondev/.tink/catalog", "library": "/Users/jondev/.tink/skills", "activeProject": null }Acceptance
tink infoprints version, resolved home, catalog, library paths, and active project root (if detected).tink info --jsonoutputs structured JSON.