All authors
Claude Skills by mcorbett51090
github.com/mcorbett51090964 skills6 installs216 views
- Publish Digital Collections And AccessPublish a collection online, rights- and cultural-sensitivity-cleared — run the copyright/rights gate and the source-community consultation, decide open-access vs restricted (CC0/CC-BY vs a rights-restricted license, with rights statements), and stand up the IIIF image/presentation stack + DAMS + online catalog + virtual exhibitions, defaulting toward openness where rights allow while cultural sensitivity gates the publish button. Reach for this when the user asks "publish our collection onli...Votes: 0GitHub stars: 7
- Design Network TopologyDesign a campus/datacenter/branch/WAN network topology by traversing the topology decision tree (scale -> traffic pattern -> redundancy need -> topology), then return the recommended topology (collapsed-core vs 3-tier vs spine-leaf vs hub-and-spoke/SD-WAN), an IP addressing plan (summarizable, room to grow), the redundancy/failure model (HSRP/VRRP, dual-homing, MLAG), and a labelled diagram description. Reach for this when the user asks to "design the network for <site/DC>". Used by `network-...Votes: 0GitHub stars: 7
- Design Segmentation And Zero TrustDesign network segmentation and a zero-trust network access posture by traversing the segmentation decision tree (what to isolate -> blast radius -> enforcement point -> identity model), then return the segment plan (VLANs/VRFs/microsegmentation), the east-west + north-south policy model, the NAC/802.1X posture, and the SASE/SD-WAN or firewall enforcement point. Reach for this when the user asks "how do we segment <IoT/OT/guest/PCI> off the network?". Used by `network-architect` (primary); se...Votes: 0GitHub stars: 7
- Plan Network ChangeTurn a network change (routing/VLAN/firewall/cutover) into a staged, reversible plan — blast-radius assessment, change window, pre-checks (baseline), the staged steps with verification gates, and a tested rollback — so no change is a big-bang gamble. Reach for this when the user needs to make a risky network change safely or migrate/cut over network infrastructure. Used by `network-operations-engineer` and `network-architect`.Votes: 0GitHub stars: 7
- Select Routing ProtocolChoose the right routing protocol (static, OSPF, EIGRP, IS-IS, BGP) for a given boundary and scale by traversing the routing-protocol decision tree (administrative boundary -> scale -> multi-vendor -> convergence/policy need), then return the recommendation, the design knobs (OSPF areas, BGP ASNs/route-reflectors/communities, summarization), and why the alternatives were ruled out. Reach for this when the user asks "OSPF vs BGP vs static between <X>?". Used by `network-architect` (primary).Votes: 0GitHub stars: 7
- Troubleshoot ConnectivityIsolate a network connectivity fault methodically, bottom-up the OSI stack (L1 link -> L2 VLAN/ARP/MAC -> L3 routing/ACL -> L4 port/firewall -> L7 DNS/app), naming the specific isolating test and confirming command at each layer, then return the ranked most-likely fault and how to confirm it. Reach for this when the user says "X can't reach Y" or reports intermittent/slow connectivity. Used by `network-operations-engineer` (primary).Votes: 0GitHub stars: 7
- Grant Postaward ComplianceManage a grant AFTER the award — set up, spend only on allowable/allocable/reasonable costs, track budget-vs-actual monthly, report on cadence, stay audit-ready through close-out. Reach for this once a grant is won (the post-award/compliance side; the pre-award qualify→write side is qualify-the-funder).Votes: 0GitHub stars: 7
- Protect Donor RetentionRead donor retention by cohort and fix the leaky bucket before pouring in acquisition, since retention is ~7x cheaper than acquisition. Reach for this on any growth question.Votes: 0GitHub stars: 7
- Qualify The FunderScore a grant opportunity on funder fit before writing, so effort goes where alignment is. Reach for this before any proposal.Votes: 0GitHub stars: 7
- Read Cost Per DollarCompute cost-to-raise-a-dollar per channel, never blended, so the subsidizing channel is visible. Reach for this on a portfolio/efficiency question.Votes: 0GitHub stars: 7
- Run The Cultivation CycleMove a donor through identification, qualification, cultivation, solicitation, and stewardship rather than jumping to the ask. Reach for this on a major-gift prospect.Votes: 0GitHub stars: 7
- Segment The Donor BaseSegment donors by value, recency, and engagement (RFM-style) to direct cultivation hours where they pay. Reach for this when cultivation is spread thin.Votes: 0GitHub stars: 7
- Alerting Rule DesignPlaybook for writing alerts that page on user-visible symptoms using multi-window multi-burn-rate rules — covering threshold selection, alert fatigue reduction, and runbook requirements.Votes: 0GitHub stars: 7
- Chaos EngineeringVerify resilience proactively with chaos experiments — a steady-state hypothesis, a controlled fault injection, a blast-radius limit, and a game day — instead of waiting for the real outage. Reach for this to prove (not assume) a system tolerates failure.Votes: 0GitHub stars: 7
- Incident ResponseRun an incident and learn from it: declare + classify severity, split IC/comms/ops roles, communicate on a cadence, mitigate before root-causing, and write a blameless postmortem with owned, dated action items.Votes: 0GitHub stars: 7
- Opentelemetry InstrumentationInstrument a service with OpenTelemetry: OTLP export, semantic conventions, the key spans and metrics, a sampling strategy (head vs tail), cardinality control, and trace/log correlation via propagated context.Votes: 0GitHub stars: 7
- Postmortem FacilitationBlameless postmortem facilitation guide — timeline reconstruction, five-whys causal analysis, contributing factor classification, and action item extraction with owners and due dates.Votes: 0GitHub stars: 7
- Slo And Error BudgetsDesign SLIs/SLOs and an error-budget policy: pick user-centric indicators, set targets by user need (not 100%), define the ship-vs-freeze budget rule, and enforce with multi-window multi-burn-rate alerts.Votes: 0GitHub stars: 7
- Slo Definition WorkshopGuided workshop playbook for defining SLIs and SLOs with engineering and product — produces a complete SLO document with error budget, burn-rate alert thresholds, and a budget policy.Votes: 0GitHub stars: 7
- Choose An Open Source LicenseRecommend an open-source license for a project from its intent (permissive adoption vs reciprocal sharing), its dependency-license graph (the strongest copyleft constrains the whole), and its contribution-agreement need (CLA vs DCO vs neither). Returns a license recommendation, the LICENSE/NOTICE files to add, and the contribution posture. Used by `oss-maintainer-strategist` (primary).Votes: 0GitHub stars: 7
- Coordinate A Security ReleaseRun a coordinated security release for a privately-reported vulnerability — private fix branch, GHSA/CVE assignment, patched versions on every supported line, an advisory, and disclosure timing. Returns the coordinated-release runbook and the advisory skeleton. The vulnerability ANALYSIS routes to security-engineering; this skill owns the release choreography. Shared by both agents.Votes: 0GitHub stars: 7
- Manage Breaking Changes And DeprecationsShip a breaking change without stranding users — run a deprecation lifecycle (warn -> window -> remove), author a migration guide, and pair the removal with a major bump and a BREAKING changelog note. Returns the deprecation plan, the migration guide skeleton, and the support-window statement. Used by `release-and-versioning-engineer` (primary).Votes: 0GitHub stars: 7
- Plan A ReleasePlan a release end to end — decide the semver bump from the change set, assemble a human-readable changelog (Keep a Changelog groups), and run a release checklist (tests green, version bumped, tag signed, artifact + provenance, advisory if needed). Returns the version, the changelog entry, and the release runbook. Used by `release-and-versioning-engineer` (primary).Votes: 0GitHub stars: 7
- Triage Issues And PrsTurn an unbounded issue/PR backlog into a tractable system — a label taxonomy, SLA tiers, a reproduction gate for bugs, a stale policy, and a graceful decline path. Returns a TRIAGE policy, issue/PR templates, and label definitions. Prevents the silent-backlog burnout the project exists to avoid. Used by `oss-maintainer-strategist` (primary).Votes: 0GitHub stars: 7
- Eligibility And ClaimsRun the eye-care claims loop: verify both medical and vision eligibility before the visit, manage payor mix, and triage denials by cause (eligibility, coding/medical-necessity, wrong-payor-routed, timely-filing). Payor specifics are verify-at-use.Votes: 0GitHub stars: 7
- Exam Flow And PretestingEngineer the exam lane: pretesting/workup done by a tech before the doctor enters, a workup-to-doctor handoff that protects chair time, and a tech-to-doctor ratio that lets one doctor run multiple lanes. Protect the scarcest resource — the doctor's chair.Votes: 0GitHub stars: 7
- Medical Vs Vision BillingRoute an eye-care visit to medical insurance vs the vision plan deliberately, on the chief complaint and what the visit addressed. Code to the encounter, document medical necessity for medical claims, and flag every payor/coding specific verify-at-use.Votes: 0GitHub stars: 7
- Optical Capture And DispensaryRun the optical for profit: track and lift the capture rate (eyes examined -> Rx written -> Rx filled in your optical), run the frame board on inventory turns, manage the lab pipeline, and dispense within managed-vision-care formularies knowingly.Votes: 0GitHub stars: 7
- Schedule And Recall ManagementBuild the eye-care schedule off recall: set recall/recare intervals by exam type, template exam-length to exam-type, and read capacity as lanes x exam length x fill rate. Recall, not walk-ins, is the primary schedule-filler.Votes: 0GitHub stars: 7
- Build A Partner Tiering ModelDesign partner tiers that trade concrete obligations (certs, pipeline, capacity) for concrete benefits (margin, MDF, leads) — not a logo wall. Reach for this when standing up or fixing a partner program.Votes: 0GitHub stars: 7
- Design An Mdf ProgramDesign market-development funds as a measured investment tied to a plan and an ROI floor — not a channel rebate nobody tracks. Reach for this when standing up or fixing MDF/co-op funds.Votes: 0GitHub stars: 7
- Size Partner Sourced PipelineSize partner-sourced vs partner-influenced pipeline with a defined attribution rule, so the program number is one finance trusts and nothing is double-counted with direct. Reach for this before any partner-revenue claim.Votes: 0GitHub stars: 7
- Structure A Co Sell MotionBuild a co-sell motion around a named rep-to-rep play — mapped account overlap, a joint value proposition, and a shared incentive — not a 'we'll co-sell' press release. Reach for this when activating an alliance.Votes: 0GitHub stars: 7
- Craft Candidate MaterialsCraft honest candidate materials — resume, LinkedIn Experience, LinkedIn About, cover letter, recruiter paste pack — as DIGEST + paste paths under /workspace. Reach for this when packaging Matthew (or fleet user) for a role; never invent metrics; Raven/current role present tense only; CoS does not own prose.Votes: 0GitHub stars: 7
- Design Comp BandsDesign defensible comp bands tied to leveling and dated market data — set midpoints/spreads, compute compa-ratio and range penetration, surface over/under-band outliers. Reach for this on a banding or offer question.Votes: 0GitHub stars: 7
- Diagnose AttritionDiagnose an attrition spike with cost and cause — split regretted from non-regretted, localize to team/manager, price the loss, name the driver. Reach for this on a retention question.Votes: 0GitHub stars: 7
- Model Hiring PlanModel a capacity-tied hiring plan — back-solve the funnel pipeline for target hires, flag the leaking stage, size recruiter capacity, and hand off the comp envelope. Reach for this on a hiring-plan or stuck-req question.Votes: 0GitHub stars: 7
- Read Engagement SignalsRead an engagement survey segmented — surface the team/tenure/manager pockets a company-wide eNPS hides and tie them to forward attrition risk. Reach for this on an engagement-survey question.Votes: 0GitHub stars: 7
- Run Pay Equity ReviewRun a pay-equity review that controls for legitimate factors — compute the raw gap, then the residual after level/role/tenure/location/performance, and route a material residual to counsel. Reach for this on a pay-equity question.Votes: 0GitHub stars: 7
- Load Test DesignDesign the load/stress/soak/spike test from a modeled workload: pick the open- vs closed-model executor deliberately, design ramping and think time, generate realistic owned test data, avoid coordinated omission, and assert thresholds in-script — tool-neutral across k6/Gatling/Locust/JMeter.Votes: 0GitHub stars: 7
- Performance Test StrategySet the performance strategy before testing: turn vague goals into falsifiable NFRs (percentile + threshold + load), model the real workload, link targets to the customer SLO, and choose the test type (load/stress/soak/spike) that answers the open question.Votes: 0GitHub stars: 7
- Profiling And Bottleneck TriageLocalize the bottleneck and size the system: CPU/memory/IO profiling and flame graphs, USE/RED triage to name the constraining resource, capacity planning with headroom via Little's law and the measured saturation point, and regression detection against a committed baseline.Votes: 0GitHub stars: 7
- Balance InventoryRead days-on-hand as tied-up cash vs stockout risk by class, handling specialty/340B/refrigerated distinctly. Reach for this on an inventory question.Votes: 0GitHub stars: 7
- Compute Real MarginCompute reimbursement minus acquisition cost minus DIR fees per script and flag negative-margin scripts the sticker hid. Reach for this on a margin question.Votes: 0GitHub stars: 7
- Protect Dispensing SafetyRead dispensing-error rate as the top operational safety + liability signal and connect it to throughput/staffing pressure — routing the clinical judgment out. Reach for this on a safety or error-rate question.Votes: 0GitHub stars: 7
- Size Throughput StaffingSize technician and pharmacist hours against script volume PLUS clinical-service time, holding verification safety as the constraint. Reach for this on a throughput or staffing question.Votes: 0GitHub stars: 7
- Translate AdherenceMeasure PDC/MPR over the measurement period and translate the adherence band into the star-rating and reimbursement implication. Reach for this on an adherence or star-measure question.Votes: 0GitHub stars: 7
- Defensible DocumentationWrite and review defensible PT/rehab daily notes and evaluations — establishing medical necessity every visit, documenting skilled care as skilled, tying each note to a plan-of-care goal, and avoiding boilerplate that invites a denial or audit finding.Votes: 0GitHub stars: 7
- Denial Prevention And AppealsPrevent PT/rehab claim denials at the front end (eligibility, authorization, units, modifiers, documentation) and triage the ones that slip through to their root cause, then write a documentation-grounded appeal — confirming each payor's edits before billing.Votes: 0GitHub stars: 7
- Plan Of Care ManagementManage the PT/rehab plan of care end to end — goals, frequency/duration, certification, and the recertification clock — so the POC stays signed and current, visits trace to goals, and a lapsing certification is re-booked before it invalidates visits.Votes: 0GitHub stars: 7