smithery.ai

markdown-customizations

Use this skill when creating or editing GitHub Copilot customization Markdown files (agent profiles, prompt files, instruction files, and skills).

First seen Mar 21, 2026

Installation

$ npx skills add https://smithery.ai

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from smithery.ai · top by installs.

npx skills add https://smithery.ai

Browse all from smithery.ai

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Skill metadata

Parsed from SKILL.md frontmatter.

LicenseCC0-1.0
Declared agents github-copilot

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,933 B
  • docs SUMMARY.md 177 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 1 installs

SKILL.md

Markdown Customizations Skill

Purpose

Help create and maintain Copilot customization files with correct structure and consistent, high-signal instructions.

When to use

Use this skill when working on any of:

  • agents/*.agent.md
  • prompts/*.prompt.md
  • instructions/*.instructions.md
  • skills/**/SKILL.md

Procedure

  1. Identify the target file type and verify the correct path + extension.
  2. Add YAML frontmatter at the top with required keys.
  3. Write the body using this structure:

- # Title - ## Purpose - ## How to use - ## Rules (MUST/SHOULD/MAY) - ## Examples (at least one when ambiguity is likely)

  1. Validate glob patterns for .instructions.md files.
  2. Ensure no contradictions with repo-wide copilot-instructions.md.

Do / Don’t

Do

  • Use short, testable rules (e.g., “MUST include description in agent profiles”).
  • Provide one minimal realistic example for each “pattern” (agent/prompt/instructions/skill).
  • Use fenced code blocks with yaml or md tags.

Don’t

  • Don’t put YAML anywhere except the initial frontmatter block.
  • Don’t create skill.md; the file must be named SKILL.md.
  • Don’t introduce conflicting guidance across multiple instruction files.

Examples

Agent profile frontmatter example

---
name: my-agent
description: Short description of what this agent does
tools: ["read", "search", "edit"]
---

Path-specific instructions frontmatter example

---
applyTo: ".github/prompts/**/*.prompt.md"
excludeAgent: "code-review"
---

Prompt file frontmatter example

---
agent: "agent"
description: "One-line description of what this prompt does"
---