Run any Skill in Manus with one click

chapar-opencode-skills

Stars3

Forks1

UpdatedMay 13, 2026 at 20:15

Maintain Chapar OpenCode configuration, agent skill layout, project skill migration, permission rules, AGENTS.md, and agents/skills playbooks. Use when changing opencode.json, creating or moving project skills, updating skill trigger policy, or removing legacy Pi skill references.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

mmrezaie

mmrezaie/chapar

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

SKILL.md

readonly

name	chapar-opencode-skills
description	Maintain Chapar OpenCode configuration, agent skill layout, project skill migration, permission rules, AGENTS.md, and agents/skills playbooks. Use when changing opencode.json, creating or moving project skills, updating skill trigger policy, or removing legacy Pi skill references.

Chapar OpenCode Skills

Use this playbook when editing OpenCode-facing agent configuration or the project-local skill catalog under agents/skills.

Scope

Key files:

opencode.json
AGENTS.md
agents/README.md
agents/skills/*/SKILL.md

Use skill-creator too when creating or substantially rewriting a skill.

Invariants

OpenCode project skills live under agents/skills.
Do not reintroduce legacy Pi skill paths or project state.
Keep AGENTS.md as baseline repository guidance; keep detailed workflow logic in focused skills.
Keep opencode.json permissions narrow and task-oriented. Do not add broad write, shell, token, or secret access just to make a workflow convenient.
Do not allow edits to spack/, .spack-env/, lockfiles, or .git/.
Skill descriptions should be trigger-oriented and specific enough for OpenCode to select the right playbook without over-triggering unrelated tasks.

Editing Procedure

Identify whether the change is config, skill content, skill layout, or docs.
For new skills, create agents/skills/<name>/SKILL.md with kebab-case name and a description that states when to use it.
Update AGENTS.md when the skill covers a repository workflow that agents must consult before changing files.
Update agents/README.md when the catalog structure or major skill set changes.
Update opencode.json only for paths and commands the skills actually need.
Keep behavior/config changes separate from documentation-only changes when committing.

Validation

python3 agents/skills/skill-creator/scripts/quick_validate.py agents/skills/<skill-name>
git diff --check

Search for stale paths before finishing:

rg 'legacy Pi|pi/skills' AGENTS.md agents opencode.json .gitignore

If historical Pi references remain only in external upstream links, call that out explicitly.

More from this repository

same repository

chapar-ci-artifact-watch

mmrezaie/chapar

Inspect live Chapar CI/CD build progress by reading durable filesystem artifact roots directly instead of waiting for GitHub Actions or GitLab UI logs. Use whenever the user asks what is happening with a running, queued, stuck, timed-out, or slow CI build, especially Rocky 9/Rocky 10 hpcsim builds, package installs, modulefile publication, release roots, buildcache roots, ccache roots, or site-specific mounts such as /resources, /Volumes/resources, ~/resources, or another mounted artifact tree.

2026-06-113

chapar-incus-ci-triage

mmrezaie/chapar

Triage Chapar GitHub Actions Incus Spack-environment CI failures, including hpcsim Rocky 9/Rocky 10 builds and future environment workflows. Use when an Incus Spack build fails, succeeds on one Rocky version but not the other, or when inspecting self-hosted runner/build logs.

2026-06-113

chapar-release-helper

mmrezaie/chapar

Modify or debug Chapar's current hpcsim release helper envs/hpcsim/release.sh. Use for hpcsim release builds, staging/promote logic, module refresh, generated Spack scopes, and release metadata. For generic package/env edits, use chapar-spack-env-change.

2026-06-113

chapar-buildcache

mmrezaie/chapar

Modify or debug Chapar buildcache or shared ccache behavior, migration, quarantine, index refresh, and cache publication for hpcsim or future Spack environments. Use for docs/buildcache.md, ci/push-buildcache.sh, release helper migration, or buildcache CI failures.

2026-06-103

chapar-commit

mmrezaie/chapar

Prepare Chapar commits and pushes with the project's commit-splitting and message policy. Use whenever the user asks to commit, push, split commits, or prepare a PR branch.

2026-06-103

chapar-config-scope-change

mmrezaie/chapar

Modify Chapar Spack configuration scopes under etc/system, etc/user, include.yaml, externals, mirrors, providers, modules, or install-tree settings. Use for config layering and OS-specific scope changes.

2026-06-103

name	chapar-opencode-skills
description	Maintain Chapar OpenCode configuration, agent skill layout, project skill migration, permission rules, AGENTS.md, and agents/skills playbooks. Use when changing opencode.json, creating or moving project skills, updating skill trigger policy, or removing legacy Pi skill references.

Chapar OpenCode Skills

Use this playbook when editing OpenCode-facing agent configuration or the project-local skill catalog under agents/skills.

Scope

Key files:

opencode.json
AGENTS.md
agents/README.md
agents/skills/*/SKILL.md

Use skill-creator too when creating or substantially rewriting a skill.

Invariants

OpenCode project skills live under agents/skills.
Do not reintroduce legacy Pi skill paths or project state.
Keep AGENTS.md as baseline repository guidance; keep detailed workflow logic in focused skills.
Keep opencode.json permissions narrow and task-oriented. Do not add broad write, shell, token, or secret access just to make a workflow convenient.
Do not allow edits to spack/, .spack-env/, lockfiles, or .git/.
Skill descriptions should be trigger-oriented and specific enough for OpenCode to select the right playbook without over-triggering unrelated tasks.

Editing Procedure

Identify whether the change is config, skill content, skill layout, or docs.
For new skills, create agents/skills/<name>/SKILL.md with kebab-case name and a description that states when to use it.
Update AGENTS.md when the skill covers a repository workflow that agents must consult before changing files.
Update agents/README.md when the catalog structure or major skill set changes.
Update opencode.json only for paths and commands the skills actually need.
Keep behavior/config changes separate from documentation-only changes when committing.

Validation

python3 agents/skills/skill-creator/scripts/quick_validate.py agents/skills/<skill-name>
git diff --check

Search for stale paths before finishing:

rg 'legacy Pi|pi/skills' AGENTS.md agents opencode.json .gitignore

If historical Pi references remain only in external upstream links, call that out explicitly.