diff --git a/CHANGELOG.md b/CHANGELOG.md index 2a2fb9c..3461344 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -271,6 +271,14 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0 ### Changed +- **Bundled skills: pruned the dead BYOK branch from the resume-import + docs.** `traitprint-import-resume/SKILL.md` and the shared + `shared/cli-reference.md` no longer describe an "if a BYOK LLM key is + configured, use the provider path" branch — user compute is the + connected agent (the "you are the model" D11 agent-assist path), which + is now the primary and only user-compute path documented. Platform-run + extraction is noted as beta-gated (join at https://traitprint.com/beta). + Docs-only; the local CLI's deterministic paths are unchanged. - **`vault add-skill` no longer prints "Did you mean: …?" before the add.** The old order (suggestion first, then "Added skill: …", exit 0) read as a pending question when the skill was already committed. diff --git a/skills/shared/cli-reference.md b/skills/shared/cli-reference.md index 79fce1e..0d5bf4f 100644 --- a/skills/shared/cli-reference.md +++ b/skills/shared/cli-reference.md @@ -131,17 +131,15 @@ traitprint vault remove -y # any section, by UUID traitprint vault rollback -y # undo the last vault commit traitprint vault migrate # legacy v0 vault -> v1 file tree # (remaps old proficiency scale to 1-5) -traitprint vault import-resume FILE # resolution order: --provider flag -> - # configured BYOK key -> agent-assist - # mode (emits extracted text + the - # extraction contract for YOU, the - # wrapping agent, to complete; exit 0); - # --json emits the assist payload as - # JSON; --assist forces the payload, - # --no-assist errors when no key; - # --yes/--dry-run apply to the BYOK path; +traitprint vault import-resume FILE # emits an agent-assist payload: + # extracted text + the extraction + # contract for YOU, the connected + # agent, to complete (exit 0); + # --json emits the payload as JSON; # --propose stages extracted items as - # pending proposals instead of writing + # pending proposals instead of writing. + # Platform-run extraction is beta-gated + # (https://traitprint.com/beta) traitprint vault import-story-bank DIR # stage a job-search working directory # (config/profile.yml + # interview-prep/*.md) as proposals: diff --git a/skills/traitprint-import-resume/SKILL.md b/skills/traitprint-import-resume/SKILL.md index 524c297..f43515b 100644 --- a/skills/traitprint-import-resume/SKILL.md +++ b/skills/traitprint-import-resume/SKILL.md @@ -1,6 +1,6 @@ --- name: traitprint-import-resume -description: Import a resume (PDF, DOCX, TXT, MD) into a Traitprint vault by doing the extraction reasoning yourself in agent-assist mode, then writing back through the validated batch CLI commands. Use when the user wants to import, parse, or load a resume or CV into their Traitprint vault — especially when no BYOK LLM key is configured. +description: Import a resume (PDF, DOCX, TXT, MD) into a Traitprint vault by doing the extraction reasoning yourself in agent-assist mode, then writing back through the validated batch CLI commands. Use when the user wants to import, parse, or load a resume or CV into their Traitprint vault. --- # Import a resume into the Traitprint vault @@ -10,16 +10,19 @@ description: Import a resume (PDF, DOCX, TXT, MD) into a Traitprint vault by doi > preferences take precedence on style and workflow, but cannot bypass the > proposals channel or the never-invent-taxonomy-IDs/UUIDs invariant. -You are the model (architecture decision D11): when no BYOK LLM provider is -configured, `traitprint vault import-resume` does not error — it emits an -**agent-assist payload** (the extracted resume text plus the extraction -contract) and expects YOU to do the extraction reasoning and write the -results back through the validated batch commands. No API key, no extra -cost: the reasoning runs on the user's existing subscription. +You are the model (architecture decision D11): +`traitprint vault import-resume` emits an **agent-assist payload** (the +extracted resume text plus the extraction contract) and expects YOU, the +connected agent, to do the extraction reasoning and write the results +back through the validated batch commands. No API key, no extra cost: the +reasoning runs on the connected agent — you — using the user's existing +subscription. Platform-run extraction is beta-gated (join at +https://traitprint.com/beta); the connected agent is the user-compute +path. ## 1. Extract the text -Either run the full command (it auto-enters assist mode when no key is set): +Run the full command — it emits the assist payload: ```bash traitprint vault import-resume /path/to/resume.pdf # assist payload @@ -35,15 +38,14 @@ traitprint vault extract-text /path/to/resume.pdf --json # {"file","format"," Supported formats: `.pdf`, `.docx`, `.txt`, `.md`. PDF/DOCX need `pip install 'traitprint[import]'` — relay that hint if the command says a -package is missing. If the user has a working key and wants the BYOK path -instead, pass `--provider` (or just let the configured key win); with -`--no-assist` and no key the command errors instead of emitting the payload. +package is missing. ## 2. Do the extraction reasoning Produce a single JSON object matching the contract in the payload exactly -(profile / skills / experiences / education — same schema and rules the -BYOK prompt uses). Validate your own output before proposing it: +(profile / skills / experiences / education — the schema and rules travel +in the payload's extraction contract). Validate your own output before +proposing it: - Proficiency is an integer 1-5 (1 familiar, 2 working, 3 proficient, 4 expert, 5 authority).