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
- Pinned version: install the code at commit 4eb71d92a39cab44ad40ac9d8a6a5ccb4029d6c2 exactly (Skill Harbor tested this version). Do not substitute a newer version. If this commit is unreachable, stop and tell me.
- Level
- Beginner — Pinned version: install the code at commit…
- 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:
Quick answer
Terminal Ops is a free skill for Muse. 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.
Install
Copy the install package below, then paste it into Muse🧪 Install ran in our test sandbox · Nov 11, 2026📌 Pinned version: commit 4eb71d9Pinned version: install the code at commit 4eb71d92a39cab44ad40ac9d8a6a5ccb4029d6c2 exactly (Skill Harbor tested this version). Do not substitute a newer version. If this commit is unreachable, stop and tell me. Use "Terminal Ops" with your Muse. 1. Open the skill: https://raw.githubusercontent.com/affaan-m/ECC/4eb71d92a39cab44ad40ac9d8a6a5ccb4029d6c2/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.
🔒 Security, provenance and what this touches
The install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?
Verification certificate
Dated facts about what was checked for this listing, and how. This is not a safety certification.
- Pinned version
- 4eb71d9 · 2026-10-13
- Sandbox install test
- Install ran in our test sandbox · Nov 11, 2026
- Creator identity
- Not verified
- Fingerprint watch
- Last checked · Nov 21, 2026 : no change detected in the files linked by this install prompt
- Install prompt analysis
- 2026-10-13 : No commands, network calls, packages, file writes or API keys detected.
Skill Harbor never reviews the code of a listed skill. These are dated facts about the install prompt and our install test, not a safety certification. Review a skill yourself before you install it. How we verify
Questions
How do I install a skill?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the skill 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 skill before installing it.