cyberuni
- 164 skills
- 0 followers
- 18 hours ago last updated
- ▌ Ssa Lowering · cyberuni bundleInternal skill: the reasoning front-end that lowers one-or-more change requests into a partitioned set of Missions — one owning Mission per spec-node (SSA) — applying the Oracle (should we?) and Architect (where/barrier?) lenses, resolving same-node contention into ordered versioned-RAW edges, and lowering only the frontier deeply; run by the conductor during intake/Explore, not triggered by users directly.
- ▌ Add Scenario · cyberuni bundleUse this skill when adding a new scenario to an ACED .feature suite — from a real failure, a production edge case, or a gap the user noticed.
- ▌ Define Agent · cyberuni bundleUse this skill when the user wants to create or improve an agent definition — a named, reusable role that can be delegated to as a subagent, loaded in-context as a persona, or both. Trigger on "create an agent", "write a conductor", "make an agent definition", "define a persona", "build a dual-mode agent", or "add an invokable agent".
- ▌ Define Skill · cyberuni bundleUse this skill when the user wants to create, scaffold, or formalize a workflow skill — a process, tool-based, or standard SKILL.md — from scratch or from an existing ad-hoc workflow. Trigger on "create a skill", "write a skill for X", "I want a skill that…", "turn this workflow into a skill", or "help me build this skill", even if they do not say "skill" explicitly. Not for agent definitions or personas (define-agent), reference-only rule sets (define-governance), or extracting the current session (skillify).
- ▌ Concept Index · cyberuni bundlePartial Skill: invoke by name only — project-spec/concept-index's engine that derives the by-concept view of a project spec into spec.md — used to re-unify a cross-cutting concern the capability folder tree scatters, not triggered by users directly.
- ▌ Doctrine Loop · cyberuni bundlePartial Skill: invoke by name only — the SDD doctrine loop, the Strategist's outer loop run by the Scanner — invoked by the doctrine-loop delegate, not triggered by users directly.
- ▌ Manage Ignore · cyberuni bundlePartial Skill: invoke by name only — intake/manage-ignore's curation engine for the SDD ignore rules — loaded by the manage gateway (Housekeeping), not triggered by users directly.
- ▌ Mission Graph · cyberuni bundleInternal skill: the mission-graph kernel — a git-tracked, append-only work-graph store folded into a ready frontier and a cycles repair view; used by the cyberfleet-batch dispatch loop, not triggered by users directly.
- ▌ Pause Mission · cyberuni bundleCheckpoint an in-progress SDD mission INTO its plan brief so any later session can pick it up. Use this skill when asked to 'pause', 'wrap up for now', or 'stop here' mid-mission — update the plan's todo statuses and rewrite its ## NEXT anchor so a fresh session continues exactly where you left off. Pass --approve to also clear the mission for headless dispatch (sets the brief's status: approved).
- ▌ Start Mission · cyberuni bundleUse this skill to make a change to an SDD project — triggered by a general change request like "add a start-mission skill to sdd", "implement the auth capability", "revise the gateway spec", or "work on <github issue url>". Opens a change request against the durable project spec and runs the mission loop (explore → deliver → handoff).
- ▌ Improve Skill · cyberuni bundleAudit, improve, or write a SKILL.md — check description trigger coverage, structure, security, and agentskills.io compliance. Use when reviewing or creating a skill for Claude Code, Cursor, Codex, Copilot CLI, or any agentskills-compatible runtime, even if the user says "my skill isn't triggering", "review before I publish", or "check this skill."
- ▌ Blast Estimate · cyberuni bundlePartial Skill: invoke by name only — blast-estimate's engine that computes a Mission's blast (low/medium/high) from its touch-set plus the project corpus and lines it up against the hand-typed declared blast — the engine for the blast-estimate node, consumed by the mission-graph's writer. Not triggered by users directly.
- ▌ Discover Plans · cyberuni bundlePartial Skill: invoke by name only — intake/plan-discovery's engine that surfaces resumable mission plan briefs — used by the sdd gateway on entry, not triggered by users directly.
- ▌ Discover Specs · cyberuni bundlePartial Skill: invoke by name only — corpus/discovery's frontmatter-scanning engine across the SDD spec locations — used by the sdd gateway to scan statuses and by start-mission to locate the project spec, not triggered by users directly.
- ▌ Formation Loop · cyberuni bundlePartial Skill: invoke by name only — the SDD formation loop, the Architect's outer loop run by the Warden — invoked by the formation-loop delegate, not triggered by users directly.
- ▌ Resume Mission · cyberuni bundleResume an in-progress SDD mission from its plan brief. Use when asked to 'load the plan', 'resume the mission', 'continue github-NN', or otherwise pick up an SDD .plan.md where it left off — re-establish the working method and spec context, find the next todo, and continue without relitigating settled ground.
- ▌ Define Command · cyberuni bundleUse this skill when the user wants to create or improve a command — a user-invoked-only slash workflow (`/name`) that never auto-triggers from the model. Trigger on "create a command", "add a slash command", "make a /deploy command", "add a user-only workflow", "convert this skill to a command", or "stop this skill from auto-triggering", even if they do not say "command" explicitly. Not for a companion command scaffolded alongside an agent definition — whether it adopts that agent in-session or gateways to it as a subagent (define-agent) — an auto-triggered workflow skill (define-skill), or a reference-only rule set (define-governance).
- ▌ Plan Retirement · cyberuni bundlePartial Skill: invoke by name only — the SDD Doctrine loop's last retro step — the gated, idempotent tracked deletion of a retired mission plan. Invoked by the doctrine-loop Scanner, not user-triggered; the clearance contract lives in the body + README.
- ▌ Check Freshness · cyberuni bundlePartial Skill: invoke by name only — the ACED eval-result freshness check — decides whether a recorded result still describes the configuration on disk, not user-triggered.
- ▌ Collision Ladder · cyberuni bundleInternal skill: at a known node-level collision between two missions, descends the finer-than-node ladder (file → region → semantic) to classify the clash hard or soft — a read-only downgrade-only disambiguator, not triggered by users directly.
- ▌ Resolve Tracking · cyberuni bundlePartial Skill: invoke by name only — intake/resolve-tracking's engine that resolves an artifact's tracked-or-ignored signal — run by the conductor at intake, not triggered by users directly.
- ▌ Verify Scenarios · cyberuni bundlePartial Skill: invoke by name only — the Gherkin-scenario-to-test-report bridge verifier — invoked by the impl-judge at the impl gate, not triggered by users directly.
- ▌ Contribute Skill · cyberuni bundleUse this skill when contributing local improvements to an installed skill back to its source repo via PR.
- ▌ Check Plan Safety · cyberuni bundlePartial Skill: invoke by name only — plan-brief/check-plan-safety's guard engine against machine-local path leaks in tracked plan artifacts — the CI guard, not triggered by users directly.
- ▌ Aced Builder Impl · cyberuni bundlePartial Skill: invoke by name only — the ACED Builder bar at the impl gate — the frozen .feature conformance criteria. Loaded by the ACED impl-producer to self-align and by the impl-judge to verify. Not triggered by users directly.
- ▌ Aced Builder Spec · cyberuni bundlePartial Skill: invoke by name only — the ACED Builder bar at the spec gate — the agent-configuration contract criteria. Loaded by the ACED spec-producer to self-align and by the spec-judge to grade. Not triggered by users directly.
- ▌ Define Governance · cyberuniCreate or revise a governance file — reference-only criteria or rules that other skills and agents load on demand. Use when the target is the criteria file itself, even if the user just says "write standards for" or "improve this governance".
- ▌ Extract Situation · cyberuni bundlePartial Skill: invoke by name only — the ACED blind-brief extractor — loaded by aced-case-judge to compose a simulating context's brief, not user-triggered.
- ▌ Manage Skill Dirs · cyberuni bundlePartial Skill: invoke by name only — config-authoring/skill-dirs' curation engine for the extra skill-scan locations improve-skill's validate engine uses — loaded by the manage gateway, not triggered by users directly.
- ▌ Aced Impl Producer · cyberuniPartial Skill: invoke by name only — the ACED impl-producer's diagnose-and-refine loop — loaded by define-agent, define-skill, and define-governance, and by the public improve skill for ACED-tracked targets, not user-triggered.
- ▌ Check Project Specs · cyberuni bundlePartial Skill: invoke by name only — corpus/spec-floor's engine that runs every project-spec check, over the whole corpus or over one project — the commit-floor and CI entrypoint, not triggered by users directly.
- ▌ Check Retired Terms · cyberuni bundlePartial Skill: invoke by name only — retired-terms' guard engine against survivors of a retired path, directory, or naming convention across the whole tracked corpus — the CI guard, not triggered by users directly.
- ▌ Manage Spec Anchors · cyberuni bundlePartial Skill: invoke by name only — corpus/spec-anchors' curation engine for SDD's extra spec-discovery anchors — loaded by the manage gateway (Housekeeping), not triggered by users directly.
- ▌ Resolve Governances · cyberuni bundlePartial Skill: invoke by name only — the SDD governance matcher, resolving which actor-bar governances apply to a touched file — run by the conductor and the cold spec/impl judges, not triggered by users directly.
- ▌ Aced Architect Impl · cyberuni bundlePartial Skill: invoke by name only — the ACED Architect bar at the impl gate — whether an agent-configuration artifact is well-formed as configuration. Loaded by the ACED impl-producer to self-align and by the impl-judge to grade. Not triggered by users directly.
- ▌ Quill Builder Impl · cyberuni bundlePartial Skill: invoke by name only — the Quill Builder bar at the impl gate — the document-scoped inspection rule and the judged defect catalog a per-scenario check cannot reach. Loaded by the Quill impl-producer to self-align and by the impl-judge to verify. Not triggered by users directly.
- ▌ Quill Builder Spec · cyberuni bundlePartial Skill: invoke by name only — the Quill Builder bar at the spec gate — what a documentation spec must contain. Loaded by the Quill spec-producer to self-align and by the spec gate to grade. Not triggered by users directly.
- ▌ Check Spec Structure · cyberuni bundlePartial Skill: invoke by name only — project-spec/check-spec-structure's engine that audits a project spec's internal node-shape — feeds the formation Warden, not triggered by users directly.
- ▌ Lifecycle Governance · cyberuni bundlePartial Skill: invoke by name only — the SDD spec lifecycle contract. Loaded by sdd, spec-gate, start-mission, the conductor, and the spec-judge, not user-triggered.
- ▌
- ▌ Touch Set Correction · cyberuni bundleInternal skill: reconciles a Mission's declared touch-set against what its git diff actually changed — read-only, post-hoc; used to correct the mission-graph's hazard set from prediction to reality, not triggered by users directly.
- ▌ Manage Model Runners · cyberuni bundlePartial Skill: invoke by name only — the ACED manage-model-runners engine — loaded in-session by the ACED manage gateway, not user-triggered.
- ▌ Check Spec References · cyberuni bundlePartial Skill: invoke by name only — project-spec/check-spec-references' engine that resolves every relative reference in one project spec's markdown and fails on the ones pointing at nothing — run from the per-project CI entrypoint, not triggered by users directly.
- ▌ Combat Log Governance · cyberuni bundlePartial Skill: invoke by name only — the SDD combat-log contract, the durable provenance record's shape. Loaded by the conductor, spec-gate, and the doctrine-loop Scanner, not user-triggered.
- ▌ Scaffold Project Spec · cyberuni bundlePartial Skill: invoke by name only — lay out an SDD project-spec
- ▌ Repair Private Skills · cyberuni bundlePartial Skill: invoke by name only — the ACED manage-gateway engine that validates and repairs repo-private skill hygiene — loaded in-session by the ACED manage gateway, not user-triggered.
- ▌ Check Plugin Manifests · cyberuni bundlePartial Skill: invoke by name only — plugin/check-plugin-manifests' guard engine against a manifest declaring a component the package does not ship — the CI guard, not triggered by users directly.
- ▌ Check Scenario Overlap · cyberuni bundlePartial Skill: invoke by name only — project-spec/scenario-overlap's engine that detects the same behavior specified in two nodes' suites across one project spec — feeds the formation Warden, not triggered by users directly.
- ▌ Manage Scenario Bridge · cyberuni bundlePartial Skill: invoke by name only — the curation engine for a project's scenario-bridge.toml — loaded by the manage gateway (Setup & discovery), not triggered by users directly.
- ▌
- ▌ Remediation Governance · cyberuni bundlePartial Skill: invoke by name only — the SDD remediation bar: how a producer responds to a `change` verdict at either gate. Loaded by the spec-producer and the impl-producer, not user-triggered.
- ▌
- ▌
- ▌
- ▌ Check Partition Quality · cyberuni bundlePartial Skill: invoke by name only — project-spec/partition-quality's engine: measures from git history how much parallel work a layout permits, and compares candidate layouts. Opt-in from scaffold-project-spec and the formation loop, and runnable standalone; not triggered by users directly.
- ▌
- ▌
- ▌ Spec Producer Governance · cyberuni bundlePartial Skill: invoke by name only — the SDD default spec-producer procedure. Loaded in-session by the conductor when it runs the spec-producer role inline, not user-triggered.
- ▌
- ▌
- ▌ Spec Structure Governance · cyberuni bundlePartial Skill: invoke by name only — the SDD project-spec organization contract: what kind of node a spec is and where that kind lives. Loaded by scaffold-project-spec, place-node, the formation Warden, and the architect bars, not user-triggered.
- ▌ Gate Validation Governance · cyberuni bundlePartial Skill: invoke by name only — the SDD gate-legality contract. Loaded by spec-gate, the conductor, and the spec-judge, not user-triggered.
- ▌ Plugin Contract Governance · cyberuni bundlePartial Skill: invoke by name only — the SDD plugin contract for what a plugin implements. Loaded by the conductor and by plugin authors, not user-triggered.
- ▌ Solution Producer Governance · cyberuni bundlePartial Skill: invoke by name only — the SDD default solution-producer procedure. Loaded in-session by the conductor when it runs the solution-producer role inline, not user-triggered.