메뉴
SkillsMP는 aiosbrain/aios-workspace에서 64개의 skill을 수집했습니다. skill을 열어 소스와 세부 정보를 확인하세요.
수집된 skill 64개 중 40개를 표시합니다.
Manage the AIOS Linear board (the ONLY PM tool — Plane is retired). Use whenever updating, reading, or commenting on AIOS Linear issues (identifiers like AIO-72, AIO-75), the brain→PM projection-tracking epic, or the backlog. Triggers on "update AIO-NN", "the…
원문 언어: 영어
Use YOUR own Slack to act as you — send messages and DMs to teammates, read your channels/DMs, and react — via the `slack` CLI (a zero-dependency tool that talks straight to the Slack Web API with your USER token). Messages post AS you and replies land in…
원문 언어: 영어
Verify that a fix or change actually did what it was for, before reporting that it works. Use before any "it works", "verified", "fixed", "confirmed", or "done" about something that was previously broken — and whenever a hook or a reviewer asks you to…
원문 언어: 영어
Analyze recent Codex session history, actual skill-loading evidence, resolver usage, installed skill catalogs, and accumulated Claude instincts to identify repeated friction, missed skill-routing opportunities, and reusable workflow improvements. Use when…
원문 언어: 영어
Pull Granola meeting notes and transcripts into 1-inbox/transcripts/ by calling the Granola API directly (this is our own connector — it does NOT use the Granola MCP). Use when the user says "pull my Granola notes", "get today's meeting transcripts", "ingest…
원문 언어: 영어
Propose 3–5 non-overlapping agent workstreams from the AIO Linear board. Use before starting parallel agent batches, when planning a factory work session, or when the user asks for a workstream update / batch plan. Triggers on "workstream update", "batch…
원문 언어: 영어
Audit whether a candidate spec is ready against an immutable repository baseline and the AIOs readiness rubric. Use for “is this spec ready,” readiness evaluation, or repository-backed spec audits; never revise or publish the candidate.
원문 언어: 영어
Build a presentation-grade, brand-themeable HTML slide deck — demo, proposal, update, or pitch — from a pre-debugged component library instead of a blank page. Ships three themes, a slide catalog with copy-pasteable markup, a brand intake schema for adding…
원문 언어: 영어
Query and update Linear issues, projects, and cycles via the Linear GraphQL API using a personal API key (our own connector — Linear's MCP is OAuth-only). Use when the user asks about their Linear issues, sprint/cycle status, or wants to create or update an…
원문 언어: 영어
Use ast-grep (sg) for AST-aware code search and deterministic rewrites/codemods across many languages. Trigger when the target is syntax SHAPE, not text: find every function/call/class/import shaped like X, rewrite console.log to logger.info, strip `as any`,…
원문 언어: 영어
Classify every unmerged remote branch as truly-unmerged, already-shipped-under-a-different-hash (squash-merge duplicate), or genuinely stale — with evidence, not guesswork. Use when asked "are these branches actually stale", "check unmerged branches", "clean…
원문 언어: 영어
Fresh-context review of a diff with severity-triaged findings (P1/P2/P3). Use when the user asks to "review" a change/PR/diff, or as the standard gate on any agent-authored change before merge. The reviewer must NOT be the session that wrote the code.
원문 언어: 영어
The closing step of every task — codify what was learned so the system gets better each use. Use after completing any task where the agent was corrected, a bug was found, a procedure was discovered, or friction repeated. Also on request ("capture this", "make…
원문 언어: 영어
Use whenever a task needs a commit or a git-history investigation. Covers atomic commits, staging by hunk, detecting commit-message style, rebase/squash/fixup/autosquash, blame, bisect, reflog, git log -S/-G, and questions like who wrote this or when was this…
원문 언어: 영어
Research → Plan → Implement discipline for any non-trivial change. Use BEFORE writing code when a task touches more than one file, introduces a dependency, changes behavior users see, or when the user asks to "plan", "spec", or "design" something. Skip only…
원문 언어: 영어
Coding-standards conscience for writing or editing code in a typed language (Python, TypeScript, Rust, Go, …). Use when authoring non-trivial code and you want strict types, honest module size, and tests that assert behavior not prose. A code-smell +…
원문 언어: 영어
Structured restructuring of EXISTING code — extract, split, rename, modernize, de-duplicate, move responsibilities — with zero behavior change and a test run after every step. Use when the task is to reshape working code (not add a feature, not the post-diff…
원문 언어: 영어
Behavior-preserving cleanup pass over a reviewed diff — run AFTER tests pass and review is addressed, BEFORE merge. Deletes dead code, collapses needless indirection, applies YAGNI. Use when the user says "simplify", "clean up this diff", or as the standard…
원문 언어: 영어
Write or improve a SKILL.md so it actually triggers and actually changes agent behavior. Use when the user says "create a skill", "turn this into a skill", "why isn't this skill triggering", or when compound-learnings decides a lesson deserves a skill.
원문 언어: 영어
Four-phase root-cause debugging loop for anything broken, throwing, failing, flaky, or slow. Use whenever the user reports a bug or a test fails unexpectedly — BEFORE proposing any fix. Root cause first; a fix without a diagnosis is a guess.
원문 언어: 영어
Enforced RED-GREEN-REFACTOR test-driven development. Use when implementing any behavior change that can be expressed as a test — new features, bug fixes, edge cases. The test MUST fail first; a test that passes on first run proves nothing.
원문 언어: 영어
Find test files that exist on disk but run in neither the local test command nor CI (orphaned tests = false confidence), plus stale coverage reports. Use when asked "is this test actually running", "check test wiring", "orphaned tests". Flags and suggests…
원문 언어: 영어
Verify a change actually works by exercising it end-to-end and observing real behavior — not just green tests. Use before declaring any nontrivial change done, before opening a PR, or when the user asks "does this actually work?".
원문 언어: 영어
Rigorous visual QA for any UI you built or changed — web pages, components, and terminal/TUI output. Use AFTER a UI change and BEFORE calling it done, or when asked does this look right / match the mock / is the layout broken / does the CJK text clip.…
원문 언어: 영어
Place an engineer on the Agentic Maturity model (5-level spine × 5 axes) via a short interview, apply the verification cap, and prescribe the 2-3 highest-leverage patterns to practice next. Use when someone asks "assess my agentic maturity", "what should I…
원문 언어: 영어
Context-engineering hygiene audit — contract bloat, context-utilization discipline, skill misfires, MCP tool sprawl. Use on a weekly/monthly cadence, when sessions feel slow or agents "get dumber over time", or before onboarding new engineers onto the harness.
원문 언어: 영어
Token/cost visibility for agentic engineering — per session, per day, per model lane. Use when someone asks about token usage, AI spend, "which lane is the money going to", or as a weekly habit once multi-model routing is live. Read-only reporting; changes…
원문 언어: 영어
Draft or restructure a Linear issue, implementation spec, acceptance criteria, or issue slice into a cold-start buildable increment. Use for “write the spec,” “make this issue buildable,” or equivalent authoring requests; do not use to evaluate, repair,…
원문 언어: 영어
Change install, onboarding, workspace hydration, config merge, skill installation, or uninstall behavior. Use to preserve user-authored state while testing idempotency, collisions, symlink or path escape, modes, dependencies, partial failure, rollback, and…
원문 언어: 영어
Change `aios update`, toolkit pull, re-exec, contribution worktrees, scheduler refresh, or version handoff behavior. Use to preserve preview and mutation boundaries, dirty state, source proof, runtime environment, recovery, and fail-closed semantics.
원문 언어: 영어
Close or abandon a delivery worktree after merge or blockage. Verify remote state, ancestry, post-merge behavior, and protected primary state before classifying cleanup as safe, blocked, or owner-decision; never delete dirty or unproven work.
원문 언어: 영어
Change a versioned API, event, transcript, persisted record, schema, or wire contract. Use when compatibility, migrations, producers, consumers, validators, fixtures, or rollback and read behavior must be designed and sequenced.
원문 언어: 영어
Publish or replace an AIO Linear issue description from a locally evaluated candidate. Use only when the user explicitly asks to publish and provides or approves the exact issue and candidate; never auto-trigger from review, readiness, authoring, or repair…
원문 언어: 영어
Change transcript ingestion, extraction, redaction, provenance, decision or task derivation, or audience-tier output. Use to enforce source allowlisting, grounding, redaction-before-egress, tier boundaries, containment, replay safety, and extraction…
원문 언어: 영어
Repair a candidate spec only after concrete readiness findings exist or the user explicitly requests repair. Convert findings into bounded edits while preserving fixed decisions, capability truth, scope, and intent; do not publish or claim readiness without…
원문 언어: 영어
Begin implementation safely in an AIOs repository when a task names or needs a branch or worktree. Resolve the repository, issue, owner, base, and branch; snapshot primary dirty state; and hand off a hydrated worktree without stashing, resetting, cleaning, or…
원문 언어: 영어
Reconcile Local Bugbot, CodeRabbit, CI, GPT review, security review, and plan-conformance findings for one exact PR head. Use after deterministic findings collection when evidence is ambiguous; do not re-review code, fix, merge, or treat a green check as…
원문 언어: 영어
Verify source changes that require rebuilt `dist/`, vendored assets, generated catalogs, Tauri resources, manifests, or lock artifacts. Use to identify source-to-generated relationships, rebuild canonically, prove freshness and parity, and test packaged…
원문 언어: 영어
Verify claims about lifecycle hooks, prompt injection, tool interception, stop continuation, subagents, or cross-runtime parity. Use for runtime or adapter preflights and capability matrices before a spec relies on behavior that may differ by installed…
원문 언어: 영어
Prove parity when a JSON Schema, TypeScript or runtime validator, generated type, or fixture set changes. Use to detect optionality, enum, default, coercion, unknown-field, and test-wiring drift; do not decide product contract semantics.
원문 언어: 영어