What is orq-manage-skills?

A command for managing Skills in orq.ai, where Skills are reusable instructions or prompt-based capabilities. It can list, inspect, create, update, retire, or delete them.

Auditing Skills, viewing or editing their details, creating new ones, marking them as retired, deleting them, and finding references.

It puts common Skill management tasks in one command and helps find prompts or agents that reference a Skill before deletion.

orq-manage-skills — Command for Claude Code by orq-ai

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Clone the repo

git clone --depth 1 https://github.com/orq-ai/assistant-plugins

Made for: Claude Code.

Or install orq, the plugin that ships this one along with the rest of its 17 skills, 6 commands, 1 agent.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/commands/orq-ai/assistant-plugins/orq-manage-skills/github.svg)](https://agentmods.dev/commands/orq-ai/assistant-plugins/orq-manage-skills)

Your own site

<a href="https://agentmods.dev/commands/orq-ai/assistant-plugins/orq-manage-skills"><img src="https://agentmods.dev/badge/commands/orq-ai/assistant-plugins/orq-manage-skills/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/commands/orq-ai/assistant-plugins/orq-manage-skills"><img src="https://agentmods.dev/badge/commands/orq-ai/assistant-plugins/orq-manage-skills.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 809 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00000	$0.00809
Opus 5	$0.00000	$0.00404
Sonnet 5	$0.00000	$0.00162
Haiku 4.5	$0.00000	$0.00081

Measured 11d ago against content hash 4e54a3297640, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

orq-manage-skills scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 11d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

commands/orq-manage-skills.md · 46 lines

How it starts

The opening of the file, as written. The whole thing — 46 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Manage Skills

Quick entry point into the orq-manage-skills skill. Routes to the right phase based on the first argument, or asks if no argument is given.

Instructions

1. Parse arguments

$ARGUMENTS may contain an action and optionally a Skill display_name or skill_id:

list — Phase 1 (list / audit)
get <name-or-id> — Phase 2 (inspect a Skill)
create — Phase 3 (create a new Skill)
update <name-or-id> — Phase 4 (edit display_name, description, tags, instructions, project_id, path)
retire <name-or-id> — Phase 4 shortcut: tag with retired (soft-retire — reversible, no enabled field exists)
delete <name-or-id> — Phase 5 (reference scan + delete)

If $ARGUMENTS is empty, ask the user which action they want via AskUserQuestion and offer the six choices above.

If $ARGUMENTS contains an action that requires a name/id but none was provided (e.g., get, update, retire, delete), call list_skills first and ask the user to pick.

2. Delegate to `orq-manage-skills`

Read skills/orq-manage-skills/SKILL.md and execute the matching phase. Pass the parsed name/id along.

3. Safety rails

Never auto-execute delete_skill from this command — always route through Phase 5's reference-scan + warn-then-confirm flow.
Always offer tagging with retired (soft-retire via update_skill) as the default first step when the reference scan finds consumers. There is no enabled field on a Skill.
Always confirm project scope before create_skill.
Always warn before sending a display_name rename — it silently breaks every {{skill.<old-name>}} and {{snippet.<old-name>}} reference.

4. Error handling

Auth errors — "Authentication failed. Check that your ORQ_API_KEY is valid."
AlreadyExists on create — surface the conflicting Skill (paginate list_skills, find by display_name) and offer either a renamed create or update_skill against the existing one.
Skill-tool unavailable — "The orq MCP server doesn't expose *_skill tools in this workspace. Falling back to REST /v2/skills — confirm before proceeding."
MCP unreachable — "Could not reach the orq.ai MCP server. Make sure it's configured: claude mcp add --transport http orq-workspace https://my.orq.ai/v2/mcp --header 'Authorization: Bearer ${ORQ_API_KEY}'"

Read the full file on GitHub · 46 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

11d ago First seen · 46 lines · 0 tokens per session scan A 4e54a3297640

Subscribe to this mod's changes

orq-manage-skills is a command published in the GitHub repository orq-ai/assistant-plugins (6 stars, last pushed 9d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 809 tokens. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Building agents

orq-manage-skills

Getting it into your agent

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

Manage Skills

Instructions

1. Parse arguments

2. Delegate to `orq-manage-skills`

3. Safety rails

4. Error handling

What this file has done since we first saw it

Other commands, from other repositories

checklist

clarify

specify

analyze

converge

implement

orq-manage-skills

Getting it into your agent

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

Manage Skills

Instructions

1. Parse arguments

2. Delegate to orq-manage-skills

3. Safety rails

4. Error handling

What this file has done since we first saw it

Other commands, from other repositories

checklist

clarify

specify

analyze

converge

implement

2. Delegate to `orq-manage-skills`