Terminal Ops
Evidence-first repo execution: run commands, debug CI, make narrow fixes, and report exactly what changed and what was verified.
- What
- Evidence-first repo execution: run commands, debug CI, make narrow fixes, and report exactly what changed and what was verified.
- Cost
- Free
- Needs
- Use "Terminal Ops" with your Muse.
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor: an operator workflow for evidence-first terminal execution inside ECC harnesses. Use it when the user wants a command run, a repo checked, a CI failure debugged, or a narrow fix pushed with exact proof of what was executed and verified. Deliberately narrower than general coding guidance: resolve the working surface (exact repo path, branch, local diff state, requested mode), read the failing surface before changing anything, keep the fix narrow (one dominant failure at a time, smallest useful proving command first), and report execution state with exact status words: inspected, changed locally, verified locally, committed, pushed, or blocked. Pulls in companion skills when relevant: verification-loop for proving steps, tdd-workflow for regression coverage, security-review for secrets or auth, github-ops for CI and PR state, knowledge-ops for durable context. By @affaan-m, listed here with credit to its creator. From the affaan-m/ECC repository (MIT). Honest caveats: an operator workflow, not a sandbox; commands run for real. Never claim fixed until the proving command was rerun, never claim pushed unless the branch actually moved upstream, and never use destructive git commands. Skill Harbor never reviews the code, review it yourself before use.
Version:
Install
Copy the install package below, then paste it into MuseThe install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?
Use "Terminal Ops" with your Muse. 1. Open the skill: https://github.com/affaan-m/ECC/blob/main/skills/terminal-ops/SKILL.md and copy the full SKILL.md text. 2. Paste it into a chat with Muse and add: "Debug this CI failure: [paste log]" or "Run the tests and report exactly what changed" or "Check the repo state on branch [name]." 3. State the requested mode up front: inspect, fix, verify, or push. Stay read-only if you only asked for an audit. Tip: ask for the SURFACE / EVIDENCE / ACTION / STATUS output format so you always know what was proven versus merely attempted. Safety: a skill is plain-text instructions; it runs nothing by itself. Commands run for real, so review destructive ones before they execute and keep secrets out of any chat.
Saved to your recent installs. Find it anytime on /connect.
Questions
How do I install a build?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a build before installing it.