New: 97,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Mcaf

by managedcode in managedcode/dotnet-skills

Apply minimal MCAF repository governance when the user explicitly asks to adopt MCAF or change MCAF-specific rules.

MITAuto-check passedAgent Workflows

Install Mcaf

skills CLI
$ npx skills add managedcode/dotnet-skills --skill mcaf -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install managedcode/dotnet-skills mcaf --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/managedcode/dotnet-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/catalog/Platform/MCAF/skills/mcaf .claude/skills/mcaf && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
mcaf
GitHub stars
486
Token cost
~1.2k tokens
SKILL.md length
568 words
Files
3 (incl. references)
Skills in repo
81
Repo updated
First seen
Licence
MIT

At a glance

Apply minimal MCAF repository governance when the user explicitly asks to adopt MCAF or change MCAF-specific rules.

  • Works in 7 steps: Confirm that the request is explicitly… → Read the root AGENTS.md and every… → Keep only durable repository rules that… → …
  • Explicitly asks to adopt MCAF
  • SKILL.md covers Workflow, MCAF 1.3.68 Policy Contract, Minimal Rules and Boundaries, plus 3 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Mcaf is an agent skill from managedcode/dotnet-skills. Apply minimal MCAF repository governance when the user explicitly asks to adopt MCAF or change MCAF-specific rules. USE FOR: creating or tightening root and local AGENTS.md policy; placing durable engineering context; defining the repository's own verification contract. DO NOT USE FOR: ordinary .NET implementation, documentation edits, UI/UX, testing, CI, Git, NFR, developer-experience, or ML work unless the request is specifically about MCAF governance. INVOKES: inspect repository policy and documentation, make…

Its SKILL.md is about 1.2k tokens, which your agent loads only when the skill is triggered. The skill folder holds 3 other files, including reference files (for example `manifest.json` and `references/adoption.md`).

It sits in Agent Workflows, covering UI design and Agent instruction files. It works with Git and .NET. The repository describes itself as: Installable .NET skill catalog and CLI for Codex, Claude Code, GitHub Copilot, and Gemini. The licence is MIT.

When your agent uses it

  • Explicitly asks to adopt MCAF
  • Change MCAF-specific rules
  • Tightening root and local AGENTS.md policy
  • Placing durable engineering context

Example prompts

  • “/mcaf”

Workflow steps

7 steps, taken from the first numbered list in SKILL.md.

  1. Confirm that the request is explicitly about adopting MCAF or changing MCAF governance.
  2. Read the root AGENTS.md and every affected local AGENTS.md completely before editing any of them.
  3. Keep only durable repository rules that future contributors and agents must know.
  4. Put each rule next to the area that owns it. Add a local AGENTS.md only when a subtree genuinely differs.
  5. Record exact build, test, format, analysis, and operational commands when the repository depends on them.
  6. Route implementation work to the normal catalog skill closest to the actual technology or behavior.
  7. Validate the changed policy, documentation links, and repository commands.

What it can do on your machine

Read from SKILL.md and the folder at commit 535dd55. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Mcaf loads about 1.2k tokens when it runs, and up to ~1.9k if it reads all its reference files. Until then it costs about 153 tokens; SKILL.md has 568 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~153
When it runs · the whole SKILL.md, loaded when a task matches
~1.2k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~1.9k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from managedcode/dotnet-skills at commit 535dd55, republished under its MIT licence (© managedcode). 568 words, ~1,200 tokens.

Download SKILL.mdSave it as .claude/skills/mcaf/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.
name
mcaf
description
Apply minimal MCAF repository governance when the user explicitly asks to adopt MCAF or change MCAF-specific rules. USE FOR: creating or tightening root and local AGENTS.md policy; placing durable engineering context; defining the repository's own verification contract. DO NOT USE FOR: ordinary .NET implementation, documentation edits, UI/UX, testing, CI, Git, NFR, developer-experience, or ML work unless the request is specifically about MCAF governance. INVOKES: inspect repository policy and documentation, make the smallest durable governance change, then validate the affected repository surfaces.

MCAF Governance

Keep MCAF as one opt-in governance layer. Do not create parallel mcaf-* implementation or process skills.

Workflow

  1. Confirm that the request is explicitly about adopting MCAF or changing MCAF governance.
  2. Read the root AGENTS.md and every affected local AGENTS.md completely before editing any of them.
  3. Keep only durable repository rules that future contributors and agents must know.
  4. Put each rule next to the area that owns it. Add a local AGENTS.md only when a subtree genuinely differs.
  5. Record exact build, test, format, analysis, and operational commands when the repository depends on them.
  6. Route implementation work to the normal catalog skill closest to the actual technology or behavior.
  7. Validate the changed policy, documentation links, and repository commands.

MCAF 1.3.68 Policy Contract

