Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →vellum-self-knowledge
Answer questions about Vellum, the assistant's architecture, capabilities, and current configuration by routing to live sources of truth
4 of 22 test cases passed with the skill.
Tokens, turns and time describe resource use, not a dollar price.
Lift withheld: 4 comparable cases; this report requires 8.
One of 3 test cases the skill fixed. Same model, same prompt, with and without the skill.
What security trust policies or domain execution rules are currently enforced on this runtime?
| Checked | Without skill | With skill |
|---|---|---|
| Executes assistant trust list to evaluate trust policies. | Missed | Passed |
The instructions your model reads when the skill loads.
Never answer from memory or general knowledge about Vellum. Always go to a source of truth. This skill contains zero static information — only pointers to where the truth lives.
assistant CLI — Live Runtime StateThe CLI is the single source of truth for anything about the running assistant's current state.
| Question type | Command |
|---|---|
| Current model, provider, config | assistant config get llm |
| Full config | assistant config list |
| Config schema (what's configurable) | assistant config schema [path] |
| Available/installed skills | assistant skills list --json |
| Platform connection | assistant platform status --json |
| Auth/identity | assistant auth info --json |
| Which providers exist, and in which sense | assistant oauth providers list --json |
| Whether one is actually connected | assistant oauth status <provider> |
| Channel delivery health | assistant channels list |
| Connected clients | assistant clients list --json |
| Trust rules | assistant trust list |
| Stored credentials | assistant credentials list |
| API keys | assistant keys list |
| MCP servers | assistant mcp list |
| Watchers | assistant watchers list |
| Token usage/costs | assistant usage totals / assistant usage breakdown --group-by provider |
| Version | assistant --version |
Run assistant --help or assistant <command> --help to discover more.
"Is X connected?" has two answers and a service can have either, both, or
neither. It takes both commands: the providers list is a catalog and says
nothing about whether anything is connected, so use it to find which provider
keys belong to X, then check each with oauth status.
Each provider in that list carries its sense: actsAs in the CLI's JSON,
acts_as over HTTP. user means the assistant can act as the person who
test cases passed with the skill
More skills from the same source and nearby in the registry, with their headline benchmark lift.