task-observer
SolidMonitors task execution for skill improvement opportunities. Use this skill during ANY multi-step task, agentic workflow, or substantive work session where the agent is using tools and producing deliverables. It captures patterns, user corrections, workflow insights, and methodology worth preserving as reusable skills. Also triggers during post-task feedback discussions and when the user explicitly mentions skill observations, improvements, the observation log, skill taxonomy, or asks the agent to watch for skill opportunities. Also known as "One Skill to Rule Them All" — trigger on this phrase too. IMPORTANT: this skill should be invoked at the start of every task-oriented session — if you are about to use tools to produce deliverables, invoke this skill first. For reliable activation, pair this description with a CLAUDE.md instruction or harness-level session-start hook (see Recommended Activation Setup) — description-level matching alone is not enforceable.
Install
Quality Score: 88/100
Skill Content
Details
- Author
- rebelytics
- Repository
- rebelytics/one-skill-to-rule-them-all
- Created
- 5 months ago
- Last Updated
- 1 weeks ago
- Language
- N/A
- License
- CC-BY-4.0
Similar Skills
Semantically similar based on skill content — not just same category
self-audit
Self-audit this skills repo against CLAUDE.md invariants, the v3 artifact contract, and README/CLAUDE.md/docs sync via three parallel read-only subagents. Local meta-skill — independent of the /task:* pipeline.
skill-capture
Turn a recurring in-session workflow into a reusable Claude Code skill. Load this the moment you notice you have run the SAME multi-step sequence (same ordered steps or commands, small variation allowed) about three times in the current session, or when open candidates are waiting in .credo/skill-candidates.md at session start or resume. It is heuristic and in-session only - no persistent counter, no tracking backend. Mode-gated like the audit nit-disposition policy: autonomous mode NEVER builds a skill (it only appends a candidate note and keeps working), active / passive / default propose the capture via the Ask tool and build only on an explicit GO. Applies inside subagents too, where the safest branch (autonomous: candidate note only, never ask, never build) is the default whenever the mode cannot be determined.
ops
Execute a milestone's interactive 🔧 Operational and 🔎 Investigation tasks — the judgment-bound work that is NOT auto-dispatched. Two modes in one pass: Operational changes production/environment state through a sanctioned surface (config/catalog/entity authoring, backfills, alarm config, dependency installs, session/machine setup); Investigation produces a defensible decision from live data (diagnoses, spikes, zero/anomaly triage) and files follow-on tasks. Enforces: autonomous runs STAGE (never verdicts, never ✅ Done), read-only diagnosis before any write, falsify every "it's fine", audited read-modify-write, reconcile+capture, "Done ≠ deployed ≠ seeded ≠ working". Records durable research to a staging journal. Use when the user says "work the ops tasks", "run ops/tooling for milestone X", "work the operational/investigation tasks", or starts an overnight or interactive ops run on a project's task board.