All authors
Claude Skills by OutlineDriven
github.com/OutlineDriven865 skills3 installs846 views
- Graph EvolutionUse when two refs or source snapshots need security-relevant structural comparison a line diff may miss; returns a GRAPH_EVOLUTION report classifying node, edge, entrypoint, and subgraph changes. Not for remote, credential, publish, deploy, or irreversible changes.Votes: 0GitHub stars: 52
- Grill With DocsUse when a repository decision needs an interview plus durable terminology and decision records. Not for remote, credential, publish, deploy, or irreversible changes.Votes: 0GitHub stars: 52
- Ground LatestUse when starting or scaffolding a codebase or service, migrating, refactoring, or picking language, framework, or dependency, or latest, LTS, or modern way. Not for remote or irreversible changes.Votes: 0GitHub stars: 52
- Guardrail Carve RunUse when guardrail-adjacent material (stealth, scraping, privacy, IP, policy, security) or mixed reversible/irreversible, sensitive work, or the user says "autobahn this". Not for carved risky work.Votes: 0GitHub stars: 52
- GuillotineUse when dead, duplicate, superseded, or generated residue must leave more than one artifact class of a repo or subsystem, preserving behavior. Not for one enumerated record set: use clean-clean-cut.Votes: 0GitHub stars: 52
- Gut SyncUse when a user resumes work and needs an orientation card without full human recall. Not for packaging context for another agent or session: use handoff. Never source or remote-system changes.Votes: 0GitHub stars: 52
- Handoff PromptUse when the user asks for a handoff, delegation, or clipboard-ready prompt for another agent: a standalone path-free prompt copied to the clipboard, confirmed by title. Not for session-snapshot briefs — use handoff; never remote, credential, publish, deploy, or irreversible.Votes: 0GitHub stars: 52
- HandoffUse when work reaches a session boundary or the user asks to hand off, delegate, or get a clipboard-ready prompt. Mode brief packages continuity; mode prompt builds the delegation prompt.Votes: 0GitHub stars: 52
- Harness Port GuideUse when the user asks to make the skills framework work in a new harness, IDE, or CLI. Not for remote, credential, publish, deploy, or irreversible changes.Votes: 0GitHub stars: 52
- Headed Browser TakeoverUse when the user asks to open or take over a visible browser session by hand, for example to solve a CAPTCHA or authenticate. Not for headless scraping or unattended automation.Votes: 0GitHub stars: 52
- History ForgetUse when the user asks to remove a session or note from recall, or to unforget or list exclusions. Not for remote, credential, publish, deploy, or irreversible changes.Votes: 0GitHub stars: 52
- History HealthUse when a user asks to audit what recall fed agents. Not for source or remote-system changes.Votes: 0GitHub stars: 52
- History NotesUse when the user says remember this or settles one durable fact. Not for remote, credential, publish, deploy, or irreversible changes.Votes: 0GitHub stars: 52
- History RecallUse when a user requests the reasoning behind one matched session by query or handle. Not for peer transfer: use history-sync. Not for store registration: use history-source-registry.Votes: 0GitHub stars: 52
- History Source RegistryUse when a coding-agent session store is added or its format drifts, to document its layout, roles, quirks. Not for recalling a session: use history-recall. Not for peer transfer: use history-sync.Votes: 0GitHub stars: 52
- History SyncUse when the user requests memory transfer to or from a named peer. Not for recalling a session: use history-recall. Not for store registration: use history-source-registry.Votes: 0GitHub stars: 52
- HowUse when the user asks "how does X work" and wants an architecture walkthrough of the code path or subsystem, including its gotchas. Don''t use for tasks that require source or remote-system changes.Votes: 0GitHub stars: 52
- Humaniseur FrUse when the user supplies French text that reads like AI output and asks to naturalize it. Not for English STE rewriting: use humanizer-en-asd-ste100.Votes: 0GitHub stars: 52
- Humanizer En Asd Ste100Use when asked to rewrite technical English for STE compliance, stripping ambiguity and AI-style patterns. Not for French de-AI-ification: use humaniseur-fr.Votes: 0GitHub stars: 52
- Humansense2systemUse when the user wants to compile taste and "this feels wrong" signals into machine-consumable tokens, rules, forbidden combinations, and examples. Not for remote or irreversible changes.Votes: 0GitHub stars: 52
- Idea SparkboxUse when the user asks to park ideas or inspiration for later. Not for code, backlog, or divergence-class cards, or remote, credential, publish, deploy, or irreversible changes.Votes: 0GitHub stars: 52
- IdeateUse when a human asks to brainstorm, asks what to build, requests ideas for a divergent subject, or invokes /ideate. Produces a grounded ideation artifact committed locally with adjudicated survivors and a reason for every rejection.Votes: 0GitHub stars: 52
- Implement SpecUse when a ticket DAG from a complete specification needs parallel execution into a green draft PR. Not for a settled ticket with no spec: use work. Not for ticket decomposition: use to-tickets.Votes: 0GitHub stars: 52
- Incremental ImplementationUse when implementing a multi-file change, building a feature from a breakdown, or writing a large amount of code. Not for a single settled ticket: use work.Votes: 0GitHub stars: 52
- Influence And NegotiationUse when an agreement-seeking interaction arises, including mid-conversation moments the model detects.Votes: 0GitHub stars: 52
- Infrastructure MentorUse when a user, especially a new hire, asks for mentoring, guidance, or explanation of infrastructure or engineering practices. Not for code changes.Votes: 0GitHub stars: 52
- InitsUse when onboarding to a repository, capturing costly conventions, constraints, or rationale, or improving AGENTS.md. Not for remote, credential, publish, deploy, or irreversible changes.Votes: 0GitHub stars: 52
- Insecure Default DiscoveryUse when the user asks to audit a file, subtree, or repository for fallback secrets, default credentials, fail-open controls, weak primitives, or permissive access. Not for exhaustive secret scanning.Votes: 0GitHub stars: 52
- Instruction Phrasing MicrotestUse when changing the wording of a rule in a skill, prompt template, or agent instruction where the change is meant to alter model output.Votes: 0GitHub stars: 52
- Instruction Understanding GateUse when a request is long, bundled, high-stakes, or has ambiguous referents. Verifies understanding before non-trivial work: restates, cross-checks context, proceeds silently, surfaces a surviving fork. Not for tiered scans — use clarify; not for interviews — use interview-me.Votes: 0GitHub stars: 52
- Intent ProposalUse when material arrives without a fully formed ask or the ask is thinner than the data suggests. Proposes the intent as a confirmation-ready proposal with a next-step sketch. Not for an interview — use interview-me.Votes: 0GitHub stars: 52
- Interactive Drop SelectorUse when the user explicitly asks to choose which issues or pull requests to close interactively. Don''t use for closing items without per-item selection and explicit approval.Votes: 0GitHub stars: 52
- InterrogateUse when asked to "interrogate" or run an adversarial multi-model review of a supplied code artifact. Not for tasks that require source or remote-system changes.Votes: 0GitHub stars: 52
- Interview MeUse when a user asks to define requirements or choose between options. A structured interview surfaces every unstated assumption one question at a time and produces a user-approved decision record before any file change. Not for intent-from-data — use intent-proposal.Votes: 0GitHub stars: 52
- Ios Build CleanupUse when the user wants a clean Xcode rebuild by deleting DerivedData and build artifacts. Do not use for diagnosing a specific build error: use ios-build-fix.Votes: 0GitHub stars: 52
- Ios Build FixUse when asked to run /ios-build-fix to fix a failing iOS build, regenerate an Xcode project from project.yml, or correct UI behavior. Not for a clean rebuild: use ios-build-cleanup.Votes: 0GitHub stars: 52
- Ios Device QaUse when the user runs /ios-device-qa to drive a real iPhone over USB through a debug-bridge daemon and return a device QA report with verified interactions. Do not use for remote, credential, publish, deploy, or irreversible changes.Votes: 0GitHub stars: 52
- Ios Visual ReviewUse when the user invokes /ios-visual-review to audit an iOS app''s visuals on a real device. Not for remote, credential, publish, deploy, or irreversible changes.Votes: 0GitHub stars: 52
- Isolate Work In WorktreeUse when a run needs its own branch and checkout to avoid collisions with concurrent work. Creates an isolated worktree, tracks a five-status lifecycle in a manifest, and removes only terminal worktrees. Not for feature-work isolation — use isolate-workspace-gate.Votes: 0GitHub stars: 52
- Isolate Workspace GateUse when asked to start feature work that needs isolation, or before executing an implementation plan. Creates an isolated git worktree with symlinked hooks, runs setup, and gates on a green baseline test suite. Not for loop-run worktree lifecycle — use isolate-work-in-worktree.Votes: 0GitHub stars: 52
- Issue IntakeUse when filing an approved task spec as a GitHub issue with a local archive and optional worktree implementer. Don''t use for spec drafting without human interrogation and redaction gates.Votes: 0GitHub stars: 52
- Issue NowUse when a human asks to compare one closed or stale tracker issue with current reality and mark it done or update it. Don''t use for bulk issue reconciliation or multi-issue sweeps.Votes: 0GitHub stars: 52
- Issue TriageUse when a human invokes triage on a new configured Slack issue report. Not for triaging reports from other channels or posting more than one verdict.Votes: 0GitHub stars: 52
- Keep Why Autostart ExamplesUse when skill or knowledge activation is unreliable, or setup reaches activation reliability. Not for remote, credential, publish, deploy, or irreversible changes.Votes: 0GitHub stars: 52
- Keep Why Continuous CaptureUse when a non-trivial change lands or is abandoned and its decision, rejected alternatives, and reason must be captured. Not for trivial or corrective changes: those belong in CHANGELOG.Votes: 0GitHub stars: 52
- Keep Why InterviewUse when departing knowledge must enter project topic files through a narration-first interview. Not for remote, credential, publish, deploy, or irreversible changes.Votes: 0GitHub stars: 52
- Keep Why MaintenanceUse when contradictions, revisit conditions, or duplicates appear in knowledge entries. Not for remote, credential, publish, deploy, or irreversible changes.Votes: 0GitHub stars: 52
- Keep Why Repo StructureUse when project documentation needs a layout or a knowledge item needs one home. Not for remote, credential, publish, deploy, or irreversible changes.Votes: 0GitHub stars: 52
- Keep Why Repo Trust BoundaryUse when repo content crosses into working context or synthesized knowledge. Flags injections and blocks derived instructions. Not for tasks requiring source or remote-system changes.Votes: 0GitHub stars: 52
- Keep Why RetrospectiveUse when an existing repository needs its unexplained rationale recovered into topic files. Don''t use for remote, credential, publish, deploy, or irreversible changes.Votes: 0GitHub stars: 52