When a repository declares that it follows MCAF 1.3, preserve these upstream mandatory policies rather than treating them as optional templates:

  • MCAF-ARCH-001: keep the complete solution in one repository and use one canonical vertical-slice identity across applicable code, tests, infrastructure, and feature documentation.
  • MCAF-GOV-001: merge incoming MCAF guidance into existing root and local AGENTS.md files. Never overwrite, truncate, summarize away, weaken, or silently omit an existing repository rule.
  • MCAF-REQ-001: for non-trivial features, keep stable requirements and acceptance criteria, map them to automated tests or explicit evidence exceptions, and link any required ADR implementation contract.
  • MCAF-AI-001: use a capable planning/integration owner for non-trivial work and keep delegated scopes bounded, independently verified, and joined before completion when the execution environment supports delegation.

Do not inject these policies into a repository that has not chosen MCAF. When updating an existing MCAF repository, preserve any stricter local rule and report a genuine conflict instead of weakening it.

Minimal Rules

  • Keep one root AGENTS.md.
  • In a multi-project MCAF solution, keep a local AGENTS.md in each project or module root with its entry points, boundaries, commands, applicable skills, and local risks.
  • Keep one source of truth for each durable fact.
  • Describe the current repository, not an intended future state.
  • Make acceptance and verification expectations concrete and runnable.
  • Add feature specifications, ADRs, review plans, or quality constraints only when the task actually needs those artifacts.
  • Turn repeated team pain into a small durable rule; do not encode one-off preferences.
Show full SKILL.md (197 more words)Show less

Boundaries

  • Do not use MCAF as a router for normal .NET work; use dotnet or the narrow framework skill.
  • Do not impose generic agile ceremonies, branch naming, UI/UX choices, onboarding templates, NFR catalogs, or ML process.
  • Do not duplicate testing, CI, documentation, security, observability, or architecture skills under an MCAF namespace.
  • Do not invent planning artifacts beyond the repository's adopted MCAF version. Current MCAF 1.3 repositories require brainstorm, acceptance, and plan artifacts for non-trivial work, so preserve that contract when it is already adopted.
  • Do not add process artifacts that are larger than the decision or behavior they clarify.

Deliver

  • the smallest repository-native governance change that resolves the explicit MCAF request
  • direct routing to implementation-focused skills for everything outside governance

Validate

  • every new rule is durable, scoped, and owned by a repository surface
  • no rule duplicates a normal implementation skill
  • referenced commands and paths exist
  • an MCAF 1.3 repository preserves MCAF-ARCH-001, MCAF-GOV-001, MCAF-REQ-001, and MCAF-AI-001 or records an explicit versioned migration state
  • scripts/verify-mandatory-policies.sh passes when the consuming repository has adopted the upstream verifier
  • removed or renamed MCAF surfaces leave no dangling catalog, bundle, watch, or documentation references

Reference

Read references/adoption.md only when bootstrapping MCAF in a repository.

© managedcode, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 2 other files (references) in catalog/Platform/MCAF/skills/mcaf of managedcode/dotnet-skills.

  • SKILL.md
  • manifest.json
  • references/adoption.md

Open the folder on GitHubat commit 535dd55

Compare with similar skills

Mcaf next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Mcaf compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Mcaf this skillmanagedcode/dotnet-skills486—~1.2kAutomated safety check: PassMIT
Neat-Freak Knowledge CloseoutKKKKhazix/khazix-skills21k—~1.9kAutomated safety check: PassMIT
Harness Evolution Feedback Looprevfactory/harness9.1k—~855Automated safety check: PassApache-2.0
Setup Matt Pocock Skillsywwynm/EverythingDone1449 repos~1.7kAutomated safety check: PassGPL-3.0
Squad Agent Collaboration Patternsmicrosoft/waza1.4k4 repos~500Automated safety check: PassMIT
Docslatitude-dev/latitude-llm4.7k—~2.5kAutomated safety check: PassMIT

Similar skills

  • Neat-Freak Knowledge Closeout

    KKKKhazix/khazix-skills

    Brings project docs, agent rule files, authorized memory and leftover workspace files back in line with what the code and runtime actually do at the end of a work session.

    21k GitHub stars~1.9k tokensUpdated 6 days ago
    Agent WorkflowsAuto-check passed

  • Harness Evolution Feedback Loop

    revfactory/harness

    Collects feedback on how an agent harness performed, generalizes it, and updates the harness agents, skills and orchestrator along with a change-history table.

    9.1k GitHub stars~855 tokensUpdated 9 days ago
    Agent WorkflowsAuto-check passed

  • Setup Matt Pocock Skills

    ywwynm/EverythingDone

    Sets up an Agent skills block in AGENTS.md/CLAUDE.md and docs/agents/ so the engineering skills know this repo's issue tracker (GitHub or local markdown), triage label vocabulary, and domain doc…

    144 GitHub starsUsed in 9 repos~1.7k tokens
    Agent WorkflowsAuto-check passed

  • Squad Agent Collaboration Patterns

    microsoft/waza

    Official

    Shared collaboration rules for a team of squad agents covering worktree awareness, writing decisions to an inbox, cross-agent requests and reviewer lockout.

    1.4k GitHub starsUsed in 4 repos~500 tokens
    Agent WorkflowsAuto-check passed

  • Docs

    latitude-dev/latitude-llm

    Review the current conversation context and git changes, then persist durable repository knowledge into dev-docs/.md by domain and into AGENTS.md for cross-cutting repo rules.

    4.7k GitHub stars~2.5k tokensUpdated yesterday
    Agent WorkflowsAuto-check passed

  • Init My Project

    MCSLTeam/MCServerLauncher-Future

    Bootstrap reusable project governance for a new or existing repo.

    121 GitHub stars~2.1k tokensUpdated 1 mo ago
    Agent WorkflowsAuto-check passed

