scaryrawr
- 65 skills
- 0 followers
- 6 hours ago last updated
- ▌ Gnome Extension Review · scaryrawrAudit or prepare this GNOME Shell extension for extensions.gnome.org review. Use after changing extension lifecycle, asynchronous work, signals, GLib sources, preferences, GSettings, supported Shell versions, packaging, or before a release or EGO submission.
- ▌ Verify Vivi · scaryrawr bundleVerify the Vivi CLI and libvaxis chat TUI through real PTY sessions, streamed Copilot responses, and durable terminal evidence. Use when changing CLI commands, terminal input/rendering, conversation lifecycle, or Copilot streaming.
- ▌ Validate Fish Plugin · scaryrawrValidate fish wrapper and completion changes with syntax and smoke checks.
- ▌ Review Fish Wrapper Changes · scaryrawrReview fish wrapper changes for token injection consistency and safe argument passthrough.
- ▌
- ▌ Update Completions · scaryrawrUpdate fish shell completions for the GitHub Copilot CLI based on its current help output. Use when asked to update, sync, or refresh completions, or when the CLI has been updated and completions need to match the latest flags, subcommands, and help topics.
- ▌ Smahtiepants · scaryrawr bundleUse this skill before answering questions or writing code that depends on a specific library, framework, language, runtime, or CLI tool (e.g. React, Express, Node, Python, Rust, CSS, Docker, Git, Bun). Your training data has a cutoff and APIs change, get deprecated, or gain new features after it. smahtiepants searches a local, up-to-date mirror of DevDocs so you can ground answers in current documentation instead of relying on potentially stale memory. Use it whenever you are unsure about an API signature, default, option name, version-specific behavior, or "is this still the right way to do X", and whenever the user asks how to use a library or what a function/flag does.
- ▌ Smahtiepants MCP · scaryrawr bundleUse this skill when smahtiepants MCP tools are available and a task depends on current documentation for a library, framework, language, runtime, API, or CLI tool (for example React, Express, Node, Python, Rust, CSS, Docker, Git, or Bun). Prefer the MCP tools `list_docsets`, `search_docs`, and `get_page_content` before answering from memory whenever API details, option names, defaults, examples, or "is this still current" questions could be stale. This is the MCP-tool version of the smahtiepants documentation workflow; use it instead of shelling out to the CLI when the MCP server is connected.
- ▌ Code Review · scaryrawr bundlePerform a thorough code review of diffs or branch comparisons for correctness, structure, regression risk, and edge-case coverage. Use when the user asks to review uncommitted changes, inspect a PR/diff, compare a branch to default, or audit recent changes for regressions. Not for general conceptual explanations of code-review practices or static-analysis tooling.
- ▌ Skill Creator · scaryrawr bundleUse this skill to create, revise, package, evaluate, or optimize GitHub Copilot skills and reusable SKILL.md-based agent instructions. Use it whenever the user wants a new Copilot skill, edits to an existing skill, eval/test prompts, skill benchmarking, skill packaging, trigger-description optimization, or reusable agent instructions.
- ▌ Tmux · scaryrawr bundleRemote control tmux sessions for interactive CLIs (python, gdb, etc.) by sending keystrokes and scraping pane output.
- ▌ Azure CLI · scaryrawrWhen users share links (such as visualstudio.com or dev.azure.com) and/or mention Azure DevOps, use the Azure DevOps CLI to interact with work items, pull requests (PRs), repositories, and more.
- ▌
- ▌ Figure It Out · scaryrawrDesign an auditable playbook when no narrower one fits: a large migration, an ambitious multi-part change, or work a human reviews after stepping away. Scales rigor to the task, runs a hypothesis loop, and logs decisions via show-me-your-work. Use for /figure-it-out, 'figure it out', a large migration, or when no narrower playbook applies.
- ▌ Ado Codespaces · scaryrawr bundleSupervise Azure DevOps coding agents running in GitHub Codespaces. Use when asked to list, start, stop, inspect, or message these Codespaces or agents.
- ▌ Show Me Your Work · scaryrawr bundleKeep a reviewable decision trail for long-running or unattended work: a TSV log with one row per decision (what, why, evidence, result). Local by default; commit it when a reviewer needs the trail to trust the result. Use for /show-me-your-work, autonomous or multi-phase runs, or work a human reviews after stepping away.
- ▌ Technical Writing · scaryrawrLayered technical-writing standard: Diátaxis structure, Google developer style sentences, STE instruction rules, Global English syntax. Use for /technical-writing or when writing or reviewing docs, RFCs, readmes, PR descriptions, or commit messages.
- ▌ Pstack Schema Validate · scaryrawr bundleValidate pstack snapshots, verification receipts, durable handoffs, or Markdown plans against the plugin's versioned contracts. Use for "validate this pstack artifact", checking pstack JSON, or verifying a pstack plan profile. Not for general JSON schema validation.
- ▌ Principle Prove It Works · scaryrawrApply after completing a task, before declaring done. Verify against the real artifact (run the feature, read the actual value, inspect the diff), not a proxy, self-report, or 'it compiles.'
- ▌ Autoresearch Create · scaryrawr bundleSet up and run an autonomous experiment loop for any optimization target. Use when asked to run autoresearch, optimize something repeatedly, start benchmark-driven experiments, or resume an existing .auto session.
- ▌ Create Verification Skill · scaryrawr bundleGenerate a project-local verification skill that drives your app the way a user does — any language, framework, or platform. Use for /create-verification-skill, "make a control skill for this repo", or when a project has no scripted way to prove UI/CLI/service behavior.
- ▌ Principle Build The Lever · scaryrawrApply to any non-trivial work, not just bulk work: edits, migrations, analyses, checks. Build the tool that does it or proves it (codemod, script, generator, or a skill your subagents follow) instead of working by hand. The tool is the artifact a reviewer can rerun.
- ▌ Principle Fix Root Causes · scaryrawrApply when debugging. Trace each symptom to its root cause and fix it there; reproduce first, ask why until you reach it, resist nil-check guards that silence crashes.
- ▌ Principle Experience First · scaryrawrApply when product, UX, or feature-scope tradeoffs come up. Choose user delight over implementation convenience; ship fewer polished features over more rough ones.
- ▌ Principle Model The Domain · scaryrawrApply when writing stateful logic, or when code branches a lot or repeats a shape assumption across files. Encode the domain in a structure instead of scattered conditionals.
- ▌ Autoresearch Finalize · scaryrawr bundleTurn a completed autoresearch session into clean, independently reviewable branches. Use when asked to finalize, clean up, or prepare autoresearch results for review.
- ▌ Maintain Verification Skill · scaryrawrPeriodic pass that keeps a project's verification skill and feature map honest: parallel source readers per feature, one live session driving every feature, at most one PR of proven corrections. Use for /maintain-verification-skill or "audit the verify skill".
- ▌ Principle Laziness Protocol · scaryrawrApply when refactoring, evaluating diff size, or tempted to add abstractions, layers, or signal threading. Bias toward deletion and the smallest change that solves the problem.
- ▌ Principle Attack The Premise · scaryrawrApply when two or more fixes that share one premise have failed the same gate. Take a census of which actors hold the imbalance before the next fix, then question the premise instead of writing another fix that assumes it.
- ▌ Principle Boundary Discipline · scaryrawrApply when wiring validation, error handling, or framework adapters. Concentrate guards at system boundaries (CLI, config, network, external APIs); trust internal types and keep business logic in pure functions.
- ▌ Principle Minimize Reader Load · scaryrawrApply when reviewing or shaping code that's hard to trace. Count layers between question and answer, and hidden state in the reader's head; collapse one-caller wrappers and shrink mutable scope.
- ▌ Principle Foundational Thinking · scaryrawrApply before writing logic: choosing core types and data structures, sequencing scaffold-vs-feature work, asking what concurrent actors share. Get the data structures right so downstream code becomes obvious.
- ▌ Principle Type System Discipline · scaryrawrApply when designing types, reviewing a function signature, or writing code in any statically-typed language. Make illegal states unrepresentable, brand semantic primitives, parse external data at boundaries, refuse to lie to the compiler, exhaust variants, derive from authoritative schemas.
- ▌ Principle Subtract Before You Add · scaryrawrApply when sequencing an addition, refactor, or rewrite. Remove dead weight, redundant validators, and stub references first, then build on the simpler base.
- ▌ Principle Guard The Context Window · scaryrawrApply when context is filling up: large outputs, long files, repeated reads, fan-out planning. Route bulk to subagents; keep summaries in the main thread, not raw payloads.
- ▌ Principle Never Block On The Human · scaryrawrApply when tempted to ask 'should I do X?' on reversible work. Proceed, present the result, let the human course-correct after the fact; reserve confirmation for irreversible actions.
- ▌ Principle Sequence Verifiable Units · scaryrawrApply to multi-step work (sweeps, migrations, runs of similar edits) and to how you stack commits and PRs. Break work into small units that each end in a verifiable state, check each before the next, and order delivery so the sequence proves itself to a reviewer.
- ▌ Principle Encode Lessons In Structure · scaryrawrApply when you catch yourself writing the same instruction a second time, or notice a recurring correction. Encode the rule as a lint, metadata flag, runtime check, or script instead of more text.
- ▌ Principle Redesign From First Principles · scaryrawrApply when integrating a new requirement into an existing design. Redesign as if the requirement had been a foundational assumption from day one, instead of bolting it on.
- ▌ Principle Test Behavior Not Implementation · scaryrawrApply when you write, change, or keep a test. Call the code the way its users do and assert the result they observe against a literal expected value. If the test would still pass when every imported function returns undefined, rewrite the assertion or delete the test.
- ▌ Principle Migrate Callers Then Delete Legacy Apis · scaryrawrApply when introducing a new internal API while old callers still exist. Migrate callers and delete the old API in the same wave instead of preserving compatibility layers.
- ▌ Principle Separate Before Serializing Shared State · scaryrawrApply when concurrent actors might write to the same file, branch, key, or state object. Eliminate the sharing first; serialize structurally only when one shared writer is a real invariant.
- ▌ Smahties · scaryrawr bundleUse the local smahties MCP server when users ask for semantic code search, conceptual codebase discovery, keyword or hybrid code search, indexing files/directories, checking index status, or listing indexed code units.
- ▌ Blogify · scaryrawr bundleUse this skill to turn a video or audio recording (a talk, meeting, or demo) into written content: documentation, a blog post, tutorial, changelog, or notes. Handles transcription, takeaway synthesis, screenshot/frame selection, and grounded drafting from local OpenAI-compatible media models. Not for real-time transcription, generic video editing, or non-generative media processing.
- ▌ How · scaryrawr bundleUse for "how does X work", code walkthroughs before changing something, and placement / ownership / layering questions ("where should this live", "which package owns this", "is this the right layer"). Explains subsystem architecture, runtime flow, onboarding mental models. Use why for motivation.
- ▌ Tdd · scaryrawrUse only when the user explicitly asks for TDD, a failing test, or a regression test, OR when the bug has an obvious cheap local test target. Skip when the test path is unclear, expensive, integration-heavy, or not requested.
- ▌ Why · scaryrawr bundleUse for 'why does X work this way', 'why we picked Y', design rationale, regressions, postmortems, or data-backed thresholds. Discovers available MCPs and queries each evidence category (source control, issue tracker, long-form docs, real-time chat, infrastructure observability, error tracking, product analytics warehouse) in parallel, then returns a cited read on decisions and tradeoffs. Use how for runtime behavior.
- ▌ Image Gen · scaryrawr bundleUse this skill to create, generate, draw, or edit images/photos into saved PNG files with OMLX image models. Covers text-to-image and image-to-image edits. Do not use for text-only image explanations, screenshot summaries, or non-generative image processing scripts.
- ▌ Arena · scaryrawrSpawn N parallel candidates at the same task, pick a base, graft the strongest parts of the losers into it. Use for /arena, 'arena this', 'throw it in the arena', or when one attempt at a non-trivial artifact would lock in the wrong shape.
- ▌ Swarm · scaryrawrFan out N parallel workers, drain them, and return one report. Use for /swarm, 'swarm this', or parallel coverage, races, gauntlets, and exploration.
- ▌ Teach · scaryrawrExplain a body of work plainly so a person actually understands it. Runs the `how` and `why` skills and weaves what they find into one clear explanation. Use for 'teach me this', 'help me really understand X', 'explain this change or subsystem to me'.
- ▌ Recall · scaryrawrReconstruct your recent working context from your own chat history, live state, and the shared record (user reports, prior fixes, incidents), then hand back a tight current-state brief. Use for 'recall my work on X', 'catch me up', 'what have I been working on', 'where did I leave off', before starting or resuming work.
- ▌ Reflect · scaryrawr bundleSpawn three parallel review subagents over the active transcript, surface learnings, and route each to a concrete edit on an existing skill. Use when the user says reflect.
- ▌ Better Init · scaryrawr bundleCreate or modify repository guidance through GitHub Copilot CLI, including guidance consumed by Copilot code review. Use when asked to initialize, bootstrap, refresh, reorganize, or generate AGENTS.md, Copilot instructions, path-specific instructions, project skills, code-review guidance, or custom agents. Do not use for requests that only read or explain existing guidance.
- ▌ Architect · scaryrawr bundleSketch types, signatures, and module structure before code, then stay in the loop while implementation fills in. Use for /architect, 'architect this', 'design this', or non-trivial work where jumping to code would lock in the wrong shape.
- ▌ Azure Devops · scaryrawr bundleUse for performing Azure DevOps work — create, inspect, review, comment on, vote on, or manage pull requests; find, query, create, update, and link Azure Boards work items (including building WIQL queries); parse and route dev.azure.com or *.visualstudio.com URLs; and upload PNG/image/file attachments to pull requests. Triggers on Azure DevOps / ADO / Azure Boards links or action requests such as "make an ADO PR", "review this Azure DevOps PR", or "find work items assigned to me". Not for general conceptual explanations that do not act on a specific Azure DevOps resource, and not for GitHub, Jira, or other non-Azure-DevOps tools.
- ▌ Digivolution · scaryrawr bundleUse for "digivolve", "use digivolution", adaptive end-of-turn reflection prompts, or requests that ask whether durable repo-specific guidance, AGENTS.md/Copilot instructions, or in-repo SKILL.md instructions are stale, missing, or should be updated.
- ▌ Automate Me · scaryrawrUse for "automate me", "create/update/refresh my -mode skill", "turn/capture my preferences or working style into a skill", or wanting agents to follow how the user works. Drafts or revises a personal -mode Agent Skill, optionally pulling evidence from recent sessions.
- ▌ Interrogate · scaryrawr bundleUse for "interrogate", "adversarial review", "multi-model review", "challenge this", "stress test this code", "find blind spots", or "tear this apart". Multiple LLM reviewers challenge changes from independent angles.
- ▌ No Comments · scaryrawrSpawn Comment Sicko, fix accepted findings, and offer encodings for claimed constraints.
- ▌ Poteto Mode · scaryrawr bundlepoteto's agent style for concise, detailed responses, deliberate subagents, unslopped prose, simple code, and verified work. Use for poteto, /poteto-mode, or requests to work in this style.
- ▌ Screen Record · scaryrawr bundleRecord agent-driven screen demos and edit video or audio with local FFmpeg. Use for screen recording or desktop capture while computer-use tools drive a workflow; trimming setup or dead time; putting videos side by side; adding captions or subtitles; generating local text-to-speech narration; or mixing and dubbing demo audio. Not for transcribing recordings, extracting documentation from meetings, or uploading and publishing media.
- ▌ Blast Radius · scaryrawrFind what a change could break somewhere else before it ships, beyond the diff, and prove the one fact it's safe because of by running real code instead of writing it up. Use for 'blast radius of X', 'what could this break', or reviewing a small diff you don't trust.
- ▌ Setup Pstack · scaryrawrConfigure which models pstack uses per role. Detect available Copilot Task models and write an always-applied user instruction in Copilot home. Use for /setup-pstack, "configure pstack models", or changing pstack's model choices.
- ▌ Ado Agent Merge · scaryrawr bundleDrive an Azure DevOps pull request from local changes through completion, including review threads, required policies, conflicts, safe auto-complete, and continued monitoring for new failures. Use when asked to "agent merge" an ADO PR, create an Azure DevOps PR and get it all the way through, or keep working and monitoring an ADO PR until it merges. Not for GitHub pull requests or status-only inspection.