Agent skill

Source Command Opsx Archive

by zhe-qi in zhe-qi/clhoria-template

Archive a completed change in the experimental workflow. An agent skill from zhe-qi/clhoria-template.

MITAuto-check passed

Install Source Command Opsx Archive

skills CLI
$ npx skills add zhe-qi/clhoria-template --skill source-command-opsx-archive -a claude-code

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

GitHub CLI
$ gh skill install zhe-qi/clhoria-template source-command-opsx-archive --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/zhe-qi/clhoria-template.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/source-command-opsx-archive .claude/skills/source-command-opsx-archive && 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
source-command-opsx-archive
GitHub stars
193
Token cost
~1.3k tokens
SKILL.md length
493 words
Files
1
Skills in repo
10
Repo updated
First seen
Licence
MIT

At a glance

Archive a completed change in the experimental workflow. An agent skill from zhe-qi/clhoria-template.

  • Works in 6 steps: If no change name provided, prompt for… → Check artifact completion status → Check task completion status → …
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Source Command Opsx Archive is an agent skill from zhe-qi/clhoria-template. Archive a completed change in the experimental workflow

Its SKILL.md is about 1.3k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

The repository describes itself as: Production-ready Hono backend template that doubles as an AI agent harness — providing feedforward guides, feedback sensors, and progressive specialization to make AI coding… The licence is MIT.

Example prompts

  • “/source-command-opsx-archive”

Workflow steps

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

  1. If no change name provided, prompt for selection
  2. Check artifact completion status
  3. Check task completion status
  4. Assess delta spec sync state
  5. Perform the archive
  6. Display summary

What it can do on your machine

Read from SKILL.md and the folder at commit 589f13e. 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

    No scripts in the folder and no shell commands in SKILL.md (its code samples are bash).

    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

Source Command Opsx Archive loads about 1.3k tokens when it runs. Until then it costs about 21 tokens; SKILL.md has 493 words of instructions outside code blocks.

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

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 zhe-qi/clhoria-template at commit 589f13e, republished under its MIT licence (© zhe-qi). 493 words, ~1,277 tokens.

