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 Testing

by managedcode in managedcode/Storage

Add or update automated tests for a change using the repository’s verification rules in AGENTS.md.

MITAuto-check passedTesting & QA

Install Mcaf Testing

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

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

GitHub CLI
$ gh skill install managedcode/Storage mcaf-testing --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/Storage.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.codex/skills/mcaf-testing .claude/skills/mcaf-testing && 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-testing
GitHub stars
138
Token cost
~1.2k tokens
SKILL.md length
590 words
Files
3 (incl. references)
Skills in repo
41
Repo updated
First seen
Licence
MIT

At a glance

Add or update automated tests for a change using the repository’s verification rules in AGENTS.md.

  • Works in 3 steps: Read the nearest AGENTS.md and confirm… → Run this skill's Workflow through the… → Return the Required Result Format with…
  • Implementing a feature
  • SKILL.md covers Trigger On, Value, Do Not Use For and Inputs, plus 7 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Mcaf Testing is an agent skill from managedcode/Storage. Add or update automated tests for a change using the repository’s verification rules in AGENTS.md. Use when implementing a feature, bugfix, refactor, or regression test; prefer stable integration/API/UI coverage and pull deeper test strategy from the bundled references.

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 `references/automated-testing.md` and `references/test-planning.md`). Compatibility notes: Requires the repository’s build and test tooling; uses commands from root or local AGENTS.md.

It sits in Testing & QA, covering Test strategy, Agent instruction files and Refactoring. It works with .NET. The repository describes itself as: Storage library provides a universal interface for accessing and manipulating data in different cloud blob storage providers. The licence is MIT.

When your agent uses it

  • Implementing a feature
  • Regression test
  • Prefer stable integration/API/UI coverage and pull deeper test strategy from the bundled references

Example prompts

  • “/mcaf-testing”

Requirements

  • Compatibility (from SKILL.md): Requires the repository’s build and test tooling; uses commands from root or local `AGENTS.md`.

Workflow steps

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

  1. Read the nearest AGENTS.md and confirm scope and constraints.
  2. Run this skill's Workflow through the Ralph Loop until outcomes are acceptable.
  3. Return the Required Result Format with concrete artifacts and verification evidence.

What it can do on your machine

Read from SKILL.md and the folder at commit 5d32121. 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.

  • Compatibility

    Requires the repository’s build and test tooling; uses commands from root or local `AGENTS.md`.

    From compatibility in the SKILL.md frontmatter.

Context cost

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

Always · name and description, kept in context so the agent knows when to use it
~71
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
~4.4k

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/Storage at commit 5d32121, republished under its MIT licence (© managedcode). 590 words, ~1,176 tokens.

Download SKILL.mdSave it as .claude/skills/mcaf-testing/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.
name
mcaf-testing
description
Add or update automated tests for a change using the repository’s verification rules in `AGENTS.md`. Use when implementing a feature, bugfix, refactor, or regression test; prefer stable integration/API/UI coverage and pull deeper test strategy from the bundled references.
compatibility
Requires the repository’s build and test tooling; uses commands from root or local `AGENTS.md`.

MCAF: Testing

Trigger On

  • implementing a feature or bugfix
  • adding a regression test for a failure
  • protecting a refactor with automated verification

Value

  • produce a concrete project delta: code, docs, config, tests, CI, or review artifact
  • reduce ambiguity through explicit planning, verification, and final validation skills
  • leave reusable project context so future tasks are faster and safer

Do Not Use For

  • repo-wide delivery policy with no test change
  • documentation-only changes unless they alter executable verification

Inputs

  • the nearest AGENTS.md
  • the changed behaviour and touched boundaries
  • existing tests near the impacted code path

Quick Start

  1. Read the nearest AGENTS.md and confirm scope and constraints.
  2. Run this skill's Workflow through the Ralph Loop until outcomes are acceptable.
  3. Return the Required Result Format with concrete artifacts and verification evidence.

