Install
$ agentstack add skill-dotnet-skills-create-skill ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Create Skill
This skill helps you scaffold new agent skills that conform to the Agent Skills specification and the dotnet/skills repository conventions.
When to Use
- Creating a new skill from scratch
- Generating a SKILL.md file with proper frontmatter
- Setting up the skill directory structure with optional folders
- Ensuring compliance with agentskills.io specification
When Not to Use
- Modifying existing skills (edit directly instead)
- Creating custom agents (use the agents/ directory pattern)
Inputs
| Input | Required | Description | |-------|----------|-------------| | Skill name | Yes | Lowercase, alphanumeric, hyphens only (e.g., code-review, ci-triage) | | Description | Yes | What the skill does and when agents should use it (1-1024 chars) | | Purpose | Yes | One paragraph describing the outcome | | Workflow steps | Recommended | Numbered steps the agent should follow |
Workflow
Step 1: Validate the skill name
Ensure the name:
- Contains only lowercase letters, numbers, and hyphens
- Does not start or end with a hyphen
- Does not contain consecutive hyphens
- Is between 1-64 characters
Step 2: Create the skill directory
skills//
└── SKILL.md
Step 3: Generate SKILL.md with frontmatter
Create the file with required YAML frontmatter:
---
name:
description:
---
Step 4: Add body content sections
Include these recommended sections:
- Purpose: One paragraph describing the outcome
- When to Use: Bullet list of appropriate scenarios
- When Not to Use: Boundaries and exclusions
- Inputs: Table of required and optional inputs
- Workflow: Numbered steps with checkpoints
- Validation: How to confirm the skill worked correctly
- Common Pitfalls: Known traps and how to avoid them
Step 5: Add optional directories (if needed)
skills//
├── SKILL.md
├── scripts/ # Executable code agents can run
├── references/ # Additional documentation loaded on demand
└── assets/ # Templates, images, data files
Step 6: Update CODEOWNERS
Add entries in .github/CODEOWNERS for the new skill and its test directory:
/plugins//skills// @owner-team
/tests/// @owner-team
Match the owner pattern used by sibling skills in the same plugin.
Step 7: Validate the skill
- Confirm frontmatter fields are valid
- Ensure SKILL.md is under 500 lines
- Check that file references use relative paths
- Verify instructions are actionable and specific
SKILL.md Template
Use this template when creating a new skill:
---
name:
description:
---
#
## When to Use
-
-
## When Not to Use
-
-
## Inputs
| Input | Required | Description |
|-------|----------|-------------|
| | Yes/No | |
## Workflow
### Step 1:
### Step 2:
## Validation
- [ ]
- [ ]
## Common Pitfalls
| Pitfall | Solution |
|---------|----------|
| | |
Validation Checklist
After creating a skill, verify:
- [ ] Skill name matches directory name exactly
- [ ] Skill name is lowercase with hyphens only
- [ ] Description is non-empty and under 1024 characters
- [ ] SKILL.md body is under 500 lines
- [ ] Instructions are specific and actionable
- [ ] Workflow has numbered steps with clear checkpoints
- [ ] Validation section exists with observable success criteria
- [ ] No secrets, tokens, or internal URLs included
- [ ]
.github/CODEOWNERShas entries for the new skill and its test directory
Common Pitfalls
| Pitfall | Solution | |---------|----------| | Name contains uppercase letters | Use only lowercase: code-review not Code-Review | | Description is vague | Include what it does AND when to use it | | Instructions are ambiguous | Use numbered steps with concrete actions | | Missing validation steps | Add checkpoints that verify success | | SKILL.md too long | Move detailed content to references/ files | | Hardcoded environment assumptions | Document requirements in compatibility field | | Missing CODEOWNERS entry | Add entries for both /plugins//skills// and /tests/// matching sibling skills' owner pattern |
References
- Agent Skills Specification
- [Repository README](../../README.md)
- [Contributing Guidelines](../../CONTRIBUTING.md)
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: dotnet
- Source: dotnet/skills
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.