Borrowing it
Nothing to install: this file belongs to joshsmithxrm/power-platform-developer-suite. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/joshsmithxrm/power-platform-developer-suite/main/.claude/skills/write-skill/SKILL.mdgit clone --depth 1 https://github.com/joshsmithxrm/power-platform-developer-suiteWrote 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.
[](https://agentmods.dev/skills/joshsmithxrm/power-platform-developer-suite/write-skill)<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/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<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="Reviewed on agentmods" width="80" height="20"></a>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.1 | $0.00033 | $0.00895 |
| Opus 5.5 | $0.00013 | $0.00358 |
| Sonnet 5.5 | $0.00007 | $0.00179 |
| Haiku 4.5 | $0.00003 | $0.00089 |
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 1mo 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.
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.
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.
- 1mo ago First seen · 88 lines · 33 tokens per session scan A 5f7d525b9a5e
write-skill is a skill published in the GitHub repository joshsmithxrm/power-platform-developer-suite (7 stars, last pushed 4d ago), licensed MIT. It adds 33 tokens to every session and 895 once invoked, about $0.0001 per session on Opus 5.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.
Other skills, from other repositories
dynamics365-expert
Expert in Dynamics 365 platform, model-driven apps, canvas apps, Power Automate flows, Dataverse, plugins, and custom workflows. Use when the user mentions Microsoft platforms, ERP, CRM, business apps, the Power Platform, or Dataverse, or when the task involves Dynamics 365 Applications, Dataverse Platform…
csharp-dotnet
Use when writing, reviewing, testing, or shipping C# / .NET code — ASP.NET Core APIs (minimal APIs vs controllers), EF Core data access, async correctness, solution layout in .cs/.csproj/.sln. NOT a Java/Spring backend (that is spring-boot), NOT a Node/TypeScript backend (that is nestjs), NOT framework-neutral REST…
release
Prepare and publish Perigon.CLI patch releases, including versioning, release notes, bilingual docs, validation, and the nuget-branch CI handoff.
docs
Use for Perigon documentation work across this workspace, especially Perigon.docs/Content/docs/Perigon bilingual and versioned docs, syncing zh-CN and en-US content, updating docs from Perigon.CLI, Perigon.template, and Perigon.Modules changes, and deciding whether to revise existing pages or add new documentation.
blazor
Use for Blazor Server development with Fluent UI Blazor, Razor components, layouts, pages, scoped UI services, culture switching, localization, forms, loading/empty/error states, and Studio-style dashboard workflows.
cli
Use for .NET command-line tool development with Spectre.Console/Spectre.Console.Cli, Microsoft.Extensions.Hosting, dependency injection, localized help text, command settings, aliases, examples, terminal output, exit codes, and stdio-safe command paths.