Workflow

  1. Read the repo’s real verification commands from AGENTS.md.
  2. Start with a failing test first when the change adds behaviour or fixes a bug.
  3. Start with the smallest meaningful test scope:
    • new or changed tests
    • related suite
    • broader regressions
  4. When the stack is .NET, use mcaf-dotnet as the orchestration skill when the task spans code, tests, and verification, and route framework mechanics through exactly one matching skill:
    • mcaf-dotnet-xunit
    • mcaf-dotnet-tunit
    • mcaf-dotnet-mstest
  5. Prefer integration, API, or UI coverage when behaviour crosses boundaries.
  6. Prove the user flow or caller-visible system flow, not just internal details.
  7. Add a regression test for every bug that can be captured reliably.
  8. If the stack is .NET and production code changed, do not stop at tests only. Finish with the repo-defined format and analyzer pass as well.
  9. Use deeper testing references only when the repo’s current strategy is unclear.

Deliver

  • automated tests close to the changed behaviour
  • verification results that match the repo’s real commands

Validate

  • the new behaviour is covered at the right level
  • the main user flow or caller-visible system flow is proven
  • tests assert meaningful outcomes, not implementation trivia
  • coverage expectations from AGENTS.md are met, or the exception is documented
  • the verification sequence matches AGENTS.md
  • for .NET changes, tests were not treated as a substitute for formatting or analyzer gates
  • broader suites are run after there is something real to verify
Show full SKILL.md (226 more words)Show less

Ralph Loop

Use the Ralph Loop for every task, including docs, architecture, testing, and tooling work.

  1. Plan first (mandatory):
    • analyze current state
    • define target outcome, constraints, and risks
    • write a detailed execution plan
    • list final validation skills to run at the end, with order and reason
  2. Execute one planned step and produce a concrete delta.
  3. Review the result and capture findings with actionable next fixes.
  4. Apply fixes in small batches and rerun the relevant checks or review steps.
  5. Update the plan after each iteration.
  6. Repeat until outcomes are acceptable or only explicit exceptions remain.
  7. If a dependency is missing, bootstrap it or return status: not_applicable with explicit reason and fallback path.
Required Result Format
  • status: complete | clean | improved | configured | not_applicable | blocked
  • plan: concise plan and current iteration step
  • actions_taken: concrete changes made
  • validation_skills: final skills run, or skipped with reasons
  • verification: commands, checks, or review evidence summary
  • remaining: top unresolved items or none

For setup-only requests with no execution, return status: configured and exact next commands.

Load References

  • read references/test-planning.md first
  • open references/automated-testing.md for deeper strategy and trade-offs
  • for broader .NET implementation flow, use mcaf-dotnet
  • for .NET framework-specific mechanics, use exactly one of mcaf-dotnet-xunit, mcaf-dotnet-tunit, or mcaf-dotnet-mstest

Example Requests

  • "Add tests for this bugfix."
  • "Protect this refactor with regression coverage."
  • "Choose the right test level for this API change."

© 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 .codex/skills/mcaf-testing of managedcode/Storage.

  • SKILL.md
  • references/automated-testing.md
  • references/test-planning.md

Open the folder on GitHubat commit 5d32121

Compare with similar skills

Mcaf Testing 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 Testing compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Mcaf Testing this skillmanagedcode/Storage138—~1.2kAutomated safety check: PassMIT
Write Vibe Testsmistralai/mistral-vibe5.1k—~1.2kAutomated safety check: PassApache-2.0
Akka.NET Testing PatternsAaronontheweb/dotnet-skills1.2k1 repos~2.4kAutomated safety check: PassMIT
MAUI UI Test Shard Rebalancerdotnet/maui23k—~995Automated safety check: PassMIT
Verify Tests Catch the Bugdotnet/maui23k—~2.7kAutomated safety check: PassMIT
Dotnet Testingnovotnyllc/dotnet-artisan233—~972Automated safety check: PassMIT

