All authors
Claude Skills by OutlineDriven
github.com/OutlineDriven865 skills3 installs846 views
- Oauth2 Flow ImplementationUse when asked to implement, debug, validate, or explain an OAuth 2.1 flow: auth code with PKCE, client credentials, device, or refresh. Also for a failing token exchange. Not for irreversible work.Votes: 0GitHub stars: 52
- ObservabilityUse when adding telemetry, composing an observability surface, reviewing alerts, shipping a production feature, or diagnosing a production issue. Not for live failures, profiling, or launch runbooks.Votes: 0GitHub stars: 52
- OffenseUse when a human says "overhaul", "rebuild this subsystem", or "rewrite it from scratch". Not for thin-slice features: use incremental-implementation. Not for root-cause repair: use strike-the-root.Votes: 0GitHub stars: 52
- OnboardUse when the user asks for onboarding, orientation, a repository tour, or where to start. Produces an evidence-backed seven-section map, deep-reads real files, and asks for the next move.Votes: 0GitHub stars: 52
- Open Source License SelectionUse when the user asks to choose, reconcile, or apply an open-source license and package metadata. Not for readiness auditing.Votes: 0GitHub stars: 52
- Open Source Readiness AuditUse when the user asks whether a repository is ready for public release or wants a gap assessment. Not for choosing or applying a license: use open-source-license-selection.Votes: 0GitHub stars: 52
- Optimise SeoUse when asked to make a Next.js App Router app crawlable, indexable, and search-optimized for sitemaps, robots, canonicals, and Core Web Vitals. Not for security headers or remote mutations.Votes: 0GitHub stars: 52
- OptimizeUse when asked to optimize code, reduce allocations, profile a target, or investigate a performance regression or measured bottleneck. Supports quick fixes, full or `extremely-optimize` measured-floor campaigns, `fastopt` hypothesis-only analysis, and `fastopt-extreme` complexity-neutral estimates. Not for remote, credential, publish, deploy, or irreversible changes.Votes: 0GitHub stars: 52
- Orchestration PatternsUse when work decomposes across subagents or role panels and needs coupling-based orchestration. Not for cloud-agent task-graph orchestration: use cloud-task-orchestrator.Votes: 0GitHub stars: 52
- Oss FuzzUse when enrolling a project in OSS-Fuzz, running its helper workflow locally, or reproducing an OSS-Fuzz report. Not for remote, credential, publish, deploy, or irreversible changes.Votes: 0GitHub stars: 52
- Paced ExplanationUse when asked to explain or teach a subsystem, module, pattern, or change in progressive layers from purpose to code depth. Not for design rationale: use why. Not for source or remote-system changes.Votes: 0GitHub stars: 52
- Parallel LaunchUse when work splits into independent sub-tasks or cross-domain research. Not for durable scope ownership with per-scope review: use partition-scopes-to-subagents.Votes: 0GitHub stars: 52
- Partition Scopes To SubagentsUse when asked to partition non-overlapping scopes across subagents and drive each to completion. Not for concurrent independent sub-tasks: use parallel-launch.Votes: 0GitHub stars: 52
- Perspective Complete ReviewUse when one named review viewpoint must run fix cycles until a fresh reviewer finds nothing. Not for multi-viewpoint review or remote, credential, publish, deploy, or irreversible changes.Votes: 0GitHub stars: 52
- Plan Review TuneUse when plan-mode enforcement hooks intercept a plan review or the user runs /plan-review-tune to tune which plan-review questions fire. Persists the tuned question flow to a local question-registry and hook configuration. Not for auditing a plan against code — use plan-review.Votes: 0GitHub stars: 52
- Plan ReviewUse when a plan path or text is supplied. Audits every item in the plan against the current codebase, including targetless decisions and assumptions, and produces an HTML accuracy verdict page. Not for tuning review questions, use plan-review-tune; not for scoring, use planning.Votes: 0GitHub stars: 52
- PlanUse when a user commits to a direction and asks to plan, brief, research, or operationalize it; or wants to enumerate designs, configurations, scenarios, and paths, audit a supplied plan, tune the review flow, or a plan-mode enforcement hook intercepts a plan review, or lock a greenfield architecture and interfaces. Modes: score, breakdown, shape, visual, storm (subject, dimensions, bounds), review (audit or tune), waterfall (brief, constraints, existing paths). Not for four-phase review: use...Votes: 0GitHub stars: 52
- Planning And Task BreakdownUse when multi-step work must be broken into dependency-ordered tasks before implementation begins. Gives every task a checkable acceptance criterion and a coherent size bound, then requires explicit user approval. Not for scoring a plan; use planning. Not for a committed-direction brief; use plan.Votes: 0GitHub stars: 52
- PlanningUse when a plan must be stress-tested, iteratively improved, and scored against a 5/5 quality bar across six dimensions. Drafts, scores with a deterministic rubric, and revises up to a fixed iteration limit. Not for a committed-direction brief; use plan. Not for task breakdown; use planning-and-task-breakdown.Votes: 0GitHub stars: 52
- Polished Web PrototypeUse when /polished-web-prototype runs or a user builds an artifact from a mockup, design plan, or brief. Not for variant galleries: use design-variants. Not for live audits: use web-design-review.Votes: 0GitHub stars: 52
- Port Static Analysis RuleUse when an existing static-analysis rule must be ported to another language or analyzer, producing an independently validated rule with vulnerable, safe, and edge-case parity tests. Use this for cross-language rule porting, not for authoring a new rule from a vulnerability description (use semgrep-rule-authoring) or for running scans (use semgrep-security-scan).Votes: 0GitHub stars: 52
- Possible Worlds QaUse when a product surface must be tested against extreme or hostile worlds. Not for design disputes: use possible-worlds. Not for remote, credential, publish, deploy, or irreversible changes.Votes: 0GitHub stars: 52
- Possible WorldsUse when a design dispute has at least two live interpretations and the caller wants worlds made explicit or a plain-language recommendation. Not for selecting a design or source/remote changes.Votes: 0GitHub stars: 52
- Post Change Check GateUse when an artifact or skill has just changed and is about to be called done, committed, or handed off. Not for remote, credential, publish, deploy, or irreversible changes.Votes: 0GitHub stars: 52
- Post Daily New IssuesUse when a human explicitly requests the daily on-call issue digest from a named issue tracker for a configured Slack channel. Not for posting without explicit human authorization for that run.Votes: 0GitHub stars: 52
- Post Merge CleanupUse when a landed merge, release, or completed change needs its cleanup surface reconciled. Scans for stale TODOs, deprecations, unused flags, and doc gaps. Not for unrelated refactoring.Votes: 0GitHub stars: 52
- Post Release StatusUse when a user asks to post, update, or check cherry-pick status for a release as a single Slack Block Kit board. Not for mutating pull requests or posting to multiple messages.Votes: 0GitHub stars: 52
- Post To SlackUse when the user explicitly asks to share a message on Slack through an incoming webhook. Not for posting without an explicit request or for retrying an ambiguous delivery.Votes: 0GitHub stars: 52
- Poteto ModeUse when asked to apply the pstack rigor mode to non-trivial work. Routes the task to a matched playbook from a 23-index and executes it to verified completion on the real surface. Not for remote, credential, publish, deploy, or irreversible changes.Votes: 0GitHub stars: 52
- PovUse when asked to judge whether to adopt, switch, reject, or revisit technology, library, pattern, or architecture, or a second opinion. Not for scoping: use brainstorm. Not for forks: use decide.Votes: 0GitHub stars: 52
- Pr Impact QuizUse when the user invokes this skill to generate targeted questions proving the author understands the change''s codebase effect. Not for reviewing the change: use review.Votes: 0GitHub stars: 52
- Pr Link IssueUse when a human explicitly asks to link a GitHub issue and Linear ticket to a pull request body. Appends one Issues block with the supplied references. Not for unlinking, searching for issues, or substituting missing identifiers.Votes: 0GitHub stars: 52
- Pr Review Canvas HtmlUse when asked to render a GitHub PR as a standalone review HTML page. Fetches PR data via gh API, renders diffs with move detection, and serves the artifact on a local port. Not for Cursor Canvas output — use pr-review-canvas.Votes: 0GitHub stars: 52
- Pr Review CanvasUse when asked to render a PR review as a Cursor Canvas artifact or a standalone HTML page served on localhost (mode: html), with risky hunks foregrounded.Votes: 0GitHub stars: 52
- Pr WalkthroughUse when a user asks for a zoomable PR map or graph-canvas orientation. Not for remote, credential, publish, deploy, or irreversible changes.Votes: 0GitHub stars: 52
- Prepare Repository For Public ReleaseUse when asked to prepare a repository for public launch or open source it. Not for remote, credential, publish, deploy, or irreversible changes.Votes: 0GitHub stars: 52
- Presentation CreatorUse when asked to create a presentation, pitch deck, or slides from a topic and audience, or to format supplied source items into a 16:9 HTML slide deck. Not for PowerPoint files.Votes: 0GitHub stars: 52
- Press Release WriterUse when a user asks to write or announce a press release for any occasion or region, adapting to release type and media format. Read-only. All output in chat.Votes: 0GitHub stars: 52
- Pricing ProjectionUse when projecting cost, estimating BYO cost or spend, or sizing a deal. Not for remote, credential, publish, deploy, or irreversible changes.Votes: 0GitHub stars: 52
- PrinciplesUse when a request names a working principle (subtract before you add, idempotent operations, never block on the human) or asks which principle applies. Not for running a repair: use strike-the-root.Votes: 0GitHub stars: 52
- PrismUse when one reviewer angle is insufficient or the user suspects a direction is tunnel-visioned or inherited its framing. Modes: artifact, direction. Not for source or remote-system changes.Votes: 0GitHub stars: 52
- Product DesignUse when deciding what an interface should do before UI is built or audited: consequences, action scope, reachable states, naming, and accessibility. Not for visual implementation: use prototype.Votes: 0GitHub stars: 52
- Product Signal PulseUse when invoking /product-signal-pulse with an optional lookback window to query configured product signals. Not for credential, publish, deploy, or irreversible changes.Votes: 0GitHub stars: 52
- Prohibit Bad HabitsUse when a user wants to define patterns the agent should not do. Don''t use for remote, credential, publish, deploy, or irreversible changes.Votes: 0GitHub stars: 52
- Project Findings Onto GraphUse when graph-backed security analysis is needed: project SARIF or reviewer findings onto a program graph; build or query a multi-language graph; summarize Trailmark structure; map smart-contract entry points; compare two refs or snapshots; or hunt confirmed vulnerability variants with pattern or graph seeding. Select findings, build-program-graph, trailmark-structural, entry-point-analyzer, graph-evolution, or variant-hunt mode and supply its required inputs. Not for security-finding triage...Votes: 0GitHub stars: 52
- Prompt OptimizerUse when asked to improve, optimize, rewrite, tune, or port a prompt, skill, or tool description. Also for building prompt evals or auditing prompt text for dated instructions.Votes: 0GitHub stars: 52
- Promql CliUse when asked to execute or investigate a PromQL expression against a Prometheus server. Read-only HTTP queries only. No source or remote-system changes.Votes: 0GitHub stars: 52
- Proof DrivenUse when property-based testing, theorem proving, or formal proof tactics require zero unproven properties. Not for remote, credential, publish, deploy, or irreversible changes.Votes: 0GitHub stars: 52
- Property Test AuthoringUse when authoring property tests, assessing PBT fit for a code path, reviewing existing property tests, or triaging a failing counterexample. Not for test-first features: use tdd.Votes: 0GitHub stars: 52
- Property Test Failure TriageUse when a generated or shrunk counterexample from a property-based test fails. Classifies whether the defect is in the implementation, the property statement, or the specification, and states the minimal repair action. Not for writing or reviewing tests.Votes: 0GitHub stars: 52