القائمة
Format and spec compliance for SKILL.md files. Use when authoring or reviewing a skill. Triggers: "review this skill", new skill drafted, format check, "does this match the dojo standard".
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Extract text, tables, citations, forms, and metadata from PDFs as grounded context for downstream M365 Copilot work. Use whenever a source for research-synthesis, decision-memo, or document-summarization arrives as a PDF (contracts, regulatory filings, policy documents, vendor reports, scanned forms, fillable intake forms, academic papers), including encrypted, permission-restricted, hybrid native-plus-scan, or large multi-hundred-page packs. Triggers: "extract from this PDF", "summarize this filing", "pull table from PDF", "OCR this scan", "read the fillable form", "this PDF is password-protected".
Produce a recap of decisions, actions, and owners — not a transcript. Use within 24h of any meeting where decisions were made or actions assigned. For a recurring series, also produce a private behavioral readout over a set window — speaking-time, decision velocity, and action carryover as a share of the whole, each finding tied to one concrete change. Triggers: "recap the meeting", "send notes", "what did we decide", post-meeting summary, "are our standups working", recurring-meeting health, meeting-series readout.
Critically inspect Copilot's draft for facts, tone, omissions, bias, and audience fit, then triage what you find by confidence and severity. Use as the REVIEW step of the pipeline, before any iteration or shipping. Triggers: before refining; before send; before a decision or sign-off; after every Copilot draft of meaningful length; reviewing a deliverable, deck, memo, or generated code/automation; running specialized passes (callout accuracy, silent gaps, will-it-survive-scrutiny, structure integrity).
Meta-skill for creating and improving dojo skills. Use when you've found a workflow worth packaging — typically after a pattern recurs 3+ times in tasks/lessons.md — or when an existing skill triggers unreliably and needs a test-driven tune-up. Triggers: "should this be a skill", recurring pattern, promoting a lesson, packaging a workflow, "this skill never fires", optimizing a skill description for discovery.
Apply your organization's brand - colors, typography, logo, and tone - consistently across Copilot-generated deliverables in Word, PowerPoint, Teams, and Viva. Use when polishing a deck, document, or post so it looks on-brand and accessible. Triggers: "make it on-brand", "apply our branding", "brand colors", "company template", "style this deck", "corporate identity", "match our style guide".
Phased workflow for building a high-quality connector or MCP server that lets Copilot act on an external system (an internal API, a line-of-business app, a SaaS tool). Use when planning, designing, or reviewing custom connector tools for Copilot or M365 agents. Triggers: "build a connector", "MCP server", "expose our API to Copilot", "custom tool for Copilot", "connect Copilot to <system>", "Graph connector design".
| name | writing-skills |
| category | do |
| description | Format and spec compliance for SKILL.md files. Use when authoring or reviewing a skill. Triggers: "review this skill", new skill drafted, format check, "does this match the dojo standard". |
A SKILL.md must look the same across the dojo so agents can parse it without surprise.
| Slot | Required? |
|---|---|
YAML frontmatter (name, category, description) | Yes |
# Title | Yes |
| One-line tagline | Yes |
## Quick Reference (table) | Yes |
## When to Use | Yes |
## How to Use | Yes |
## Examples (Don't:/Do: table) | Yes |
## Critical Rules | Yes |
## Common Pitfalls | Yes |
## Anti-Patterns | Yes |
## Verify Before <action> (checklist) | Yes |
## Related | Yes |
---
name: kebab-case-name
category: kata | waza | kumite-task | kumite-office | kumite-connector | cowork | do
description: >-
One paragraph. Specific about when the agent should activate this skill.
Mention trigger phrases, contexts, and the typical scenario.
---
# Title Case Name
One-line summary.
---
## Quick Reference
| col | col |
|---|---|
| ... | ... |
## When to Use
- Trigger 1
- Trigger 2
## How to Use
Step-by-step or numbered list.
## Examples
| Don't: Anti | Do: Pro |
## Critical Rules
- ...
## Common Pitfalls
- ...
## Anti-Patterns
- ...
## Verify Before <action>
- [ ] ...
## Related
- [other-skill](../other-skill/SKILL.md)
name matches the folder name exactly.category is one of: kata, waza, kumite-task, kumite-office, kumite-connector, cowork, do.description is what Copilot uses to activate the skill — be specific; include trigger phrases.Don't: / Do:) for comparisons.| Don't: Format failure | Do: Format success |
|---|---|
Missing category | category: kata (or appropriate) |
description says "use this skill for stuff" | description lists 3 trigger phrases + scenario |
| Body opens with backstory | Body opens with one-line tagline |
| Anti-Patterns lists examples without "why" | Anti-Patterns names the failure mode |
| No Related links | Related lists 3–5 sibling skills |
name / category / description = broken auto-discovery.name matches folder.category set to a valid value.description includes specific trigger phrases.Don't: / Do: comparison table (no emoji).