agentleFS
yu-iskwyu-iskw/coding-agent-fabric/.claude/skills/test-integration-docker/SKILL.md

test-integration-docker

Skill1 starsChanged 9 months agoApache-2.0View on GitHub

Run comprehensive integration tests using real skills (Vercel, Anthropic, Expo) in a Docker container. Managed via Makefile for standard lifecycle control.

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 3 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Verify Docker is running.

    line 13
  2. Very specific:

    Run make -C integration_tests test in the project root.

    line 15
  3. Very specific:

    Use make -C integration_tests clean if needed to prune images.

    line 17
  4. Distinctive:

    Ensure the Docker daemon is active, then execute the following command from the project root to build the image and run the full test suite:

    line 23
  5. Distinctive:

    All integration scenarios pass.

    line 51

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Integration Testing with Docker & Real Skills

This skill executes integration tests in a containerized environment using actual skill repositories from the community. It uses a Makefile to manage the build and test lifecycle.

Workflow Checklist

  • Step 1: Environment Readiness
    • Verify Docker is running.
  • Step 2: Execute Tests
    • Run make -C integration_tests test in the project root.
  • Step 3: Lifecycle Management
    • Use make -C integration_tests clean if needed to prune images.

Detailed Instructions

1. Run Integration Tests

Ensure the Docker daemon is active, then execute the following command from the project root to build the image and run the full test suite:

make -C integration_tests test-verbose

2. Standard Makefile Targets

You can also use the Makefile directly for granular control:

Build the image only

make -C integration_tests build

Clean up images

make -C integration_tests clean

Success Criteria

  • Docker image builds successfully with git and make installed.
  • caf CLI is linked and available in the container.
  • Real-world skills are cloned from GitHub (Vercel, Anthropic).
  • caf skills add successfully installs these real skills.
  • All integration scenarios pass.

Scenarios Covered

  1. CLI Health: Version and help checks.
  2. Real-World Skills (Vercel): Clones vercel-labs/agent-skills and installs skills like web-design-guidelines.
  3. Real-World Skills (Anthropic): Clones anthropics/skills and installs document skills.
  4. Subagent Verification: Lists available subagents in the clean container.
  5. Multi-Agent Matrix: Tests are executed for both Claude Code and Cursor agents.
  6. Scope Isolation: Tests are executed for both project and global scopes, verifying that global installations do not leak into the project's package.json.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.