All authors
Claude Skills by mcorbett51090
github.com/mcorbett51090964 skills6 installs216 views
- Validate Realized SavingsMeasure realized savings against a finance-recognized baseline and locate leakage, so negotiated savings aren't mistaken for P&L impact. Reach for this on any savings claim.Votes: 0GitHub stars: 7
- Assumption MappingStructured playbook for surfacing and ranking the riskiest assumptions behind a product initiative, then designing the cheapest test for each — the core of continuous discovery before building.Votes: 0GitHub stars: 7
- Continuous DiscoveryRun continuous product discovery: weekly JTBD customer interviews, an opportunity-solution tree (outcome -> opportunities -> solutions -> experiments), assumption mapping with riskiest-assumption testing, and problem validation before solutioning.Votes: 0GitHub stars: 7
- PrioritizationPrioritize by evidence, not opinion: use a transparent framework (RICE = reach x impact x confidence / effort, or cost-of-delay, or opportunity scoring) to make trade-offs explicit and arguable, and frame everything around outcomes rather than outputs.Votes: 0GitHub stars: 7
- Product MetricsMeasure what matters: define a North Star metric that captures delivered value, decompose it into 3-5 movable input metrics, distinguish vanity (cumulative totals) from actionable (rates/cohorts/retention), set guardrails, and judge outcomes vs a baseline.Votes: 0GitHub stars: 7
- Rice PrioritizationWorked RICE scoring playbook for evidence-based backlog prioritization — covers calibrating each factor, avoiding common scoring errors, and using the output to run a defensible prioritization meeting.Votes: 0GitHub stars: 7
- Project Charter And BaselineStand up the predictive plan of record — a project charter (objective, success criteria, sponsor, high-level scope, assumptions/constraints), a scope statement + WBS decomposed to single-owner work packages, and the scope/schedule/cost baseline that change control is measured against. Reach for this at project initiation, a reset, or before any earned-value reporting. Used by `delivery-lead` (primary).Votes: 0GitHub stars: 7
- Raid FacilitationBuild or refresh a decision-grade RAID register — risks framed cause→event→consequence and scored against a stated rubric (qualitative probability×impact, quantified/EMV where the stakes justify it), each with a response and a single owner; plus issue triage, assumptions, and dependency tracking. Reach for this when a RAID stub needs to become a real register, a risk needs quantifying, or issues need triaging to action. Used by `risk-and-raid-analyst` (primary).Votes: 0GitHub stars: 7
- Sprint PlanningPlan a sprint from a backlog — set a single sprint goal, size the commitment to demonstrated capacity (not aspiration), attach acceptance criteria + a single owner to every committed item, and make carry-over explicit. Reach for this when a team is starting a sprint, replanning mid-flight, or diagnosing erratic velocity. Used by `scrum-master` (primary).Votes: 0GitHub stars: 7
- Stakeholder EngagementBuild and maintain a stakeholder register with power/interest mapping, design a tailored communications plan, prepare steering packs and executive status reports, and handle escalation memos — ensuring the right message reaches the right stakeholder at the right depth every cycle.Votes: 0GitHub stars: 7
- Status And Steering PackPackage delivery + risk data into audience-ready communication — a narrative-first status (RAG that explains itself and never contradicts the numbers), a steering-committee pack, and an escalation memo that is a decision request. Reach for this for recurring status, an exec/board update, or an escalation under pressure. Used by `stakeholder-comms-lead` (primary).Votes: 0GitHub stars: 7
- Context Window EngineeringDecide what actually goes in the context window — static instructions vs just-in-time retrieval vs conversation history vs tools — with a per-section token budget and lost-in-the-middle-aware ordering. Reach for this when the window is bloating, quality is dropping as context grows, cost/latency is climbing, or you're unsure what to keep vs compress. Pairs with prompt-pattern-selection.Votes: 0GitHub stars: 7
- Prompt Eval And RegressionBuild the eval/regression set that gates prompt changes — labeled input/expected pairs over the hard cases, a scoring method (exact / schema-valid / rubric / LLM-judge with its caveat), a pass threshold, a CI gate with the model pinned, and injection cases. Reach for this before shipping a prompt, when a tweak silently broke other cases, or to defend against prompt injection. Pairs with structured-output-design.Votes: 0GitHub stars: 7
- Prompt Pattern SelectionChoose the prompting pattern — zero-shot, few-shot, chain-of-thought, decomposition/chaining, role framing, or self-consistency — by tracing the task against reliability need and token/latency cost. Reach for this when a prompt is inconsistent, when you're about to add examples 'just in case', or when one prompt is quietly doing several jobs. Pairs with structured-output-design.Votes: 0GitHub stars: 7
- Structured Output DesignMake an LLM return reliably machine-parseable output — choose the enforcement mechanism (native JSON/schema mode, tool/function calling, constrained grammar, or prose+parser), define the schema, and build the parse/validate/repair path. Reach for this when output format drifts, when downstream code parses model output, or when 'return JSON' in prose keeps failing. Pairs with prompt-pattern-selection.Votes: 0GitHub stars: 7
- Age DelinquencyAge delinquency into buckets and weight collections by collectability, not the total. Reach for this on a delinquency or cash question.Votes: 0GitHub stars: 7
- Build NoiBuild the EGI-to-NOI bridge from gross potential rent and translate to value at a cap rate. Reach for this on an NOI or valuation question.Votes: 0GitHub stars: 7
- Diagnose Leasing FunnelDiagnose the leasing funnel step-by-step and split renewal-vs-acquisition need. Reach for this on a lease-up question.Votes: 0GitHub stars: 7
- Project OccupancyProject ending occupancy as a flow of move-ins, move-outs, and renewals against a target. Reach for this on an occupancy question.Votes: 0GitHub stars: 7
- Quantify Turn LossQuantify lost rent during unit turns and frame the work-order backlog as a retention risk. Reach for this on a turn or maintenance question.Votes: 0GitHub stars: 7
- Accessibility 508 And RecordsSection 508 / WCAG 2.x conformance lifecycle: gap assessment, automated and manual testing methodology, VPAT/ACR authoring using the ITIC template, remediation prioritization, and ongoing testing cadence. Covers FOIA / public-records request handling (intake, exemption analysis, redaction, response timelines) and plain-language compliance (Plain Writing Act, Federal Plain Language Guidelines).Votes: 0GitHub stars: 7
- Grants ManagementFederal and state grant lifecycle management: pre-award application (NOFO analysis, project narrative, budget, SF-424 family), post-award setup (Notice of Award review, restricted-fund structure), ongoing management (drawdowns, budget modifications, subrecipient monitoring, progress reporting), closeout, and single audit readiness under 2 CFR 200 (Uniform Guidance).Votes: 0GitHub stars: 7
- Public Procurement And RfpEnd-to-end public procurement and RFP/RFI response workflow: bid-no-bid scoring, compliance matrix construction, Section L/M mapping, technical and management volume drafting, past-performance selection and narrative, price volume structure, and post-submission debrief analysis. Covers federal (FAR Parts 12, 13, 15, 16) and SLED (cooperative purchasing, state procurement codes) procurement.Votes: 0GitHub stars: 7
- E2e AutomationWrite deterministic E2E/integration tests: target resilient role/test-id selectors, wait on conditions never fixed sleeps, isolate and clean up test data, and structure with page objects so a UI change updates one locator.Votes: 0GitHub stars: 7
- Flaky Test TriageStructured procedure for detecting, classifying, and eliminating flaky tests — covers quarantine mechanics, root-cause patterns (timing, state, network, ordering), and the fix or delete decision.Votes: 0GitHub stars: 7
- Test InfrastructureBuild trustworthy test infrastructure: factory-based isolated test data, ephemeral per-run environments + service virtualization, automated flaky-test detection/quarantine, parallel sharding, and coverage+mutation reporting in CI.Votes: 0GitHub stars: 7
- Test Pyramid AuditAudit procedure for diagnosing test pyramid shape — identifies ice-cream-cone suites, slow E2E over-reliance, and unit test gaps, then produces a concrete rebalancing plan.Votes: 0GitHub stars: 7
- Test Strategy DesignDesign a test strategy on the pyramid: map defect classes to the cheapest test level that catches them, prioritize by risk, use coverage as a floor and mutation testing as the quality truth, and decide what not to test.Votes: 0GitHub stars: 7
- Design And Transpile Quantum CircuitDesign a quantum circuit for a chosen algorithm and transpile it to a real device's topology and native gate set — qubits/gates/measurement, the VQE/QAOA/quantum-kernel ansatz, decomposition to native gates, routing to qubit connectivity with SWAP overhead, and the transpiled depth checked against the coherence budget so it stays shallow enough for NISQ. Also builds the hybrid quantum-classical optimizer loop for variational algorithms. Reach for this when the user asks 'build/transpile this ...Votes: 0GitHub stars: 7
- Select Error Mitigation And BenchmarkSelect NISQ error-mitigation techniques for a noisy circuit and benchmark the result honestly — zero-noise extrapolation, probabilistic error cancellation, measurement-error mitigation, dynamical decoupling (mitigation, NOT the error correction fault tolerance will provide), the shots for a target statistical error, and a benchmark against an exact/simulated reference with the residual bias/variance quantified. Reach for this when the user asks 'the results are noisy — can I trust them?', 'wh...Votes: 0GitHub stars: 7
- Triage Quantum Use CaseDecide whether a problem should use quantum computing at all — and if so, which paradigm, qubit modality, NISQ-vs-fault-tolerant placement, SDK/provider, and resource estimate — by traversing the quantum triage decision tree (classical-vs-quantum gate → paradigm → modality → NISQ-vs-FT → SDK/provider), returning a go/no-go verdict that defaults to 'classical wins today' unless a proven advantage, an in-regime problem size, and an affordable state-prep cost all hold. Reach for this when the us...Votes: 0GitHub stars: 7
- Adaptive Run ClassifierSubstrate-neutral pre-execution classifier contract. A single Haiku call emits a `run_config` JSON envelope that right-sizes cardinality knobs + per-phase model tier + reasoning level for multi-phase agentic workflows (the rc-deep-research loop is the first consumer). Workflows read the envelope; substrate adapters (Claude / Codex / Copilot) map tier labels to SKUs. Carved out behind `.ravenclaude/run-config.json` `enabled: false` so adoption is opt-in and rollback is one line.Votes: 0GitHub stars: 7
- Agent Dispatch EvaluatorUniversal pre-dispatch model right-sizer. A single Haiku 4.5 forced-tool call evaluates `{subagent_type, description, prompt_head}` at every Agent dispatch / Workflow `agent()` call / `thing-decide.py` seat dispatch and binds (downgrades AND upgrades) the model selection. Carved out behind `.ravenclaude/dispatch-config.json` `enabled: false` so adoption is opt-in and rollback is one line. Tribunal-seat verdicts are shadow forever for MVP (protects the v0.32.0 backbone-diversity invariant).Votes: 0GitHub stars: 7
- Agent Quality RubricScore and improve an agent file against a 6-dimension rubric — Mission clarity, Scope sharpness, Capability Grounding alignment, Output-Contract completeness, Escalation paths, Example scenarios. Each dimension scored 1-5 with anchors; includes a remediation template that turns a low score into an actionable PR. Reach for this skill when authoring a new agent, reviewing a PR that adds or modifies an agent, or running a periodic agent-bank audit. Used by `prompt-engineer` (primary) plus `archi...Votes: 0GitHub stars: 7
- Analog Closeness ScorecardRecompute the M/H/G/O/E/I/T/V weighted closeness score (and the observed-vs-inferred quality bar) for a product-analog comparison, reusing the exact formula from the 2026-08-14 analog-repos-gap-fill survey instead of hand-deriving the arithmetic each time. Use when scoring how close a candidate repo/product is to RavenClaude (or any similarly-shaped catalog+governance+ops comparison) on the eight-dimension rubric.Votes: 0GitHub stars: 7
- Audit Ci GatesFor any consumer project where a CI workflow is meant to *enforce* a property (lint, format, security scan, manifest validation, version pin, layout allow-list, etc.). When working on a CI file or adding a new check, run this skill — every gate must fail on a known-bad input AND pass on a known-good input. A gate that runs without gating, or gates the wrong thing, is invisible from inside a green CI dashboard. Also triggers on user phrases like "audit the CI", "verify the gates", "is this gat...Votes: 0GitHub stars: 7
- Authoring Org SkillsAuthors, validates and packages a claude.ai Organization Skill — the intake questions, the trigger and scope exercises, then lint, pack and verify against measured platform constraints. Reach for this when someone wants to publish a Skill to their organization, or when an upload was rejected and the reason is unclear.Votes: 0GitHub stars: 7
- Drafting Customer RepliesDrafts a reply to an inbound customer email, grounded in the account record and the published help-centre articles rather than in recall. Use when a customer emails about billing, a renewal or an outage, when a reply must cite current policy, or when a teammate asks for a first draft to edit.Votes: 0GitHub stars: 7
- Screening Vendor InvoicesScreens a supplier invoice against the purchase order and the approval matrix, flagging quantity, price and duplicate-payment discrepancies before the invoice reaches the approver. Use when an invoice arrives for a purchase order, when a payment run is being prepared, or when an approver asks why an invoice was held.Votes: 0GitHub stars: 7
- Skeleton<What it does, in one clause.> Use when <the concrete situation from your trigger list>, or when <a second situation>.Votes: 0GitHub stars: 7
- Branch ArchiveSafely retire a local branch by tagging its tip first, then deleting the branch. The sanctioned escape hatch from guard-destructive.sh's blanket `git branch -D` block — turns silent-loss-of-unmerged-work into a reversible, audit-logged operation. Use when an agent or maintainer wants to clean up old feature branches that represent abandoned approaches, stale plans, or superseded work.Votes: 0GitHub stars: 7
- Brand ExtractionPoint at a website home page and extract every logo variant plus the brand 'schema' (design tokens — colors, typography, radii) into a ready-to-apply brand kit, so HTML documents/reports you generate for that project match the brand. Use when the user says things like 'pull the logo and brand from this site', 'extract the brand schema from <url>', 'make my reports match <company>'s style', or 'grab the colors and fonts from this homepage'.Votes: 0GitHub stars: 7
- Cheap Lane DelegationRoute ONE well-defined job (single-file, tests, summary, mechanical refactor) off Claude via cheap-lane-delegate.sh (bounded, returns). Opt-in cheap_lane: advise|agent. NOT for quota-escape, host-switch, fresh window, or 'pass remaining work to Grok' → session-handoff.Votes: 0GitHub stars: 7
- Claude Code Parallel And ModesUse when choosing Claude Code CLI parallelism or modes — remapping informal "max parallel", picking plan mode / subagents / worktrees /batch / ultracode workflows / ultrathink /effort /compact, surviving parent context limits during fan-out (disk-first handoff), or writing operator prompt templates. Not for non-Claude coding tools (escalate ai-coding-model-guidance) and not for inventing a /max-parallel command.Votes: 0GitHub stars: 7
- Claude OrchestrateOne-off Claude orchestration — route this task through Claude's brain even when the host CLI is Copilot/GPT/Grok. The `orchestrator:` knob in comfort-posture.yaml sets the always-on default; this skill is for on-demand invocation.Votes: 0GitHub stars: 7
- Cleanup WorktreesRemove finished agent worktrees, prune their branches, and surface anything still in flight. Run at the end of a multi-agent session and weekly as hygiene.Votes: 0GitHub stars: 7
- Contribute FindingFor Claude sessions running in a consumer project (any project where ravenclaude-core is installed). Triggered when you discover a cross-domain finding worth contributing back to the RavenClaude marketplace — either spontaneously, or when the user says "contribute this," "save to RavenClaude," "this is worth keeping," or similar. Walks through the qualifying check, picks the right shape (lesson, best-practice, or both), and formats a copyable staging submission the user can drop into RavenCla...Votes: 0GitHub stars: 7
- Create PrOpen a pull request for the current branch using the project's standard template. Verifies the branch is green, summarizes the diff against main, and pushes only after the user confirms.Votes: 0GitHub stars: 7
- Cross Platform DeterminismFor any script that produces a file the repo COMMITS and CI DIFFS — generated HTML, lockfiles, JSON snapshots, fixture files, documentation rendered from source. The output must be byte-identical regardless of who regenerated it or on what OS. This skill catches the specific failure modes that turn a freshness gate into a paper tiger that fails forever — OS-dependent path separators, locale-dependent encodings, nondeterministic ordering, drifting timestamps. Triggers on phrases like "freshnes...Votes: 0GitHub stars: 7
- Decision ReviewRoute a yes/no decision through the command-review tribunal (the Thing) for a binding verdict instead of pausing the human. Use before asking the user any yes/no question, and in the post-PR decision review. The tribunal auto-decides rule/fact-derivable calls and defers genuine preferences (and irreversible/high-blast calls) back to the human.Votes: 0GitHub stars: 7