What Career Context supplies
- User-supplied roles, projects, education, and credentials.
- Stated goals, interests, and preferred direction.
- Proof links, constraints, and claims to avoid.
- A reusable file that can be inspected and corrected.
Documentation · workflow
How VitaeContext works
Keep career context in files you can inspect. Use one focused method for the task in front of you.
Core workflow
Context first. Task second.
VitaeContext gives an agent a stable starting point instead of rebuilding career history inside every conversation.
- 01
Gather trusted material
Start with CVs, profile text, project notes, links, exports, and other material you can inspect.
- 02
Create career context
Use the context skill to organize facts, stated goals, evidence, constraints, and claims to avoid in Markdown.
- 03
Choose one method
Load the skill for the current CV, profile, repository, portfolio, message, interview, or other task.
- 04
Review the result
Check that claims stay supported, goals remain separate from experience, and missing evidence is visible.
What a skill supplies
- A task-specific workflow.
- Platform constraints and source-aware guidance.
- Expected inputs and useful output formats.
- A self-review for evidence, scope, and fabrication.
A maintained input
How is Career Context different?
Career Context is the broad, inspectable source supplied before a task. It is not another public profile or a provider-specific memory feature.
Is Career Context private?
VitaeContext is a local CLI and readable Markdown skill package with no project backend collecting Career Context. You choose where the file lives and what to supply to an agent. After you share content with an external provider, that provider's data rules apply.
Does VitaeContext verify claims?
No. It organizes user-supplied facts, stated goals, proof references, and claims to avoid. Its skills tell agents to preserve those boundaries and flag missing evidence, but generated work can still contain errors and requires human review.
Normal prompt
Give the context and name the task.
Exact invocation differs by provider. Explicitly name the installed skill when possible.
Use vitaecontext-github.
Read my career context file at ~/.vitaecontext/name-surname-career-context.md.
Audit my GitHub profile and list the changes I should make first.
Do not add claims that are not supported by the file.Option A: Command task packet
Run npx vitaecontext context summary <file> --for github to create a bounded Markdown packet for one platform. Good for manual AI chat sessions or direct copy-paste.
Option B: Cross-workspace MCP
Configure the stateless MCP server (npx -y vitaecontext-mcp). Your AI coding assistants across all project repositories can query your private context and VitaeGraph dynamically without copying files.