OPS on-demand: This skill should be used when the user asks to "vip list", "who is a VIP", "add someone…

MITAuto-check: notes

Install Vip

skills CLI
$ npx skills add Lifecycle-Innovations-Limited/claude-ops --skill vip -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install Lifecycle-Innovations-Limited/claude-ops vip --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/Lifecycle-Innovations-Limited/claude-ops.git skills-src && mkdir -p .claude/skills && cp -r skills-src/claude-ops/skills/vip .claude/skills/vip && rm -rf skills-src

Use ~/.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/

Facts

Skill name
vip
GitHub stars
542
Token cost
~1.9k tokens
SKILL.md length
702 words
Files
2
Skills in repo
67
Repo updated
First seen
Licence
MIT

At a glance

OPS on-demand: This skill should be used when the user asks to "vip list", "who is a VIP", "add someone…

  • Works in 4 steps: Enforce the list — VIP senders rank… → Require FULL context before answering or… → Order triage output by tier. → …
  • Asks to vip list
  • SKILL.md covers Scope (deliberately narrow), Configuration, Tiers and Operations, plus 3 more sections
  • Calls python3

What it does

Vip is an agent skill from Lifecycle-Innovations-Limited/claude-ops. OPS on-demand: This skill should be used when the user asks to "vip list", "who is a VIP", "add someone…

Its SKILL.md is about 1.9k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files (for example `templates/vip-list.example.json`).

The repository describes itself as: Business operating system for Claude Code — 57 skills, 21 agents, smart daemon. Unified inbox (WhatsApp/Email/Slack/Telegram), autonomous PR merge, full-AWS monitoring, revenue… The licence is MIT.

When your agent uses it

  • Asks to vip list

Example prompts

  • “vip list”
  • “who is a VIP”
  • “/vip”

Requirements

  • Python 3
  • Pre-approved tools (allowed-tools): Bash, Read, Grep, Skill, AskUserQuestion

Workflow steps

4 steps, taken from the first numbered list in SKILL.md.

  1. Enforce the list — VIP senders rank ahead of everything else in every sweep.
  2. Require FULL context before answering or drafting for a VIP: the whole
  3. Order triage output by tier.
  4. Suggest additions when the signals below appear.

What it can do on your machine

Read from SKILL.md and the folder at commit 1aa0928. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Bash
    • Read
    • Grep
    • Skill
    • AskUserQuestion

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • python3

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    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.

Context cost

Vip loads about 1.9k tokens when it runs. Until then it costs about 27 tokens; SKILL.md has 702 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~27
When it runs · the whole SKILL.md, loaded when a task matches
~1.9k

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: notes

The automated check noted patterns worth knowing about, such as sudo or a known installer.

  • NotePre-approves every shell command (allowed-tools: Bash)SKILL.md
    allowed-tools: Bash, Read, Grep, Skill, AskUserQuestion

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 Lifecycle-Innovations-Limited/claude-ops at commit 1aa0928, republished under its MIT licence (© Lifecycle-Innovations-Limited). 702 words, ~1,870 tokens.

Download SKILL.mdSave it as .claude/skills/vip/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
vip
description
OPS on-demand: This skill should be used when the user asks to "vip list", "who is a VIP", "add someone…
allowed-tools
Bash, Read, Grep, Skill, AskUserQuestion
argument-hint
[list|show <person>|set <person> --tier N|suggest|why <person>]

/ops:vip — VIP List

Load ops-rules before acting. Public repo (no personal data). Outbound: one draft → one approval → one send. If AskUserQuestion / Workflow are missing, follow Rule 10 in ops-rules (Hermes: numbered options / two-turn Telegram card; delegate_task).

The priority layer over every inbox. VIPs are checked FIRST in any sweep, answered first, drafted with extra care, and never buried in a bulk digest.

Scope (deliberately narrow)

