New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Source Command Opsx Propose

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

Propose a new change - create it and generate all artifacts in one step

MITAuto-check passed

Install Source Command Opsx Propose

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

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

GitHub CLI
$ gh skill install zhe-qi/clhoria-template source-command-opsx-propose --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-propose .claude/skills/source-command-opsx-propose && 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-propose
GitHub stars
193
Token cost
~1.1k tokens
SKILL.md length
556 words
Files
1
Skills in repo
10
Repo updated
First seen
Licence
MIT

At a glance

Propose a new change - create it and generate all artifacts in one step

  • Works in 5 steps: If no input provided, ask what they want… → Create the change directory → Get the artifact build order → …
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Source Command Opsx Propose is an agent skill from zhe-qi/clhoria-template. Propose a new change - create it and generate all artifacts in one step

Its SKILL.md is about 1.1k 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-propose”

Workflow steps

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

  1. If no input provided, ask what they want to build
  2. Create the change directory
  3. Get the artifact build order
  4. Create artifacts in sequence until apply-ready
  5. Show final status

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 Propose loads about 1.1k tokens when it runs. Until then it costs about 25 tokens; SKILL.md has 556 words of instructions outside code blocks.

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

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). 556 words, ~1,128 tokens.

Download SKILL.mdSave it as .claude/skills/source-command-opsx-propose/SKILL.md (or your agent's skills folder).
name
source-command-opsx-propose
description
Propose a new change - create it and generate all artifacts in one step

source-command-opsx-propose

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

Command Template

Propose a new change - create the change and generate all artifacts in one step.

I'll create a change with artifacts:

  • proposal.md (what & why)
  • design.md (how)
  • tasks.md (implementation steps)

When ready to implement, run /opsx:apply

Input: The argument after /opsx:propose is the change name (kebab-case), OR a description of what the user wants to build.

Steps

  1. If no input provided, ask what they want to build

    Use the AskUserQuestion tool (open-ended, no preset options) to ask:

    "What change do you want to work on? Describe what you want to build or fix."

    From their description, derive a kebab-case name (e.g., "add user authentication" → add-user-auth).

    IMPORTANT: Do NOT proceed without understanding what the user wants to build.

  2. Create the change directory

    bash
    openspec new change "<name>"

    This creates a scaffolded change at openspec/changes/<name>/ with .openspec.yaml.

  3. Get the artifact build order

    bash
    openspec status --change "<name>" --json

    Parse the JSON to get:

    • applyRequires: array of artifact IDs needed before implementation (e.g., ["tasks"])
    • artifacts: list of all artifacts with their status and dependencies

  4. Create artifacts in sequence until apply-ready

    Use the TodoWrite tool to track progress through the artifacts.

    Loop through artifacts in dependency order (artifacts with no pending dependencies first):

    a. For each artifact that is ready (dependencies satisfied):

    • Get instructions:
      bash
      openspec instructions <artifact-id> --change "<name>" --json
    • The instructions JSON includes:
      • context: Project background (constraints for you - do NOT include in output)
      • rules: Artifact-specific rules (constraints for you - do NOT include in output)
      • template: The structure to use for your output file
      • instruction: Schema-specific guidance for this artifact type
      • outputPath: Where to write the artifact
      • dependencies: Completed artifacts to read for context
    • Read any completed dependency files for context
    • Create the artifact file using template as the structure
    • Apply context and rules as constraints - but do NOT copy them into the file
    • Show brief progress: "Created <artifact-id>"

    b. Continue until all applyRequires artifacts are complete

    • After creating each artifact, re-run openspec status --change "<name>" --json
    • Check if every artifact ID in applyRequires has status: "done" in the artifacts array
    • Stop when all applyRequires artifacts are done

    c. If an artifact requires user input (unclear context):

    • Use AskUserQuestion tool to clarify
    • Then continue with creation

  5. Show final status

    bash
    openspec status --change "<name>"
Show full SKILL.md (180 more words)Show less

Output

After completing all artifacts, summarize:

  • Change name and location
  • List of artifacts created with brief descriptions
  • What's ready: "All artifacts created! Ready for implementation."
  • Prompt: "Run /opsx:apply to start implementing."

Artifact Creation Guidelines

  • Follow the instruction field from openspec instructions for each artifact type
  • The schema defines what each artifact should contain - follow it
  • Read dependency artifacts for context before creating new ones
  • Use template as the structure for your output file - fill in its sections
  • IMPORTANT: context and rules are constraints for YOU, not content for the file
    • Do NOT copy <context>, <rules>, <project_context> blocks into the artifact
    • These guide what you write, but should never appear in the output

Guardrails

  • Create ALL artifacts needed for implementation (as defined by schema's apply.requires)
  • Always read dependency artifacts before creating a new one
  • If context is critically unclear, ask the user - but prefer making reasonable decisions to keep momentum
  • If a change with that name already exists, ask if user wants to continue it or create a new one
  • Verify each artifact file exists after writing before proceeding to next

© 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-propose of zhe-qi/clhoria-template.

Open the folder on GitHubat commit 589f13e

Compare with similar skills

Source Command Opsx Propose 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 Propose compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Source Command Opsx Propose this skillzhe-qi/clhoria-template193—~1.1kAutomated safety check: PassMIT
Geo Proposalsickn33/agentic-awesome-skills47k1 repos~3.2kAutomated safety check: NotesMIT
Better Proposals AutomationComposioHQ/awesome-claude-skills77k3 repos~764Automated safety check: PassNone
Contract And Proposal Writeralirezarezvani/claude-skills28k2 repos~3.4kAutomated safety check: PassMIT
ProposalChorus-AIDLC/Chorus1.2k—~5.5kAutomated safety check: PassAGPL-3.0
Proposal Writerholaboss-ai/holaOS11k—~574Automated safety check: PassCustom licence

Similar skills

  • Geo Proposal

    sickn33/agentic-awesome-skills

    Auto-generate a professional, client-ready GEO service proposal from audit data.

    47k GitHub starsUsed in 1 repo~3.2k tokens
    Sales & SupportAuto-check: notes

  • Better Proposals Automation

    ComposioHQ/awesome-claude-skills

    Automate Better Proposals tasks via Rube MCP (Composio). An agent skill from ComposioHQ/awesome-claude-skills.

    77k GitHub starsUsed in 3 repos~764 tokens
    Productivity & AutomationAuto-check passed

  • Contract And Proposal Writer

    alirezarezvani/claude-skills

    Generate professional, jurisdiction-aware business documents: freelance contracts, project proposals, SOWs, NDAs, and MSAs.

    28k GitHub starsUsed in 2 repos~3.4k tokens
    Legal & ComplianceAuto-check passed

  • Proposal

    Chorus-AIDLC/Chorus

    Chorus Proposal workflow on Hermes — create proposals with document and task drafts, manage dependency DAG, validate, submit, and run the read-only proposal reviewer via delegatetask.

    1.2k GitHub stars~5.5k tokensUpdated yesterday
    Sales & SupportAuto-check passed

  • Proposal Writer

    holaboss-ai/holaOS

    Draft client proposals and statements of work that scope, price, and win the project.

    11k GitHub stars~574 tokensUpdated 1 mo ago
    Sales & SupportAuto-check passed

  • Review Proposals

    anthropics/claude-for-legal

    Official

    Review and approve (or reject) pending playbook update proposals from the playbook-monitor agent and apply approved changes to the practice profile.

    9.6k GitHub starsUsed in 2 repos~410 tokens
    Sales & SupportAuto-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 Propose

What does Source Command Opsx Propose do?

Propose a new change - create it and generate all artifacts in one step. Source Command Opsx Propose is an agent skill from zhe-qi/clhoria-template.

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

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

How do I install Source Command Opsx Propose in Codex?

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

Can I use Source Command Opsx Propose 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-propose -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-propose, .gemini/skills/source-command-opsx-propose, .github/skills/source-command-opsx-propose and .opencode/skills/source-command-opsx-propose in your project.

What does Source Command Opsx Propose need to run?

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

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

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

About 1.1k tokens (SKILL.md is roughly 4.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 Source Command Opsx Propose?

Skills that share tags, products or a category with Source Command Opsx Propose: Geo Proposal (sickn33/agentic-awesome-skills, 47k stars), Better Proposals Automation (ComposioHQ/awesome-claude-skills, 77k stars), Contract And Proposal Writer (alirezarezvani/claude-skills, 28k stars) and Proposal (Chorus-AIDLC/Chorus, 1.2k 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 Propose?

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.