A guide for creating or changing PPDS skills, including their names, folder structure, instructions, and discoverability.

Use it when authoring, editing, renaming, or reorganizing a skill in `.claude/skills/`.

It helps new skills follow the project's conventions so users can find and use them consistently.

write-skill — Skill for Claude Code and Codex by joshsmithxrm: A guide for creating or changing PPDS skills, including…

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods

npx agentmods add skills/joshsmithxrm/power-platform-developer-suite/write-skill

Any agent

npx skills add joshsmithxrm/power-platform-developer-suite --skill write-skill

Clone the repo

git clone --depth 1 https://github.com/joshsmithxrm/power-platform-developer-suite

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/joshsmithxrm/power-platform-developer-suite/write-skill.svg)](https://agentmods.dev/skills/joshsmithxrm/power-platform-developer-suite/write-skill)

Your own site

<a href="https://agentmods.dev/skills/joshsmithxrm/power-platform-developer-suite/write-skill"><img src="https://agentmods.dev/badge/skills/joshsmithxrm/power-platform-developer-suite/write-skill.svg" alt="Measured on agentmods" height="20"></a>

Per session 33 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 895 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5	$0.00033	$0.00895
Opus 5	$0.00016	$0.00447
Sonnet 5	$0.00007	$0.00179
Haiku 4.5	$0.00003	$0.00089

Measured 3d ago against content hash 5f7d525b9a5e, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

write-skill scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 3d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.claude/skills/write-skill/SKILL.md · 88 lines

How it starts

The opening of the file, as written. The whole thing — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Write Skill

Guide for authoring PPDS skills that are consistent and discoverable.

Naming Convention

Pattern: {action} or {action}-{qualifier}, kebab-case.

The name should describe what the skill does, not the technology it uses.

Good	Bad	Why
`ext-verify`	`webview-cdp`	Users think "verify extension," not "use Chrome DevTools Protocol"
`tui-verify`	`terminal-pty`	Named by surface + action, not by technology
`ext-panels`	`webview-panels`	Consistent `ext-` prefix for extension skills
`design`	`brainstorm-spec`	Single word when unambiguous
`pr`	`create-pull-request`	Short is better when the action is obvious
`debug`	`systematic-debugging`	Verb, not adjective-noun

Qualifiers: Only add when needed to disambiguate. /verify is the orchestrator; surface-specific guides are in /verify REFERENCE.md sections.

Directory Structure

Skills go in .claude/skills/<name>/SKILL.md:

.claude/skills/
  my-skill/
    SKILL.md           # Required — the skill content
    supporting-doc.md  # Optional — referenced by SKILL.md
    example.py         # Optional — code examples or scripts

All skills live in .claude/skills/{name}/SKILL.md with YAML frontmatter. The .claude/commands/ directory has been deprecated and removed.

Frontmatter

Every SKILL.md starts with YAML frontmatter:

---
name: my-skill
description: One sentence describing when to use this skill. Write for AI discoverability — this is what makes the AI auto-load the skill when the user says something relevant.
---

Description tips:

Lead with the trigger condition: "Use when..." or "How to..."
Include the words a user would say: "test the extension", "create a PR", "debug this"
Don't describe the technology — describe the user's intent
Keep under 200 characters

Two-File Pattern

SKILL.md is capped at 150 lines and is the entry point loaded on demand. Move rationale, worked examples, and long tables into a sibling REFERENCE.md that SKILL.md references. See .claude/skills/TWO-FILE-PATTERN.md.

Read the full file on GitHub · 88 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

3d ago First seen · 88 lines · 33 tokens per session scan A 5f7d525b9a5e

Subscribe to this mod's changes

write-skill is a skill published in the GitHub repository joshsmithxrm/power-platform-developer-suite (5 stars, last pushed 10d ago), licensed MIT. It adds 33 tokens to every session and 895 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Building agents cli dataverse dotnet dynamics365 mcp power-platform

PowerAppsControl

Drive the PowerAppsControl MCP server to UX-test a Power App end to end: open and verify an app URL, let the user choose a mode (smoke test = in-depth read-only exploration that produces a repeatable natural-language test plan; or run my test plan), then run it in a recorded session and produce a video + HTML report…

ilyafainberg/PowerAppsControl · 177 tokens

xrm-mcp

Skip steps you already have answers for. If you ran listtables or describetable earlier in the session, reuse those results.

jukkan/xrm-mcp · 0 tokens

run-integration-tests

Build, pack, and run .NET MAUI integration tests locally. Validates templates, samples, and end-to-end scenarios using the local workload.

dotnet/maui · 35 tokens

run-helix-tests

Submit and monitor .NET MAUI unit tests on Helix infrastructure. Supports running XAML, Resizetizer, Core, Essentials, and other unit test projects on distributed Helix queues.

dotnet/maui · 45 tokens

refresh-arm-sdk-release

WORKFLOW SKILL — Prepares Azure.ResourceManager SDK refresh pull requests in azure-sdk-for-net. WHEN: "prepare sdk refresh", "refresh Azure.ResourceManager package", "update ARM SDK from autorest tag", "refresh changelog dependencies". INVOKES: git and GitHub pull request tools for branch, commit, push, and PR…

Azure/azure-sdk-for-net · 91 tokens

azsdk-common-pipeline-analysis

Analyze Azure SDK CI/CD pipeline failures into a structured diagnosis, and define the required output format. Load this skill before calling azsdkanalyzepipeline, which returns raw failure data that this skill interprets and formats. USE FOR: "pipeline failed", "build failure", "CI check failing", "tests failing in…

Azure/azure-sdk-for-net · 192 tokens