Download SKILL.mdSave it as .claude/skills/source-command-opsx-archive/SKILL.md (or your agent's skills folder).
name
source-command-opsx-archive
description
Archive a completed change in the experimental workflow

source-command-opsx-archive

Use this skill when the user asks to run the migrated source command opsx-archive.

Command Template

Archive a completed change in the experimental workflow.

Input: Optionally specify a change name after /opsx:archive (e.g., /opsx:archive add-auth). If omitted, check if it can be inferred from conversation context. If vague or ambiguous you MUST prompt for available changes.

Steps

  1. If no change name provided, prompt for selection

    Run openspec list --json to get available changes. Use the AskUserQuestion tool to let the user select.

    Show only active changes (not already archived). Include the schema used for each change if available.

    IMPORTANT: Do NOT guess or auto-select a change. Always let the user choose.

  2. Check artifact completion status

    Run openspec status --change "<name>" --json to check artifact completion.

    Parse the JSON to understand:

    • schemaName: The workflow being used
    • artifacts: List of artifacts with their status (done or other)

    If any artifacts are not done:

    • Display warning listing incomplete artifacts
    • Prompt user for confirmation to continue
    • Proceed if user confirms
  3. Check task completion status

    Read the tasks file (typically tasks.md) to check for incomplete tasks.

    Count tasks marked with - [ ] (incomplete) vs - [x] (complete).

    If incomplete tasks found:

    • Display warning showing count of incomplete tasks
    • Prompt user for confirmation to continue
    • Proceed if user confirms

    If no tasks file exists: Proceed without task-related warning.

  4. Assess delta spec sync state

    Check for delta specs at openspec/changes/<name>/specs/. If none exist, proceed without sync prompt.

    If delta specs exist:

    • Compare each delta spec with its corresponding main spec at openspec/specs/<capability>/spec.md
    • Determine what changes would be applied (adds, modifications, removals, renames)
    • Show a combined summary before prompting

    Prompt options:

    • If changes needed: "Sync now (recommended)", "Archive without syncing"
    • If already synced: "Archive now", "Sync anyway", "Cancel"

    If user chooses sync, use Task tool (subagent_type: "general-purpose", prompt: "Use Skill tool to invoke openspec-sync-specs for change '<name>'. Delta spec analysis: <include the analyzed delta spec summary>"). Proceed to archive regardless of choice.

  5. Perform the archive

    Create the archive directory if it doesn't exist:

    bash
    mkdir -p openspec/changes/archive

    Generate target name using current date: YYYY-MM-DD-<change-name>

    Check if target already exists:

    • If yes: Fail with error, suggest renaming existing archive or using different date
    • If no: Move the change directory to archive
    bash
    mv openspec/changes/<name> openspec/changes/archive/YYYY-MM-DD-<name>
  6. Display summary

    Show archive completion summary including:

    • Change name
    • Schema that was used
    • Archive location
    • Spec sync status (synced / sync skipped / no delta specs)
    • Note about any warnings (incomplete artifacts/tasks)
Show full SKILL.md (91 more words)Show less

Output On Success

## Archive Complete

**Change:** <change-name>
**Schema:** <schema-name>
**Archived to:** openspec/changes/archive/YYYY-MM-DD-<name>/
**Specs:** ✓ Synced to main specs

All artifacts complete. All tasks complete.

Output On Success (No Delta Specs)

## Archive Complete

**Change:** <change-name>
**Schema:** <schema-name>
**Archived to:** openspec/changes/archive/YYYY-MM-DD-<name>/
**Specs:** No delta specs

All artifacts complete. All tasks complete.

Output On Success With Warnings

## Archive Complete (with warnings)

**Change:** <change-name>
**Schema:** <schema-name>
**Archived to:** openspec/changes/archive/YYYY-MM-DD-<name>/
**Specs:** Sync skipped (user chose to skip)

**Warnings:**
- Archived with 2 incomplete artifacts
- Archived with 3 incomplete tasks
- Delta spec sync was skipped (user chose to skip)

Review the archive if this was not intentional.

Output On Error (Archive Exists)

## Archive Failed

**Change:** <change-name>
**Target:** openspec/changes/archive/YYYY-MM-DD-<name>/

Target archive directory already exists.

**Options:**
1. Rename the existing archive
2. Delete the existing archive if it's a duplicate
3. Wait until a different date to archive

Guardrails

  • Always prompt for change selection if not provided
  • Use artifact graph (openspec status --json) for completion checking
  • Don't block archive on warnings - just inform and confirm
  • Preserve .openspec.yaml when moving to archive (it moves with the directory)
  • Show clear summary of what happened
  • If sync is requested, use the Skill tool to invoke openspec-sync-specs (agent-driven)
  • If delta specs exist, always run the sync assessment and show the combined summary before prompting

© zhe-qi, 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 .agents/skills/source-command-opsx-archive of zhe-qi/clhoria-template.

Open the folder on GitHubat commit 589f13e

Compare with similar skills

Source Command Opsx Archive 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.

Source Command Opsx Archive compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Source Command Opsx Archive this skillzhe-qi/clhoria-template193—~1.3kAutomated safety check: PassMIT
OpenSpec Bulk Change ArchiverFission-AI/OpenSpec71k3 repos~5.6kAutomated safety check: PassMIT
Verification Before Completionforyourhealth111-pixel/Vibe-Skills3.6k—~1.1kAutomated safety check: PassApache-2.0
Verification Before Completionfarm-fe/farm5.6k46 repos~1kAutomated safety check: PassMIT
Experimental Designaiming-lab/AutoResearchClaw15k—~286Automated safety check: PassMIT
Openspec Archive Changetsedio/tsed3.1k6 repos~4.1kAutomated safety check: PassMIT

Similar skills

  • Archives several completed OpenSpec changes in one operation, checking the codebase to resolve spec conflicts rather than archiving blindly.

    71k GitHub starsUsed in 3 repos~5.6k tokens
    DevelopmentAuto-check passed
  • Verification Before Completion

    foryourhealth111-pixel/Vibe-Skills

    Completion-evidence route used before claiming work is complete, fixed, passing, committed, or PR-ready.

    3.6k GitHub stars~1.1k tokensUpdated 1 mo ago
    Agent WorkflowsAuto-check passed
  • A skill your agent uses when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any…

    5.6k GitHub starsUsed in 46 repos~1k tokens
    Agent WorkflowsAuto-check passed
  • Experimental Design

    aiming-lab/AutoResearchClaw

    Best practices for designing reproducible ML experiments. An agent skill from aiming-lab/AutoResearchClaw.

    15k GitHub stars~286 tokensUpdated 1 mo ago
    Research & ScienceAuto-check passed
  • Archive a completed OpenSpec change in the experimental workflow.

    3.1k GitHub starsUsed in 6 repos~4.1k tokens
    Auto-check passed
  • Verification Before Completion

    jnMetaCode/superpowers-zh

    Chinese-language rule that bars an agent from claiming work is done, fixed or passing until it has run a verification command and read the output.

    8.3k GitHub stars~443 tokensUpdated 4 days ago
    Agent WorkflowsAuto-check passed

More from zhe-qi/clhoria-template

All 10 skills in this repo
  • Effect V4

    zhe-qi/clhoria-template

    Effect v4 模式指南。当需要创建 Effect 服务、定义错误类型、编写 Effect 程序、管理 Layer 组合、或使用 Effect 封装异步操作时使用

    193 GitHub stars~887 tokensUpdated 2 mo ago
    Auto-check passed
  • Bullmq

    zhe-qi/clhoria-template

    创建或修改 BullMQ 队列任务。当需要创建新队列、添加任务类型、注册 Worker、设置定时任务、或用户请求"添加后台任务/队列处理"时使用

    193 GitHub stars~1.6k tokensUpdated 2 mo ago
    Auto-check passed
  • Create Tier

    zhe-qi/clhoria-template

    创建或修改一个新的 API tier。当用户请求“新增 tier / 创建 partner tier / 新增 merchant 端 / 新增 tenant 端 / 新增 API 端 / 新增一套路由层”时使用。目标是在不修改框架核心的前提下,为新 tier 补齐配置、中间件、类型别名、路由入口和测试。

    193 GitHub stars~1.7k tokensUpdated 2 mo ago
    Auto-check: notes
  • Crud

    zhe-qi/clhoria-template

    创建或修改 CRUD 模块。当需要创建新的增删改查 API、修改现有路由模块、添加新字段、新增接口、或用户请求"创建/修改 XX 管理"时使用

    193 GitHub stars~552 tokensUpdated 2 mo ago
    Auto-check passed
  • DB Schema

    zhe-qi/clhoria-template

    创建或修改数据库 Schema。当需要创建新表、修改表结构、定义字段、设置索引约束、或涉及 Drizzle ORM / drizzle-zod 操作时使用

    193 GitHub stars~620 tokensUpdated 2 mo ago
    Auto-check passed
  • Drizzle V1

    zhe-qi/clhoria-template

    Drizzle ORM v1 关系查询指南。当需要定义 Relations v2、编写关系查询、使用 through 多对多、预定义过滤器、或从旧版 Drizzle 迁移时使用

    193 GitHub stars~3k tokensUpdated 2 mo ago
    Auto-check passed

Questions about Source Command Opsx Archive

What does Source Command Opsx Archive do?

Archive a completed change in the experimental workflow. An agent skill from zhe-qi/clhoria-template. Source Command Opsx Archive is an agent skill from zhe-qi/clhoria-template.

How do I install Source Command Opsx Archive in Claude Code?

Run `npx skills add zhe-qi/clhoria-template --skill source-command-opsx-archive -a claude-code`. Or copy the skill folder (.agents/skills/source-command-opsx-archive in zhe-qi/clhoria-template) into .claude/skills/source-command-opsx-archive in your project. Claude Code loads it when a task matches its description.

How do I install Source Command Opsx Archive in Codex?

Run `npx skills add zhe-qi/clhoria-template --skill source-command-opsx-archive -a codex`. Or copy the skill folder (.agents/skills/source-command-opsx-archive in zhe-qi/clhoria-template) into .agents/skills/source-command-opsx-archive in your project. Codex loads it when a task matches its description.

Can I use Source Command Opsx Archive 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 zhe-qi/clhoria-template --skill source-command-opsx-archive -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/source-command-opsx-archive, .gemini/skills/source-command-opsx-archive, .github/skills/source-command-opsx-archive and .opencode/skills/source-command-opsx-archive in your project.

What does Source Command Opsx Archive need to run?

SKILL.md names no scripts, command-line tools or credentials: Source Command Opsx Archive is instructions for the agent only.

Does Source Command Opsx Archive 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 Source Command Opsx Archive 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 Source Command Opsx Archive use?

Source Command Opsx Archive 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 Source Command Opsx Archive use?

About 1.3k tokens (SKILL.md is roughly 5.1k 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 Source Command Opsx Archive?

Skills that share tags, products or a category with Source Command Opsx Archive: OpenSpec Bulk Change Archiver (Fission-AI/OpenSpec, 71k stars), Verification Before Completion (foryourhealth111-pixel/Vibe-Skills, 3.6k stars), Verification Before Completion (farm-fe/farm, 5.6k stars) and Experimental Design (aiming-lab/AutoResearchClaw, 15k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Source Command Opsx Archive?

zhe-qi (a GitHub user) maintains it in zhe-qi/clhoria-template, which has 193 GitHub stars. The repository holds 10 skills in this directory. The repository was last updated on July 30, 2026.

Source: zhe-qi/clhoria-template on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.