Install
$ agentstack add skill-yipxiyi-openarc-openarc ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
OpenArc Entry
Use this as the first stop when the user says "use OpenArc" or asks for repository governance without naming a specific skill.
Fast Routing
Map the user's request to the narrowest skill:
| User Intent | Use | | --- | --- | | "Set up OpenArc here" | repository-governance, then profile-specific governance skills as needed | | "What is missing?" / "Audit this repo" | repository-governance, then run the scan helper if available | | "Clarify this request" / "New feature" / "New goal" | clarification-gate, then route to PRD, spec, plan, or implementation | | "Write PRD" | product-governance | | "Write spec" | spec-workflow | | "Plan implementation" | planning-engine | | "Define design system" | design-governance | | "Define brand" | brand-governance | | "Organize assets" | assets-governance | | "Migrate existing workspace" | workspace-migration | | "Version this change" | version-governance | | "Branch, commit, PR, release" | release-workflow | | "Prepare for open source" | open-source-maintenance |
Default First Pass
For a new or unfamiliar repository:
- Scan existing files before writing.
- Use the detected
repo_profileto separate core, delivery, and conditional governance. - Report what already exists, what is profile-relevant missing, and what conflicts.
- Recommend one of:
- bootstrap missing governance
- migrate existing docs
- clarify a new goal or change before writing PRD, spec, or plan
- create one spec and plan
- prepare branch/PR/release
- Ask only for decisions that materially affect output.
Helper Scripts
If this plugin's scripts/openarc.py is available, prefer:
python3 plugins/openarc/scripts/openarc.py scan .
python3 plugins/openarc/scripts/openarc.py doctor plugins/openarc
Use script output as evidence, not as a replacement for judgment.
Rules
- Do not load every OpenArc skill by default.
- Do not create all governance docs unless the user asks for full setup.
- Use
clarification-gatebefore PRD, spec, plan, or implementation work when the request is broad, ambiguous, risky, or new. - Do not require
docs/DESIGN.md,docs/BRAND.md, ordocs/assets/*for script, CLI, automation, library, or docs-only repositories unless the repo already has UI or brand signals. - Prefer a small first useful artifact over a complete governance dump.
- Existing repository conventions win over OpenArc templates.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: Yipxiyi
- Source: Yipxiyi/OpenArc
- License: MIT
- Homepage: https://github.com/Yipxiyi/OpenArc
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.