All authors
Claude Skills by mcorbett51090
github.com/mcorbett51090964 skills6 installs216 views
- Schedule And Capacity PlanningPlan outpatient PT/rehab clinic capacity and the schedule template against committed plan-of-care visit cadence, provider hours, patient flow, and the measured no-show/cancellation rate — so provider hours become completed, billable visits.Votes: 0GitHub stars: 7
- Therapy Billing And UnitsCalculate PT/rehab billable units correctly: separate timed (time-based, 15-min) from untimed (service-based) CPT codes, apply the 8-minute rule to total timed units, and place GP/KX/59 modifiers — confirming the payor's rule variant before billing.Votes: 0GitHub stars: 7
- Classify DoraCompute the four DORA keys and classify the org against the bands with windows and baselines. Reach for this on a DevEx-measurement question.Votes: 0GitHub stars: 7
- Design Golden PathDesign a paved road that is the lowest-friction compliant option, with self-service actions and guardrails. Reach for this on a paved-road question.Votes: 0GitHub stars: 7
- Measure AdoptionRead adoption as teams-on-golden-path ÷ total, name the gap, and segment the un-adopted teams. Reach for this on an adoption question.Votes: 0GitHub stars: 7
- Quantify ToilQuantify manual toil and the automation ROI in engineer-hours per year. Reach for this on an automate-or-not question.Votes: 0GitHub stars: 7
- Set Platform SlosDefine platform SLIs/SLOs and an error budget that gates platform change. Reach for this on a platform-reliability question.Votes: 0GitHub stars: 7
- Alm Pipeline DesignDesign end-to-end ALM pipelines for Power Platform solutions — pac CLI primitives, Azure DevOps multi-stage pipelines, source-control unpacked solutions, env-var + connection-reference promotion across DEV → TEST → UAT → PROD, managed-vs-unmanaged discipline. Used by `solution-alm-engineer` (primary).Votes: 0GitHub stars: 7
- Canvas App PerformanceDiagnose and fix Power Fx canvas app performance — delegation as a P1 design constraint, lazy-load patterns, Concurrent() vs sequential, ClearCollect vs collection growth, OnStart vs OnVisible, screen-transition cost, control-count budgets per screen, and the connector-call audit via Monitor. Used by `power-fx-engineer` (primary).Votes: 0GitHub stars: 7
- Code ReviewDeep code audit that finds dead wiring, silent failures, unfinished features, placeholder stubs, bloated files, and unnecessary complexity. Produces an actionable report with file:line references grouped by severity. Think of it as a senior dev doing a thorough PR review of the entire codebase. Triggers on: "code review", "audit the code", "review the code", "find dead code", "find placeholders", "check for stubs", "prune the code", "code cleanup", "implementation review", "completeness check...Votes: 0GitHub stars: 7
- Copilot Studio Bot DesignDesign Copilot Studio bots — topic vs generative-answers boundaries, knowledge-source hygiene, trigger-phrase design, slot-filling patterns, escalation-to-human criteria, AI Builder vs prompt-flow vs direct Azure OpenAI decisions, and the test-set discipline that catches regressions on every authoring change. Used by `copilot-studio-engineer` (primary).Votes: 0GitHub stars: 7
- Dataverse Payload PreflightValidate a Dataverse create/update payload against LIVE entity metadata in ONE pass — before you POST/PATCH — so you never fix-one-field-and-retrigger. Catches nonexistent columns, invalid option-set values, malformed/missing lookup binds, missing required fields, and the owner-not-provided (SPN-create) trap together. Run it on the FIRST create failure, or up front when a human re-fire or long run gates each test.Votes: 0GitHub stars: 7
- Dataverse PluginsUse when developing, registering, or deploying Dataverse plugins (C# server-side extensions). Covers the IPlugin interface, execution pipeline stages, entity images, common patterns (auto-numbering, cascading updates, validation), and registration/deployment. Triggers on: "plugin", "server-side logic", "business logic", "auto-number", "cascading update", "pre-operation", "post-operation", "plugin registration", "IPlugin", "execution pipeline", "plugin trace", "InvalidPluginExecutionException"...Votes: 0GitHub stars: 7
- Dataverse Web ApiUse when programmatically creating, modifying, or querying Dataverse schema and metadata via the Web API (OData v4.0). Covers table/column/relationship definitions, solution ALM, form and view XML construction, app module composition, global option sets, business rules, Custom API registration, and publishing. Triggers on: "dataverse api", "dataverse metadata", "entitydefinitions", "web api schema", "create dataverse table", "create dataverse column", "fetchxml", "formxml", "layoutxml", "data...Votes: 0GitHub stars: 7
- Dataverse Web ResourcesUse when creating, deploying, or managing Dataverse web resources for model-driven apps. Covers JavaScript form scripts (OnLoad, OnSave, OnChange events), HTML dashboard pages, CSS styling, image resources, navigation/side panes, ribbon/command bar customization, business process flow client API, and deployment via the Web API. Triggers on: "web resource", "javascript form", "form script", "html dashboard", "ribbon command", "onload event", "onchange event", "onsave event", "formContext", "Xr...Votes: 0GitHub stars: 7
- Dlp Policy DesignDesign tenant Data Loss Prevention policies for Power Platform — business / non-business / blocked classification, environment-scoped vs tenant-wide policies, exemption process, common-connector pitfalls (HTTP, SharePoint, Dataverse, custom connectors), and the "every flow gets re-evaluated on policy change" implication. Used by `power-platform-admin` (primary).Votes: 0GitHub stars: 7
- Grounding ProtocolReduce confident-but-incorrect "I can't do that" claims by forcing agents to verify capabilities before refusing scope. Mandatory checklist covers skills review, alternate-methods enumeration, team-composition check, and escalation phrasing. Inherited by every Power Platform agent.Votes: 0GitHub stars: 7
- Maintainability ReviewForward-looking maintainability + evolvability review of a Power Platform solution — understandability, modifiability, testability, evolution readiness, ownership. Used before major releases, handoffs, when inheriting an existing solution.Votes: 0GitHub stars: 7
- Managed Solution ImportHardened pac solution import plus explicit baseline-aware cloud-flow reactivation for SPN-driven CI/CD — preflight, baseline, import, reactivate, verify. Managed imports leave flows Draft when the importing identity lacks connection permission; this reactivates only flows that were Active, splits transient vs durable 403s, and verifies state. Run on any managed import to TEST/PROD, or use reactivate/verify standalone.Votes: 0GitHub stars: 7
- Pbir Ref IntegrityReport-wide referential-integrity validator for a PBIR Enhanced report's `definition/` tree. Deterministic, stdlib-only `check_refs.py` that catches DANGLING cross-file references — bookmarks pointing at deleted pages/visuals, `visualInteractions` naming visuals that no longer exist, a `pageOrder` that omits/invents/duplicates a page, an `activePageName`/`activeSection` that names a missing page, and report-wide visual-name collisions. Mimics the referential-integrity half of pbir-utils `vali...Votes: 0GitHub stars: 7
- Pcf ControlsUse when building, deploying, or using PowerApps Component Framework (PCF) controls. Covers field controls and dataset controls, React virtual controls, control lifecycle, manifest configuration, solution packaging, and deployment. Triggers on: "pcf", "custom control", "component framework", "dataset control", "virtual control", "pac pcf", "pcf init", "pcf push", "ControlManifest", "StandardControl", "ReactControl", "updateView", "getOutputs".Votes: 0GitHub stars: 7
- Plan With TeamSpawns an Agent Team to collaboratively plan Power Platform / Dataverse applications. Three specialists (Data Architect, UX Designer, The Skeptic) debate and refine the plan before any code is written. Falls back to structured single-agent planning if agent teams are not enabled. Triggers on: "plan my app", "plan with team", "design my app", "architect this app", "plan the schema", "team planning", "agent team plan", "plan power app", "plan dataverse app", "design the data model".Votes: 0GitHub stars: 7
- Power Apps Code AppsUse when building, scaffolding, debugging, or deploying Microsoft Power Apps Code Apps using React, Vue, or TypeScript in VS Code. Handles project initialization via pac CLI, Dataverse and connector data access via the @microsoft/power-apps SDK, power.config.json configuration, Vite build pipelines, and deployment to Power Platform environments. Triggers on: "power apps", "code app", "pac code", "dataverse", "power platform app", "vibe coding", "scaffold power app", "deploy code app".Votes: 0GitHub stars: 7
- Power AutomateVeteran-level reference for Power Automate work — expressions, error handling + scopes, child flows, solution-aware flows + connection references, Dataverse triggers, throttling, approvals, performance patterns. Used by `flow-engineer` (primary) and any agent touching flows.Votes: 0GitHub stars: 7
- Power BiVeteran-level reference for Power BI — PBIP project structure + git, semantic model design, DAX patterns + performance, deployment pipelines, refresh / gateway troubleshooting, integration with Power Platform solutions / ALM. Used by `power-bi-engineer` (primary).Votes: 0GitHub stars: 7
- Power Pages PermissionsDesign table permissions, web roles, and authentication for Power Pages — anonymous vs authenticated patterns, B2C / Entra-External-ID auth, table-permission scoping (global / contact / account / parental / self), record ownership, and the "row I can see in MDA but not in Pages" debugging playbook. Used by `power-pages-engineer` (primary).Votes: 0GitHub stars: 7
- Record ScreenRecord a Chrome browser tab to video via CLI. Use when the user wants to capture a screen recording of a browser tab. Supports list, start, stop, caption, and status subcommands. No debug mode required — uses a Chrome extension.Votes: 0GitHub stars: 7
- Report Visualization DesignDesign a Power BI report/visualization in the Kurt-Buhler / Bas-Dohmen mold — a checklist-driven method: decide the question first, structure the page with the 3-30-300 information-seeking hierarchy, choose the visual by question-type, design headline KPIs with actual/target/gap + pre-attentive color, lay everything on an 8-pt grid, and tune density / color tokens / accessibility. Emits a layout that maps cleanly onto PBIR (visualType enum + pbir-layout-engine geometry). Used by `power-bi-eng...Votes: 0GitHub stars: 7
- Update Model Driven AppUse when an agent must PROGRAMMATICALLY UPDATE an existing model-driven Power Apps app (including its custom pages) in a real Power Platform environment — typically reusing a service principal (SPN). Owns the "there has to be a way" question: it splits the update surface (record/config data · the model-driven solution shell · custom pages) into the right mechanism per surface, front-loads the SPN-rights + environment-policy gates, and enforces the non-obvious safety facts (canvas .pa.yaml is ...Votes: 0GitHub stars: 7
- Visual QaAI-powered visual QA testing that walks through an app in the browser, records every action with annotated captions (what was done, what should happen), captures screenshots/GIFs, and sends the evidence to Gemini for automated review. Catches UX misalignments, broken flows, missing states, and edge cases that traditional tests miss. Can use Agent Teams for parallel test coverage. Triggers on: "visual test", "visual qa", "test the app", "qa review", "check the ui", "record a test", "walk throu...Votes: 0GitHub stars: 7
- Build Fertility From DataBuild the fertility program from current soil/tissue data and removal rates, not last year's program, so neither over- nor under-application costs margin. Reach for this on a fertility question.Votes: 0GitHub stars: 7
- Build Per Acre EconomicsBuild cost and margin per acre by field so the money-losing acres are visible. Reach for this on any margin question.Votes: 0GitHub stars: 7
- Manage By ZoneRead yield and soil by management zone and apply variable-rate inputs where they pay, instead of a field average. Reach for this on a yield or input question.Votes: 0GitHub stars: 7
- Optimize Input EconomicsSet input rates at the economic optimum where marginal return equals marginal cost, not at agronomic maximum, so the last unit pays. Reach for this on any input decision.Votes: 0GitHub stars: 7
- Time The OperationsTime planting, application, and harvest to the agronomic and weather window, since timing drives yield and quality more than rate. Reach for this on an operations-timing question.Votes: 0GitHub stars: 7
- Packaging And TieringDesign good-better-best packaging where each tier is fenced by a self-selection dimension (scale, use case, support, security) rather than a longer feature list, and separate core from add-ons. Reach for this when turning a feature set into tiers, when customers all pick the cheapest plan, or when tiers differ only by feature count. Pairs with value-metric-design.Votes: 0GitHub stars: 7
- Price Change RolloutPlan a price change as a migration, not an edit — grandfathering, cohort sequencing, renewal-timing, comms, and the guardrail metrics (GRR, contraction, leakage, win-rate) to watch. Reach for this when raising prices, repackaging, migrating models (e.g. seat to usage), or simplifying a price card. Pairs with packaging-and-tiering and the price-change-rollout-plan template.Votes: 0GitHub stars: 7
- Pricing Model SelectionChoose the pricing model — subscription, per-seat, usage/consumption, tiered, flat-rate, freemium, or hybrid — by tracing the value of the product against consumption variance and acquisition needs. Reach for this when a product needs its first model, when a per-seat model is capping growth, or when an AI/usage-cost feature breaks the existing model. Pairs with value-metric-design (decide the metric alongside the model).Votes: 0GitHub stars: 7
- Value Metric DesignChoose the value metric — what you charge per (seats, usage units, records, transactions, outcomes) — the single highest-leverage pricing decision. Reach for this when a product's metric caps growth, when expansion isn't automatic, or before setting any price number. Scores candidate metrics on value-alignment, expansion-with-success, and budget-predictability.Votes: 0GitHub stars: 7
- Willingness To Pay ResearchDesign a willingness-to-pay study — Van Westendorp PSM, Gabor-Granger, conjoint/MaxDiff, or a live price A/B test — choosing the method by the decision it serves and the data available, with sample-frame and bias guards. Reach for this before setting a price number, when defending a price, or when stated WTP and behavior disagree. Routes statistical significance to applied-statistics.Votes: 0GitHub stars: 7
- Control Plan And SustainLock the gain after an improvement: build the control plan, design SPC monitoring, write standard work, add poka-yoke (mistake-proofing), define the reaction plan, and hand off to the process owner. A fix without a control plan didn't happen.Votes: 0GitHub stars: 7
- Dmaic Project CharterScope an improvement opportunity as a DMAIC project: problem statement, quantified goal, CTQ/VOC, SIPOC boundaries, baseline metric, team, and timeline. Produces a populated charter using the dmaic-project-charter template.Votes: 0GitHub stars: 7
- Lean Waste AnalysisFind and remove waste using the 8 wastes (DOWNTIME), value-add analysis, takt/cycle time comparison, bottleneck/constraint identification, and quick-win prioritization. Feeds the DMAIC Improve phase with a ranked elimination roadmap.Votes: 0GitHub stars: 7
- Process Capability And SpcBaseline a process: compute DPMO/sigma level and Cp/Cpk, select and read the right control chart (I-MR / Xbar-R / p / c / u), and apply Western Electric/Nelson rules to separate common-cause from special-cause variation. Routes deeper capability inference and hypothesis testing to applied-statistics.Votes: 0GitHub stars: 7
- Process MappingBuild the current-state process map: SIPOC, swimlane/flowchart, and value-stream map. Mark value-add vs. non-value-add steps and handoffs. Identify where to instrument and measure. Used in the DMAIC Measure phase before root-cause analysis begins.Votes: 0GitHub stars: 7
- Root Cause AnalysisDrive to proven root cause using 5 Whys, fishbone/Ishikawa (6M categories), and Pareto (80/20 prioritization), then validate the suspected cause with data. Routes hypothesis testing to applied-statistics. Anti-pattern: solution-jumping before cause is proven.Votes: 0GitHub stars: 7
- Build The Spend CubeBuild and classify the spend cube by category, supplier, and business unit, surfacing tail spend, so strategy rests on visibility. Reach for this when spend is opaque.Votes: 0GitHub stars: 7
- Manage Supplier RiskAssess supplier and concentration risk across the base and mitigate single-source exposure, instead of a one-time checkbox. Reach for this on a continuity question.Votes: 0GitHub stars: 7
- Segment The SpendPlace a category on the supply-risk × spend matrix and match the sourcing play before sourcing, so you don't auction a strategic single-source. Reach for this before any sourcing event.Votes: 0GitHub stars: 7
- Source On TcoRun a sourcing decision on TCO — freight, quality, switching, inventory, lifecycle — not unit price, so a price 'savings' doesn't raise total cost. Reach for this on any sourcing event.Votes: 0GitHub stars: 7