This skill does four things and nothing else:

  1. Enforce the list — VIP senders rank ahead of everything else in every sweep.
  2. Require FULL context before answering or drafting for a VIP: the whole thread, every account on that channel, both directions, plus the ledger brief.
  3. Order triage output by tier.
  4. Suggest additions when the signals below appear.

It does not read histories for their own sake, does not draft unasked, and does not open a second channel just because one record is open. A tier edit is metadata only. Tagging someone is never an instruction to sweep their history.

Configuration

Nothing here is machine-specific. Every value resolves from userConfig, an env var, or $HOME.

userConfig keyEnv overrideDefaultMeaning
vip_list_pathVIP_LIST_PATH$HOME/.claude-ops/state/vip-list.jsonTier data + why/register notes
vip_max_tierVIP_MAX_TIER2Highest tier treated as VIP
vip_suggest_enabled—trueEmit VIP candidate suggestions
vip_volume_days—30Window for the volume signal
vip_volume_min—12Two-way messages that trip volume
relations_cliRELATIONS_CLI$HOME/.claude-ops/relations/bin/relations-cliShared ledger CLI (see relations)
bash
PREFS_PATH="${PREFS_PATH:-${CLAUDE_PLUGIN_DATA_DIR:-$HOME/.claude/plugins/data/ops-ops-marketplace}/preferences.json}"
read_pref() { [ -f "$PREFS_PATH" ] && python3 -c 'import json,sys;print(json.load(open(sys.argv[1])).get(sys.argv[2],"") or "")' "$PREFS_PATH" "$1" 2>/dev/null; }

VIP_LIST_PATH="${VIP_LIST_PATH:-$(read_pref vip_list_path)}"
VIP_LIST_PATH="${VIP_LIST_PATH:-$HOME/.claude-ops/state/vip-list.json}"
VIP_MAX_TIER="${VIP_MAX_TIER:-$(read_pref vip_max_tier)}"
VIP_MAX_TIER="${VIP_MAX_TIER:-2}"

# "No VIPs" and "the VIP list was never set up" are DIFFERENT answers and must
# never look the same. An unconfigured install that silently reports an empty
# list turns this skill into a no-op: every inbox sweep then treats the most
# important people as ordinary traffic and nobody finds out. Fail loud.
if [ ! -f "$VIP_LIST_PATH" ]; then
  echo "vip: no list at $VIP_LIST_PATH — set userConfig vip_list_path or VIP_LIST_PATH." >&2
  echo "vip: copy templates/vip-list.example.json there to start one." >&2
  exit 3
fi

The list file lives OUTSIDE the repo tree — it is the operator's identity and must never be committed (ops-rules Rule 0). Shape: templates/vip-list.example.json.

Tiers

TierMeaningHandling
1Inner circleNever let it sit. Checked first, answered first, never batched
2Key businessSame day. Ranked above general triage
3-5ReservedNot VIP by default (vip_max_tier = 2)

The ledger's importance_tier column is the source of truth for the tier value; the JSON file carries the why and the register notes (language, tone, dates to avoid). Both are read; the DB wins on conflict.

Operations

SubcommandWhat it does
list (default)Every person at or above vip_max_tier, grouped by tier
show <person>Tier, type, why, channel, register notes
set <person> --tier NAudited tier write via the ledger CLI, reason required
suggestRead-only candidate scan (see signals below); never writes
why <person>Which signal put a suggested candidate on the list
bash
"$RELATIONS_CLI" vip-list --max-tier "$VIP_MAX_TIER"
"$RELATIONS_CLI" vip <person_id> --tier 1 --type personal --reason "<why>"

Tier writes go through the CLI, never raw SQL. The CLI owns source_reference, the audit log, and the rollback path. A direct UPDATE on the ledger DB — inline or wrapped in a script — leaves an unauditable row and is forbidden even where no guard happens to fire.

Show full SKILL.md (273 more words)Show less

Sweep order