More from managedcode/dotnet-skills

All 81 skills in this repo

  • Analyzer Config

    managedcode/dotnet-skills

    Use a repo-root .editorconfig to configure free .NET analyzer and style rules.

    486 GitHub stars~1.3k tokensUpdated today
    Auto-check passed

  • Archunitnet

    managedcode/dotnet-skills

    Use the open-source free ArchUnitNET library for architecture rules in .NET tests.

    486 GitHub stars~1.2k tokensUpdated today
    Auto-check passed

  • Aspire

    managedcode/dotnet-skills

    Build, upgrade, and operate Aspire 13.5.x C or TypeScript application hosts with the current CLI, AppHost, ServiceDefaults, integrations, dashboard, testing, MCP, and deployment patterns for…

    486 GitHub stars~3.6k tokensUpdated today
    Auto-check passed

  • Aspnet Core

    managedcode/dotnet-skills

    Build, debug, modernize, or review ASP.NET Core applications with correct hosting, middleware, security, configuration, logging, and deployment patterns on current .NET.

    486 GitHub stars~2.1k tokensUpdated today
    Auto-check passed

  • Asynkron Profiler

    managedcode/dotnet-skills

    Use the open-source free Asynkron.Profiler dotnet tool for CLI-first CPU, allocation, exception, contention, and heap profiling of .NET commands or existing trace artifacts.

    486 GitHub stars~1.7k tokensUpdated today
    Auto-check passed

  • Azure Functions

    managedcode/dotnet-skills

    Build, review, or migrate Azure Functions in .NET with correct execution model, isolated worker setup, bindings, DI, and Durable Functions patterns.

    486 GitHub stars~2.6k tokensUpdated today
    Auto-check passed

Works with

Categories

Questions about Mcaf

What does Mcaf do?

Apply minimal MCAF repository governance when the user explicitly asks to adopt MCAF or change MCAF-specific rules. Mcaf is an agent skill from managedcode/dotnet-skills. Apply minimal MCAF repository governance when the user explicitly asks to adopt MCAF or change MCAF-specific rules.

When should I use Mcaf?

Mcaf fits situations like: explicitly asks to adopt MCAF; change MCAF-specific rules; tightening root and local AGENTS.md policy; placing durable engineering context.

How do I install Mcaf in Claude Code?

Run `npx skills add managedcode/dotnet-skills --skill mcaf -a claude-code`. Or copy the skill folder (catalog/Platform/MCAF/skills/mcaf in managedcode/dotnet-skills) into .claude/skills/mcaf in your project. Claude Code loads it when a task matches its description.

How do I install Mcaf in Codex?

Run `npx skills add managedcode/dotnet-skills --skill mcaf -a codex`. Or copy the skill folder (catalog/Platform/MCAF/skills/mcaf in managedcode/dotnet-skills) into .agents/skills/mcaf in your project. Codex loads it when a task matches its description.

Can I use Mcaf in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add managedcode/dotnet-skills --skill mcaf -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/mcaf, .gemini/skills/mcaf, .github/skills/mcaf and .opencode/skills/mcaf in your project.

What does Mcaf need to run?

SKILL.md names no scripts, command-line tools or credentials: Mcaf is instructions for the agent only.

Does Mcaf access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Mcaf safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Mcaf use?

Mcaf is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Mcaf use?

About 1.2k tokens (SKILL.md is roughly 4.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 733 tokens, read only when the agent opens those files.

What are the alternatives to Mcaf?

Skills that share tags, products or a category with Mcaf: Neat-Freak Knowledge Closeout (KKKKhazix/khazix-skills, 21k stars), Harness Evolution Feedback Loop (revfactory/harness, 9.1k stars), Setup Matt Pocock Skills (ywwynm/EverythingDone, 144 stars) and Squad Agent Collaboration Patterns (microsoft/waza, 1.4k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Mcaf?

managedcode (a GitHub organization) maintains it in managedcode/dotnet-skills, which has 486 GitHub stars. The repository holds 81 skills in this directory. The repository was last updated on October 7, 2026.

Source: managedcode/dotnet-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.