All authors
Claude Skills by mcorbett51090
github.com/mcorbett51090964 skills6 installs216 views
- Community Health ReviewDiagnose a developer community by the metrics that matter — answered-question rate, time-to-first-response, returning contributors, and sentiment — not member or follower count. Use to assess a forum/Discord/Discussions/Stack Overflow presence and design ops that fix unanswered questions.Votes: 0GitHub stars: 7
- Conference Talk And CfpShape a conference talk and write a CFP abstract that gets accepted and lands — lead with the attendee takeaway (what they can DO afterward), state concrete takeaways, match the track, and keep it engineer-to-engineer not a product pitch. Use when proposing or preparing a developer-conference talk.Votes: 0GitHub stars: 7
- Devrel Content StrategyChoose content formats and a calendar for an activation goal — format follows the goal (getting-started for first success, sample app for the value path, guide for a concept, talk for reach), not the trendy channel. Use when planning DevRel content tied to the activation funnel.Votes: 0GitHub stars: 7
- Getting Started AuditMeasure and shorten time-to-first-success — walk the getting-started path from a clean state, time it, rank friction points by where developers drop off, and make a fix-or-document call on each. Use whenever you need to know how good (or bad) onboarding really is.Votes: 0GitHub stars: 7
- Sample App DesignSpec a sample app or SDK quickstart that demonstrates the real value path as production-grade, runnable code — it runs from a clean checkout, handles errors, pins versions, and has no hardcoded secrets. Use when designing or reviewing sample code that developers will copy verbatim.Votes: 0GitHub stars: 7
- Choose Monorepo ToolingPick the right monorepo/build tool and package manager for a described repo by traversing the monorepo-tooling decision tree (language mix → scale → hermeticity need → tool), then return the recommended tool, the package-manager pick, the tradeoffs, and an explicit list of what NOT to adopt yet. Reach for this when the user asks 'which monorepo tool?' or 'should we adopt Nx/Turborepo/Bazel?'. Used by `build-systems-architect` (primary).Votes: 0GitHub stars: 7
- Manage DependenciesSet and enforce dependency & package management across a monorepo: version policy (single-version vs independent), lockfile hygiene (commit + freeze in CI), automated batched upgrades (renovate/dependabot), supply-chain hygiene (SBOM, provenance/SLSA, digest pinning), and staged cross-repo upgrades. Reach for this when the user asks 'how do we manage versions/lockfiles?' or 'upgrade X safely across the monorepo'. Used by `monorepo-engineer` (primary).Votes: 0GitHub stars: 7
- Optimize Build And CacheDiagnose and fix a slow build by measuring the task graph and cache-hit rate, auditing cache CORRECTNESS (input-hash completeness, hermeticity leaks) before any speed tuning, then applying the highest-leverage fix (affected-only, remote cache, parallelism, splitting the long pole). Reach for this when the user says 'the build is slow' or 'is remote caching worth it / even correct?'. Used by `build-systems-architect` (primary).Votes: 0GitHub stars: 7
- Ci Pipeline DesignDesign a fast, deterministic CI pipeline: stage ordering by cost, dependency/build caching keyed on the lockfile, build matrices and test sharding, required-check contracts for branch protection, and SHA-pinned third-party actions.Votes: 0GitHub stars: 7
- Gitops DeliveryStand up GitOps continuous delivery with Argo CD or Flux: desired-state-in-Git repo structure (app-of-apps, environment overlays), promotion-by-PR, drift detection/self-heal posture, and secrets without plaintext.Votes: 0GitHub stars: 7
- Progressive DeliveryChoose and wire a progressive-delivery strategy — blue-green, canary, rolling, or feature-flagged — by blast radius and reversibility, with a health-gated promotion and an automated, rehearsed rollback.Votes: 0GitHub stars: 7
- Secrets Rotation And ManagementPlaybook for managing secrets across the CI/CD pipeline — vaulting, injection at runtime, automated rotation, and the emergency response procedure when a secret is compromised — so long-lived credentials never live in pipeline definitions, env files, or Git.Votes: 0GitHub stars: 7
- Supply Chain IntegrityProduce trustworthy artifacts: reproducible/deterministic builds, minimal non-root container images, SemVer + immutable digests, build-time SBOM (CycloneDX/SPDX), and SLSA provenance + signing for verifiable supply-chain integrity.Votes: 0GitHub stars: 7
- Choose Digital Twin ArchitectureScope and architect a digital twin for a described asset and decision by traversing the digital-twin architecture decision tree (decision it informs → twin type → shadow-vs-bidirectional → descriptive/predictive/prescriptive → modeling approach → fidelity → sync → platform), then return the twin scope/type, the fidelity level (only as much as the decision needs), the modeling approach (physics vs data-driven/surrogate/reduced-order vs hybrid), the platform (DTDL+Azure Digital Twins / AAS / Ec...Votes: 0GitHub stars: 7
- Design Twin Data And Sync ModelFrom a physical asset and its telemetry, derive the twin's data and synchronization model — the signal list and sampling rates, the transport protocol (MQTT / OPC-UA / Kafka), the edge-vs-cloud split, the sync-latency budget the decision tolerates, the binding of each signal to the twin's model properties (DTDL properties / AAS submodel elements), and the drift-detection + recalibration policy. Reach for this when the user asks "what data does this twin need and how often?", "map our sensor s...Votes: 0GitHub stars: 7
- Implement Twin Integration And SimulationBuild a digital twin end to end — ingest the telemetry (MQTT / OPC-UA / Kafka, edge-vs-cloud) and bind it to the model (DTDL properties / AAS submodels), wire the physics or reduced-order/surrogate model, run simulation and what-if scenarios against live twin state, stand up 3D or dashboard visualization where it earns its keep, and — the step teams skip — validate fidelity against the real asset (predicted-vs-actual SLIs, error bounds, calibration) plus a drift monitor. Reach for this when t...Votes: 0GitHub stars: 7
- Build The Retention EngineRead cohort retention and the repeat rate and build the second-purchase engine, since retention compounds LTV. Reach for this when growth depends on acquisition alone.Votes: 0GitHub stars: 7
- Cost The ReturnsRead return rate and its full cost as a contribution-margin line, so a high-return category isn't mistaken for a winner. Reach for this on a margin question.Votes: 0GitHub stars: 7
- Diagnose The FunnelLocate a conversion problem by funnel stage — traffic, product page, cart, checkout — instead of reading the headline rate. Reach for this when conversion is low.Votes: 0GitHub stars: 7
- Manage Cac By ChannelRead CAC by channel and cohort and allocate budget to efficiency, instead of a blended number. Reach for this when CAC climbs.Votes: 0GitHub stars: 7
- Read Ltv CacRead LTV:CAC against the 3:1 line and contribution margin after the real costs, so a profitability problem is diagnosed correctly. Reach for this on any growth/profit question.Votes: 0GitHub stars: 7
- Adoption Sequencing K12Sequence K-12 partner adoption activities by stage (newly-implemented / first-year-sustaining / multi-year-mature / pre-renewal) with school-year-phase overlay. Surface-by-surface rhythm (teacher / admin / student / family-facing). Diagnostic-before-intervention discipline — don't push feature-breadth in stage 1. Used by `learning-analytics-analyst` + `success-playbook-designer`.Votes: 0GitHub stars: 7
- Advocacy Program DesignDesign a structured EdTech advocacy program with 5-tier ladder (logo → quote → case study → speaker → peer call). Health-score eligibility gate (top-quartile only), 2-asks-per-year ceiling, state-by-state anonymization overlay (CA/NY/IL stricter; TX/FL more permissive), FERPA consent for student/parent quotes. Used by `success-playbook-designer` + `ferpa-comms-translator` + `edtech-partner-success-manager`.Votes: 0GitHub stars: 7
- Cs Platform IntegrationThe back-end integration contract for a centralized EdTech customer success dashboard sitting on top of Planhat (CS platform) + Salesforce (CRM) + Snowflake (warehouse / product usage) + Zapier (glue) + Granola (AI meeting notes, stubbed). Documents what each system contributes to the dashboard's `bi-report/data.json` shape, the sync-freshness thresholds that drive the source-freshness banner, the identity spine that joins records across systems, and the Granola-into-Planhat flow (currently a...Votes: 0GitHub stars: 7
- Daily Action QueueCompute "today's top N accounts" for a K-12 EdTech PSM as a ranked list with next-best-action + confidence + rationale. Weighted-signal formula (lifecycle-aware), with RICE / ICE as alternate framings. Every action carries an explicit rationale string naming the dominant signal + the threshold crossed + the prescribed play. Designed so the PSM can answer "why this account today?" in one sentence.Votes: 0GitHub stars: 7
- Executive Sponsor MappingMap the partner's buying committee — economic buyer, champion, technical buyer / IT, user-champion, blocker, executive sponsor — across segments (K-12 / higher-ed / corp L&D). Includes the multi-thread coverage gap visualization, the "ghost sponsor" detection pattern, sponsor-change protocols, and integration with the durable partner profile. Reach for this skill on a new-partner kick-off, before a renewal, when a critical contact leaves, or when QBRs are well-attended but decisions aren't ha...Votes: 0GitHub stars: 7
- Expansion Play DesignDesign expansion motions that fire only when the partner has earned value — 3-gate eligibility (top-quartile health + demonstrable adoption + organizational readiness), value-trigger taxonomy, seat / module / department land-and-expand patterns, internal-champion-armament, ROI-storytelling format, and the "don't sell to bottom-quartile" discipline. Segment overlays for K-12 / higher-ed / corp L&D. Reach for this skill when designing the firm's expansion playbook or when the partner-success le...Votes: 0GitHub stars: 7
- Ferpa Comms TranslationReshape a partner communication into a FERPA-safe, audience-appropriate message — classify the data bucket, screen the small-cohort residual, reshape per audience, treat each language as a redesign. Used by ferpa-comms-translator and by any PSM drafting parent/admin/leadership copy. NOT advocacy quotes (that's advocacy-program-design) and NOT a legal opinion.Votes: 0GitHub stars: 7
- Health Report DashboardBuild a self-contained, Power-BI/Tableau-style HTML portfolio report from partner-health data — KPI cards (NRR/GRR/avg-health/red-count/renewal-risk), a health-band donut, a 12-week trend line, a peer-cohort range chart, score-component drill-downs, red-flag surfacing, and a sortable/filterable per-partner table. Used by `learning-analytics-analyst` (primary) + `edtech-partner-success-manager`. Ships with a ready-to-open demo (sample data) AND regenerates from real data — replace `bi-report/d...Votes: 0GitHub stars: 7
- Implementation 90 Day ArcRun the 90-day technical-onboarding arc for a newly-contracted EdTech partner — discovery (weeks 1-2) → integration setup (3-4) → train-the-trainer (5-6) → go-live + Day-30 measurement (7-8) → stabilization + PSM handoff (9-12). Calendar-dead-zone go-live check is the highest-leverage pre-flight. Used by `edtech-partner-success-manager` + `learning-analytics-analyst`.Votes: 0GitHub stars: 7
- Partner Health ScoringDesign and maintain a partner health score that actually predicts renewal / churn for EdTech partners. Signal selection, weighting, half-life / decay, red-flag triggers, and threshold-to-play mapping. Reach for this skill when designing a new score, refreshing one that's stopped predicting outcomes, or interpreting a score move.Votes: 0GitHub stars: 7
- Partner Training Program DesignDesign partner-facing training programs for EdTech — train-the-trainer is the only model that scales in K-12. K-12 PD modality decision rule (live-in-person / live-virtual / hybrid / async-with-followup), PD-credit alignment with state frameworks, teacher-union overlay in unionized states. Used by `ravenclaude-core/documentarian` + `edtech-partner-success-manager` + `success-playbook-designer`.Votes: 0GitHub stars: 7
- Psm Dashboard BuildCodex's master roadmap for executing the Partner Success Command Center build. Invoke FIRST when asked to build any tier of the PSM dashboard. Identifies which tier to execute, names the read-list, codifies the anti-pattern catalog from /tmp/research-codex-failure-modes.md, and provides the wall-handling + verification rituals.Votes: 0GitHub stars: 7
- Qbr CompositionCompose a Quarterly Business Review end-to-end — data pull plan, narrative arc, deck outline, talk track, post-QBR commitment tracker. Reach for this skill 1–2 weeks before a QBR is scheduled, OR after a QBR to convert in-meeting promises into a tracked plan.Votes: 0GitHub stars: 7
- Recovery Play DesignDesign red-flag intervention sequences — root-cause diagnostic before remedy (4 parallel hypotheses), time-bound recovery plan with measurable 30/60/90-day signal targets, escalation criteria (PSM → success leadership → exec sponsor → counsel → churn-prep), the "is this recoverable?" rule, churn-prep workflow when not, and the post-recovery learning capture. Reach for this skill when a partner trips red on the health score, when a renewal is at clear risk, or when a partner has signaled dissa...Votes: 0GitHub stars: 7
- Renewal Play DesignDesign renewal motions that earn the renewal instead of negotiating it — T-180/T-120/T-90/T-60/T-30/T-0 sequence, sponsor-confirmation arc, value-evidence pack, multi-thread the buying committee, decision-memo support, expand/maintain/contract decision rule, and segment-specific overlays (K-12 budget cycle, higher-ed academic calendar, corp L&D fiscal year). Reach for this skill 120-90 days before a renewal date, when a renewal "should be safe" but no movement has happened, or when designing ...Votes: 0GitHub stars: 7
- Rostering Data QualityDiagnose rostering / SIS / LMS data-sync issues in EdTech contexts — K-12 (Clever, ClassLink, OneRoster), higher-ed (SIS/LMS), corporate L&D (HRIS/LMS). When to escalate to product vs coach the partner's admin. Reach for this skill when a partner says "the data isn't right" or when partner-engagement metrics drop without an obvious user-side cause.Votes: 0GitHub stars: 7
- Success Plan AuthoringAuthor a 30/60/90 day or quarterly success plan for an EdTech partner that has measurable success criteria, named owners, and a defensible cadence. Reach for this skill when onboarding a new partner OR when refreshing a quarterly plan after a renewal / midyear review.Votes: 0GitHub stars: 7
- Bounce Complaint SuppressionClose the email feedback loop — classify hard vs soft bounces and spam complaints, enforce a suppression check before every send, and reconcile the ESP's suppression list with your own so you never re-send to a bad address. Reach for this when the user says "we keep emailing bounced addresses", "handle complaints", or "build a suppression list". Used by `email-sending-engineer` (primary).Votes: 0GitHub stars: 7
- Deliverability AuditDiagnose why mail is landing in spam (or pre-flight a domain before a big send) by traversing the deliverability triage tree — authentication, DMARC alignment, reputation/warm-up, list hygiene, content, and bulk-sender compliance — then return the specific failing layer, the fix, and how to confirm it from postmaster/RUA signals. Reach for this when the user says "why are we going to spam?", "audit our deliverability", or "are we Gmail/Yahoo compliant?". Used by `email-deliverability-architec...Votes: 0GitHub stars: 7
- Email Authentication SetupStand up SPF, DKIM, and DMARC (and optionally BIMI) for a sending domain and reach enforcement safely. Traverse the authentication decision tree (authenticate -> align -> enforce), emit the exact DNS records, and stage a p=none -> quarantine -> reject rollout gated on aggregate-report evidence. Reach for this when the user says "set up SPF/DKIM/DMARC", "get to DMARC enforcement", or "pass Gmail's sender rules". Used by `email-deliverability-architect` (primary).Votes: 0GitHub stars: 7
- Email Template EngineeringBuild responsive HTML email templates that render across clients (Outlook/Word engine, Gmail clipping, Apple Mail dark mode) using MJML or table-based HTML, with a plain-text part, accessible markup, and the client-quirk guards. Reach for this when the user says "build a <type> email", "my email looks broken in Outlook", or "make this email responsive / dark-mode safe". Used by `email-sending-engineer` (primary).Votes: 0GitHub stars: 7
- Transactional Email IntegrationIntegrate an Email Service Provider (SES, SendGrid, Postmark, Resend, Mailgun) for transactional sending with idempotent sends, signature-verified and idempotent webhook event handling (delivered/bounce/complaint/open), and retry/rate-limit discipline. Reach for this when the user says "wire up <ESP>", "send receipts/password resets", or "handle delivery webhooks". Used by `email-sending-engineer` (primary).Votes: 0GitHub stars: 7
- Budget MemoryTrack flash and RAM (image, static, worst-case stack/heap) against the part's limits. Reach for this on any memory or footprint question.Votes: 0GitHub stars: 7
- Build Power BudgetBuild the duty-cycled current profile and compute average current and battery life. Reach for this on any battery-life or energy question.Votes: 0GitHub stars: 7
- Plan OtaDesign a dual-bank OTA scheme with signed images and automatic rollback before fielding. Reach for this before any device ships.Votes: 0GitHub stars: 7
- Select ProtocolSelect the radio on the power/range/bandwidth/cost trade — don't default to Wi-Fi. Reach for this on a connectivity question.Votes: 0GitHub stars: 7
- Verify Real TimeCharacterize WCET and ISR latency and verify the schedule holds under worst case. Reach for this on any timing or determinism question.Votes: 0GitHub stars: 7
- Decide Tech DebtDecide whether to pay down a specific tech-debt by sizing its carrying cost and payback against the roadmap — not all-or-nothing. Reach for this before a 'we must stop and refactor' or 'we never have time' reflex.Votes: 0GitHub stars: 7
- Design Hiring LoopDesign a structured hiring loop — rubric, consistent questions, evidence-based scoring, a debrief that surfaces dissent — over a vibe-based one. Reach for this before scheduling interviews.Votes: 0GitHub stars: 7