Any inbox, chat, email, or ticket sweep runs in this order:

  1. Resolve the VIP set once (vip list), cache it for the sweep.
  2. Tier 1 senders, every channel, both directions, every account.
  3. Tier 2 senders, same.
  4. Everything else, normal triage.

A VIP with an unanswered inbound is always surfaced individually, with the thread context, never as a line in a digest.

Suggesting additions

Suggest, never add silently. A tier change needs the owner's word, then the audited CLI write. Three signals:

SignalTrigger
volumevip_volume_min+ two-way messages in vip_volume_days with someone off the list
frustrationThey say they are being ignored or chased ("still waiting", "any update")
chain-breakTheir last message is inbound and still unanswered

Two filters keep this honest, both learned from real false positives:

  • Anchor every keyword on both sides. A bare stem matches inside longer words (ping inside "tapping") and produces phantom frustration hits.
  • A thread ending on a sign-off is CLOSED, not broken. "Thanks!", "sounds good", an emoji, or any short ack with no question mark is not an open ask. Without this filter most chain-breaks are noise that buries the real ones.

Present at most 5 a week: who, which signal, the evidence line, and the exact CLI command to apply it. Then ask plainly. On "no", do not raise that person again.

  • relations — the ledger, decision queue and draft path this list ranks
  • ops-inbox — the sweep that consumes the tier order
  • ops-comms — the send path, still gated by Rule 6 for every VIP
  • people — contact directory / identity resolution
  • ops-rules — Rule 0 (the list is operator data, never committed)

© Lifecycle-Innovations-Limited, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file in claude-ops/skills/vip of Lifecycle-Innovations-Limited/claude-ops.

  • SKILL.md
  • templates/vip-list.example.json

Open the folder on GitHubat commit 1aa0928

Compare with similar skills

Vip 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.

Vip compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Vip this skillLifecycle-Innovations-Limited/claude-ops542—~1.9kAutomated safety check: NotesMIT
Knowledge Opsaffaan-m/ECC276k2 repos~1.7kAutomated safety check: PassMIT
Research Opsaffaan-m/ECC276k2 repos~902Automated safety check: PassMIT
Terminal Opsaffaan-m/ECC276k2 repos~750Automated safety check: PassMIT
Messages Opsaffaan-m/ECC276k1 repos~724Automated safety check: PassMIT
Email Opsaffaan-m/ECC276k1 repos~1.1kAutomated safety check: PassMIT

Similar skills

  • Knowledge Ops

    affaan-m/ECC

    Knowledge base management, ingestion, sync, and retrieval across multiple storage layers (local files, MCP memory, vector stores, Git repos).

    276k GitHub starsUsed in 2 repos~1.7k tokens
    Knowledge ManagementAuto-check passed
  • Research Ops

    affaan-m/ECC

    Evidence-first current-state research workflow for ECC. An agent skill from affaan-m/ECC.

    276k GitHub starsUsed in 2 repos~902 tokens
    Research & ScienceAuto-check passed
  • Terminal Ops

    affaan-m/ECC

    Evidence-first repo execution workflow for ECC. An agent skill from affaan-m/ECC.

    276k GitHub starsUsed in 2 repos~750 tokens
    Testing & QAAuto-check passed
  • Messages Ops

    affaan-m/ECC

    Evidence-first live messaging workflow for ECC. An agent skill from affaan-m/ECC.

    276k GitHub starsUsed in 1 repo~724 tokens
    Productivity & AutomationAuto-check passed
  • Email Ops

    affaan-m/ECC

    Evidence-first mailbox triage, drafting, send verification, and sent-mail-safe follow-up workflow for ECC.

    276k GitHub starsUsed in 1 repo~1.1k tokens
    Writing & ContentAuto-check passed
  • GitHub Ops

    affaan-m/ECC

    GitHub repository operations, automation, and management. An agent skill from affaan-m/ECC.

    276k GitHub starsUsed in 2 repos~1.5k tokens
    DevelopmentAuto-check: warnings