Similar skills

  • Write Vibe Tests

    mistralai/mistral-vibe

    Official

    Guides writing or refactoring tests for the Mistral Vibe CLI agent so they check behavior through stable boundaries, like tool invocation or saved session shape, instead of internal calls.

    5.1k GitHub stars~1.2k tokensUpdated yesterday
    Testing & QAAuto-check passed

  • Akka.NET Testing Patterns

    Aaronontheweb/dotnet-skills

    Shows how to test Akka.NET actors with Akka.Hosting.TestKit: swapping services for fakes, using TestProbes, and checking persistence, plus when the older TestKit still fits.

    1.2k GitHub starsUsed in 1 repo~2.4k tokens
    Testing & QAAuto-check passed

  • MAUI UI Test Shard Rebalancer

    dotnet/maui

    Official

    Splits a slow .NET MAUI UI-test category into method-level CI shards sized from historical Azure DevOps timings so each job fits a target duration.

    23k GitHub stars~995 tokensUpdated today
    Testing & QAAuto-check passed

  • Verify Tests Catch the Bug

    dotnet/maui

    Official

    Confirms that newly added tests actually fail without the fix, auto-detecting UI, device, unit or XAML tests and running the matching runner.

    23k GitHub stars~2.7k tokensUpdated today
    Testing & QAAuto-check passed

  • Dotnet Testing

    novotnyllc/dotnet-artisan

    Defines .NET test strategy and implementation patterns across xUnit v3 (Facts, Theories, fixtures, IAsyncLifetime), integration testing (WebApplicationFactory, Testcontainers), Aspire testing…

    233 GitHub stars~972 tokensUpdated 1 mo ago
    Testing & QAAuto-check passed

  • Csharp Testing

    affaan-m/ECC

    C and .NET testing patterns with xUnit, FluentAssertions, mocking, integration tests, and test organization best practices.

    274k GitHub starsUsed in 1 repo~2.2k tokens
    Testing & QAAuto-check passed

More from managedcode/Storage

All 41 skills in this repo

  • Mcaf Adr Writing

    managedcode/Storage

    Create or update an ADR under docs/ADR/ for architectural decisions, dependency changes, data-model changes, or cross-cutting policy shifts.

    138 GitHub stars~951 tokensUpdated today
    Auto-check passed

  • Mcaf Agile Delivery

    managedcode/Storage

    Shape delivery workflow around backlog quality, roles, ceremonies, and engineering feedback.

    138 GitHub stars~883 tokensUpdated today
    Auto-check passed

  • Mcaf Architecture Overview

    managedcode/Storage

    Create or update docs/Architecture.md as the global architecture map for a solution.

    138 GitHub stars~950 tokensUpdated today
    Auto-check passed

  • Mcaf CI CD

    managedcode/Storage

    Design or refine CI/CD workflows, quality gates, release flow, and safe AI-assisted pipeline authoring.

    138 GitHub stars~981 tokensUpdated today
    Auto-check passed

  • Mcaf Code Review

    managedcode/Storage

    Prepare for, perform, or tighten code review workflow: PR scope, review checklist, reviewer expectations, and merge hygiene.

    138 GitHub stars~957 tokensUpdated today
    Auto-check passed

  • Mcaf Devex

    managedcode/Storage

    Improve developer experience for multi-component solutions: onboarding, F5 contract, cross-platform tasks, local inner loop, and reproducible setup.

    138 GitHub stars~911 tokensUpdated today
    Auto-check passed

Works with

Categories

Questions about Mcaf Testing

What does Mcaf Testing do?

Add or update automated tests for a change using the repository’s verification rules in AGENTS.md. Mcaf Testing is an agent skill from managedcode/Storage.md.

When should I use Mcaf Testing?

Mcaf Testing fits situations like: implementing a feature; regression test; prefer stable integration/API/UI coverage and pull deeper test strategy from the bundled references.

How do I install Mcaf Testing in Claude Code?

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

How do I install Mcaf Testing in Codex?

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

Can I use Mcaf Testing 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/Storage --skill mcaf-testing -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-testing, .gemini/skills/mcaf-testing, .github/skills/mcaf-testing and .opencode/skills/mcaf-testing in your project.

What does Mcaf Testing need to run?

SKILL.md names no scripts, command-line tools or credentials: Mcaf Testing is instructions for the agent only. Compatibility (from SKILL.md): Requires the repository’s build and test tooling; uses commands from root or local `AGENTS.md`..

Does Mcaf Testing 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 Testing 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 Testing use?

Mcaf Testing 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 Testing use?

About 1.2k tokens (SKILL.md is roughly 4.7k 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 3.2k tokens, read only when the agent opens those files.

What are the alternatives to Mcaf Testing?

Skills that share tags, products or a category with Mcaf Testing: Write Vibe Tests (mistralai/mistral-vibe, 5.1k stars), Akka.NET Testing Patterns (Aaronontheweb/dotnet-skills, 1.2k stars), MAUI UI Test Shard Rebalancer (dotnet/maui, 23k stars) and Verify Tests Catch the Bug (dotnet/maui, 23k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Mcaf Testing?

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

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