Billing Automation
wshobson/agents
Covers building subscription billing: billing cycles, subscription states, invoice generation, proration, tax handling and dunning for failed payments.
Answer questions about Vellum, its config, billing, and hosting from live sources of truth
MITAuto-check passed
Install Vellum Self Knowledge
$ npx skills add vellum-ai/vellum-assistant --skill vellum-self-knowledge -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install vellum-ai/vellum-assistant vellum-self-knowledge --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/vellum-ai/vellum-assistant.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/vellum-self-knowledge .claude/skills/vellum-self-knowledge && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "vellum-self-knowledge" agent skill from https://github.com/vellum-ai/vellum-assistant/tree/main/skills/vellum-self-knowledge into .claude/skills/vellum-self-knowledge/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vellum-self-knowledge", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/vellum-ai/vellum-assistant/tree/main/skills/vellum-self-knowledgeType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add vellum-ai/vellum-assistant --skill vellum-self-knowledge -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install vellum-ai/vellum-assistant vellum-self-knowledge --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/vellum-ai/vellum-assistant.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/vellum-self-knowledge .agents/skills/vellum-self-knowledge && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "vellum-self-knowledge" agent skill from https://github.com/vellum-ai/vellum-assistant/tree/main/skills/vellum-self-knowledge into .agents/skills/vellum-self-knowledge/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vellum-self-knowledge", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add vellum-ai/vellum-assistant --skill vellum-self-knowledge -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install vellum-ai/vellum-assistant vellum-self-knowledge --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/vellum-ai/vellum-assistant.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/vellum-self-knowledge .cursor/skills/vellum-self-knowledge && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "vellum-self-knowledge" agent skill from https://github.com/vellum-ai/vellum-assistant/tree/main/skills/vellum-self-knowledge into .cursor/skills/vellum-self-knowledge/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vellum-self-knowledge", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/vellum-ai/vellum-assistant.git --path skills/vellum-self-knowledge--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add vellum-ai/vellum-assistant --skill vellum-self-knowledge -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install vellum-ai/vellum-assistant vellum-self-knowledge --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/vellum-ai/vellum-assistant.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/vellum-self-knowledge .gemini/skills/vellum-self-knowledge && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "vellum-self-knowledge" agent skill from https://github.com/vellum-ai/vellum-assistant/tree/main/skills/vellum-self-knowledge into .gemini/skills/vellum-self-knowledge/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vellum-self-knowledge", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install vellum-ai/vellum-assistant vellum-self-knowledgeInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add vellum-ai/vellum-assistant --skill vellum-self-knowledge -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/vellum-ai/vellum-assistant.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/vellum-self-knowledge .github/skills/vellum-self-knowledge && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "vellum-self-knowledge" agent skill from https://github.com/vellum-ai/vellum-assistant/tree/main/skills/vellum-self-knowledge into .github/skills/vellum-self-knowledge/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vellum-self-knowledge", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add vellum-ai/vellum-assistant --skill vellum-self-knowledge -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install vellum-ai/vellum-assistant vellum-self-knowledge --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/vellum-ai/vellum-assistant.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/vellum-self-knowledge .opencode/skills/vellum-self-knowledge && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "vellum-self-knowledge" agent skill from https://github.com/vellum-ai/vellum-assistant/tree/main/skills/vellum-self-knowledge into .opencode/skills/vellum-self-knowledge/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vellum-self-knowledge", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
vellum-self-knowledge- GitHub stars
- 1.4k
- Token cost
- ~3k tokens
- SKILL.md length
- 1,031 words
- Files
- 1
- Skills in repo
- 108
- Repo updated
- First seen
- Licence
- MIT
At a glance
Answer questions about Vellum, its config, billing, and hosting from live sources of truth
- Works in 3 steps: The assistant CLI — Live Runtime State → Vellum Docs Site — Conceptual Knowledge → Source Code — Deep Implementation Details
- SKILL.md covers Critical Rule and Sources of Truth
- Calls git; reaches vellum.ai
What it does
Vellum Self Knowledge is an agent skill from vellum-ai/vellum-assistant. Answer questions about Vellum, its config, billing, and hosting from live sources of truth
Its SKILL.md is about 3k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts. Compatibility notes: Designed for Vellum personal assistants
The repository describes itself as: An AI Assistant that’s easy to setup, does your work 24/7, knows your preferences and gets better over time. The licence is MIT.
Example prompts
- “/vellum-self-knowledge”
Requirements
- Compatibility (from SKILL.md): Designed for Vellum personal assistants
Workflow steps
3 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 33cc983. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
git
From the folder's file list and the shell code blocks in SKILL.md.
Network
Hosts in commands or code, which the agent is likely to contact:
vellum.ai
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Compatibility
Designed for Vellum personal assistants
From compatibility in the SKILL.md frontmatter.
Context cost
Vellum Self Knowledge loads about 3k tokens when it runs. Until then it costs about 28 tokens; SKILL.md has 1,031 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from vellum-ai/vellum-assistant at commit 33cc983, republished under its MIT licence (© vellum-ai). 1,031 words, ~2,984 tokens.
Download SKILL.mdSave it as
.claude/skills/vellum-self-knowledge/SKILL.md (or your agent's skills folder).- name
- vellum-self-knowledge
- description
- Answer questions about Vellum, its config, billing, and hosting from live sources of truth
- compatibility
- Designed for Vellum personal assistants
- metadata.emoji
- 🪞
Critical Rule
Never answer from memory or general knowledge about Vellum. Always go to a source of truth.
Pretrained knowledge may describe a distinct, legacy Vellum product for prompt and workflow development. That product is not this assistant. Never use it to answer questions about this Vellum.
This skill contains zero static information — only pointers to where the truth lives.
Sources of Truth
1. The assistant CLI — Live Runtime State
The 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 |
| Balance, plan credit left/used, extra credit, expiry, daily limit | assistant platform credits --json |
| Plan, subscription status, billing cycle boundary | assistant platform subscription --json |
| Plan catalog and pricing | assistant platform plans --json |
| Invoices | assistant platform invoices list --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
authorized it, assistant means a bot people reach the assistant through.
Report the sense found rather than a bare yes.
Do not infer the sense from the provider key. slack and discord name the
user integration while their bots are slack_channel and discord_channel,
yet telegram is itself the bot. Some services offer both from one authorize
URL, so having done one is not evidence of the other, and people often cannot
recall which they did.
channels list reports delivery health for channels that have a readiness
probe, which is not all of them. It answers whether a channel is working, not
whether something is connected.
Credit balance, plan credit, and today's spend come from the platform's
billing ledger through platform credits and platform subscription, never
from an estimate. "How much of my allowance is left" is the plan-credit
reading, the same one the in-app usage meter shows: plan_credit_remaining
of plan_credit_total, with plan_credit_used_fraction as the percentage.
When plan_credits_spent is true, further managed usage draws on
extra_credit_remaining only if that is above zero; at zero the organization
is out of credit. Plan credit mixes grants with different lifetimes
(only the Pro bundle turns over with the billing cycle), so it has no single
reset date: give next_credit_expiry_at and credits_expiring_soon for what
expires next (across all grants, not only plan credit), and currentPeriodEnd
from platform subscription only as the billing cycle boundary. When the grant fields are null, say the platform
reports no plan-credit figures rather than deriving them. The only spend
figure platform credits reports is daily_spend: today's (UTC)
spend counted against the daily credit limit, which excludes spend covered by
plan-included credits. Present it as exactly that. For total spend today, or
spend over any other period, say that you cannot see it and point to
Settings > Billing; do not substitute daily_spend or usage totals, which is
a local token-cost estimate, not the ledger. When platform credits fails or
the assistant is not connected to the platform, say plainly that you cannot
see the balance and point to Settings > Billing. Do not guess a number, an
allowance model, or a reset schedule, and never imply you checked when you did
not.
Show full SKILL.md (351 more words)Show less
2. Vellum Docs Site — Conceptual Knowledge
For "what is", "how does", and "why" questions, fetch the relevant page from the docs site.
Base URL: https://www.vellum.ai/docs
| Topic | Path |
|---|---|
| What is Vellum | /getting-started/what-is-vellum |
| Installation | /getting-started/installation |
| Quick start | /getting-started/quick-start |
| Your first skill | /getting-started/your-first-skill |
| How it all fits together | /key-concepts/how-it-all-fits-together |
| The workspace | /key-concepts/the-workspace |
| Skills & tools | /key-concepts/skills-and-tools |
| Memory & context | /key-concepts/memory-and-context |
| Channels | /key-concepts/channels |
| Identity | /key-concepts/identity |
| Scheduling | /key-concepts/scheduling |
| Glossary | /key-concepts/glossary |
| Privacy & data | /trust-security/privacy-and-data |
| The permissions model | /trust-security/the-permissions-model |
| Security best practices | /trust-security/security-best-practices |
| Architecture | /developer-guide/architecture |
| Security (developer) | /developer-guide/security |
| Features & capabilities | /developer-guide/features |
| API & communication | /developer-guide/api |
| Development workflow | /developer-guide/development-workflow |
| Contributing | /developer-guide/contributing |
| Local hosting | /hosting-options/local-hosting |
| Advanced hosting | /hosting-options/advanced-options |
| Environments | /environments |
| Pricing | /pricing |
| Roadmap | /roadmap |
| FAQ | /help/faq |
| Common issues | /help/common-issues |
| Getting help | /help/getting-help |
| Skills reference index | /skills-reference |
| Specific skill reference | /skills-reference/<skill-name> |
Install, platform, and "how do I install you" questions belong on Installation and FAQ, not memory. Pricing and "is it free" belong on Pricing, then the assistant platform credits|subscription|plans commands for this assistant's live plan.
Use web_fetch to pull the page content. If a URL 404s, try fetching the docs homepage and navigating from the sidebar.
3. Source Code — Deep Implementation Details
For questions the docs and CLI can't answer (internal architecture, how a specific feature is implemented, source-level details):
- Get the current version:
assistant --version - The open source repo is at
https://github.com/vellum-ai/vellum-assistant - The release for version X is at
https://github.com/vellum-ai/vellum-assistant/releases/tag/vX.Y.Z - Check out the matching tag locally:
cd /workspace/vellum-assistant && git fetch --tags && git checkout v<version> - Key source locations:
assistant/— Runtime (conversation loop, tool dispatch, memory, scheduling)gateway/— Ingress boundary (webhooks, Telegram, Twilio, reverse proxy)clients/- End-user surfaces (web SPA, iOS, Android, macOS, Windows, Linux, Chrome extension)skills/— Bundled skill definitionsARCHITECTURE.md— Cross-system indexassistant/ARCHITECTURE.md— Runtime internalsgateway/ARCHITECTURE.md— Gateway internalsassistant/docs/architecture/— Detailed architecture docs (security, memory, etc.)
- Read the relevant source files to answer the question.
Resolution Order
- CLI first — if the question is about current state, config, or capabilities, the CLI has it.
- Docs second — if the question is conceptual ("what is X", "how does Y work"), fetch the docs page.
- Source code last — only for deep implementation questions that the docs don't cover.
© vellum-ai, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in skills/vellum-self-knowledge of vellum-ai/vellum-assistant.
Open the folder on GitHubat commit 33cc983
Compare with similar skills
Vellum Self Knowledge next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Vellum Self Knowledge this skillvellum-ai/vellum-assistant | 1.4k | — | ~3k | Automated safety check: Pass | MIT | |
| Billing Automationwshobson/agents | 40k | 13 repos | ~473 | Automated safety check: Pass | MIT | |
| Customer Billing Opsaffaan-m/ECC | 276k | 2 repos | ~1.1k | Automated safety check: Pass | MIT | |
| Finance Billing Opsaffaan-m/ECC | 276k | 1 repos | ~958 | Automated safety check: Pass | MIT | |
| cmux Billing Runbookmanaflow-ai/cmux | 28k | — | ~2.8k | Automated safety check: Pass | Custom licence | |
| Invoices Billingsickn33/agentic-awesome-skills | 47k | 1 repos | ~4.4k | Automated safety check: Pass | MIT |
Similar skills
Customer Billing Ops
affaan-m/ECC
Operate customer billing workflows such as subscriptions, refunds, churn triage, billing-portal recovery, and plan analysis using connected billing tools like Stripe.
Finance Billing Ops
affaan-m/ECC
Evidence-first revenue, pricing, refunds, team-billing, and billing-model truth workflow for ECC.
cmux Billing Runbook
manaflow-ai/cmux
Runbook for the cmux billing code: Stripe Checkout, customer portal, subscription changes, webhooks and how Pro plan entitlement is resolved from Stack metadata.
Invoices Billing
sickn33/agentic-awesome-skills
Invoice and billing register: invoice number, client, project, issue and due dates, subtotal, discount, tax and withholding, total, payments, balance and aging.
Add Hosted Key
simstudioai/sim
Add hosted API key support to a tool so Sim provides the key (metered and billed to the workspace) when a user has not brought their own.
More from vellum-ai/vellum-assistant
All 108 skills in this repoVellum GitHub App Setup
vellum-ai/vellum-assistant
Create and configure a GitHub App so the assistant can push commits, open PRs, and comment under its own bot identity.
Discord App Setup
vellum-ai/vellum-assistant
Connect a Discord bot to the assistant via the Discord Gateway with guided application creation and intent configuration
Sentry App Setup
vellum-ai/vellum-assistant
Create and configure a Sentry internal integration so the assistant can manage issues, alerts, and releases under its own identity
Memory Corpus Ingest
vellum-ai/vellum-assistant
Ingest a large dataset into memory as a skimmed map. An agent skill from vellum-ai/vellum-assistant.
Plugin Builder
vellum-ai/vellum-assistant
A skill your agent uses when the user wants to build, scaffold, ship, or edit a Vellum plugin that bundles multiple surfaces (hooks, tools, skills, and more) into one installable package.
Slack App Setup
vellum-ai/vellum-assistant
Connect a Slack app to the Vellum Assistant via Socket Mode.
Questions about Vellum Self Knowledge
What does Vellum Self Knowledge do?
Answer questions about Vellum, its config, billing, and hosting from live sources of truth. Vellum Self Knowledge is an agent skill from vellum-ai/vellum-assistant.
How do I install Vellum Self Knowledge in Claude Code?
Run `npx skills add vellum-ai/vellum-assistant --skill vellum-self-knowledge -a claude-code`. Or copy the skill folder (skills/vellum-self-knowledge in vellum-ai/vellum-assistant) into .claude/skills/vellum-self-knowledge in your project. Claude Code loads it when a task matches its description.
How do I install Vellum Self Knowledge in Codex?
Run `npx skills add vellum-ai/vellum-assistant --skill vellum-self-knowledge -a codex`. Or copy the skill folder (skills/vellum-self-knowledge in vellum-ai/vellum-assistant) into .agents/skills/vellum-self-knowledge in your project. Codex loads it when a task matches its description.
Can I use Vellum Self Knowledge in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add vellum-ai/vellum-assistant --skill vellum-self-knowledge -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/vellum-self-knowledge, .gemini/skills/vellum-self-knowledge, .github/skills/vellum-self-knowledge and .opencode/skills/vellum-self-knowledge in your project.
What does Vellum Self Knowledge need to run?
Going by SKILL.md and its folder, Vellum Self Knowledge needs the command-line tools its instructions call (git). Compatibility (from SKILL.md): Designed for Vellum personal assistants.
Does Vellum Self Knowledge access the network?
SKILL.md names 1 domain. In commands or code: vellum.ai; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.
Is Vellum Self Knowledge safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Vellum Self Knowledge use?
Vellum Self Knowledge is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Vellum Self Knowledge use?
About 3k tokens (SKILL.md is roughly 12k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Vellum Self Knowledge?
Skills that share tags, products or a category with Vellum Self Knowledge: Billing Automation (wshobson/agents, 40k stars), Customer Billing Ops (affaan-m/ECC, 276k stars), Finance Billing Ops (affaan-m/ECC, 276k stars) and cmux Billing Runbook (manaflow-ai/cmux, 28k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Vellum Self Knowledge?
vellum-ai (a GitHub organization) maintains it in vellum-ai/vellum-assistant, which has 1,408 GitHub stars. The repository holds 108 skills in this directory. The repository was last updated on October 9, 2026.
Source: vellum-ai/vellum-assistant on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.