More from Lifecycle-Innovations-Limited/claude-ops

All 67 skills in this repo
  • Ops Dash

    Lifecycle-Innovations-Limited/claude-ops

    OPS on-demand: This skill should be used when the user asks to "ops dashboard", "pixel HQ", or…

    542 GitHub stars~4.7k tokensUpdated today
    Auto-check: notes
  • Ops Gtm

    Lifecycle-Innovations-Limited/claude-ops

    OPS on-demand: This skill should be used when the user asks to "go to market", "GTM plan", or…

    542 GitHub stars~3.7k tokensUpdated today
    Auto-check: notes
  • Ops Marketing

    Lifecycle-Innovations-Limited/claude-ops

    OPS on-demand: This skill should be used when the user asks to "klaviyo", "ads spend", or…

    542 GitHub stars~3.5k tokensUpdated today
    Auto-check: notes
  • Ops Socials

    Lifecycle-Innovations-Limited/claude-ops

    OPS on-demand: This skill should be used when the user asks to "tweet", "post to linkedin", or…

    542 GitHub stars~3.6k tokensUpdated today
    Auto-check: notes
  • Ops Yolo

    Lifecycle-Innovations-Limited/claude-ops

    OPS on-demand: This skill should be used when the user asks to "yolo mode", "run the business today"…

    542 GitHub stars~4k tokensUpdated today
    Auto-check: notes
  • Ops Monitor

    Lifecycle-Innovations-Limited/claude-ops

    OPS on-demand: This skill should be used when the user asks to "datadog", "APM alerts", or…

    542 GitHub starsUsed in 1 repo~1.5k tokens
    Auto-check: notes

Questions about Vip

What does Vip do?

OPS on-demand: This skill should be used when the user asks to "vip list", "who is a VIP", "add someone…. Vip is an agent skill from Lifecycle-Innovations-Limited/claude-ops.

When should I use Vip?

Vip fits situations like: asks to vip list.

How do I install Vip in Claude Code?

Run `npx skills add Lifecycle-Innovations-Limited/claude-ops --skill vip -a claude-code`. Or copy the skill folder (claude-ops/skills/vip in Lifecycle-Innovations-Limited/claude-ops) into .claude/skills/vip in your project. Claude Code loads it when a task matches its description.

How do I install Vip in Codex?

Run `npx skills add Lifecycle-Innovations-Limited/claude-ops --skill vip -a codex`. Or copy the skill folder (claude-ops/skills/vip in Lifecycle-Innovations-Limited/claude-ops) into .agents/skills/vip in your project. Codex loads it when a task matches its description.

Can I use Vip 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 Lifecycle-Innovations-Limited/claude-ops --skill vip -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/vip, .gemini/skills/vip, .github/skills/vip and .opencode/skills/vip in your project.

What does Vip need to run?

Going by SKILL.md and its folder, Vip needs the command-line tools its instructions call (python3). Our summary lists: Python 3. Its frontmatter pre-approves these tools: Bash, Read, Grep, Skill, AskUserQuestion.

Does Vip access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Vip safe to install?

Our automated static check of SKILL.md found notes only (pre-approves every shell command (allowed-tools: bash)), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.

What licence does Vip use?

Vip 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 Vip use?

About 1.9k tokens (SKILL.md is roughly 7.5k 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 Vip?

Skills that share tags, products or a category with Vip: Knowledge Ops (affaan-m/ECC, 276k stars), Research Ops (affaan-m/ECC, 276k stars), Terminal Ops (affaan-m/ECC, 276k stars) and Messages Ops (affaan-m/ECC, 276k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Vip?

Lifecycle-Innovations-Limited (a GitHub organization) maintains it in Lifecycle-Innovations-Limited/claude-ops, which has 542 GitHub stars. The repository holds 67 skills in this directory. The repository was last updated on October 9, 2026.

Source: Lifecycle-Innovations-Limited/claude-ops on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.