Agent skill

Testing

by penpot in penpot/penpot

Enforce TDD workflow and testing best practices for Penpot. An agent skill from penpot/penpot.

MPL-2.0Auto-check passedTesting & QA

Install Testing

skills CLI
$ npx skills add penpot/penpot --skill testing -a claude-code

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

GitHub CLI
$ gh skill install penpot/penpot 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/penpot/penpot.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/testing .claude/skills/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
testing
GitHub stars
61k
Token cost
~487 tokens
SKILL.md length
220 words
Files
1
Skills in repo
24
Repo updated
First seen
Licence
MPL-2.0

At a glance

Enforce TDD workflow and testing best practices for Penpot. An agent skill from penpot/penpot.

  • Works in 3 steps: RED — Write a failing test first → GREEN — Write minimal code to pass → REFACTOR — Clean up while tests stay green
  • Implementing features
  • SKILL.md covers When to Use, Workflow, Required Reading and Key Rules, plus 1 more section
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Testing is an agent skill from penpot/penpot. Enforce TDD workflow and testing best practices for Penpot. Use when implementing features, fixing bugs, or modifying behavior. Reads testing memory for full guidance.

Its SKILL.md is about 490 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Testing & QA, covering Test-driven development and Test strategy. The repository describes itself as: Penpot: The open-source design platform for Product teams that need scalable collaboration. The licence is MPL-2.0.

When your agent uses it

  • Implementing features
  • Modifying behavior

Example prompts

  • “/testing”

Workflow steps

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

  1. RED — Write a failing test first
  2. GREEN — Write minimal code to pass
  3. REFACTOR — Clean up while tests stay green

What it can do on your machine

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

Testing loads about 487 tokens when it runs. Until then it costs about 44 tokens; SKILL.md has 220 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~44
When it runs · the whole SKILL.md, loaded when a task matches
~487

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 penpot/penpot at commit fc8a126, republished under its MPL-2.0 licence (© penpot). 220 words, ~487 tokens.

Download SKILL.mdSave it as .claude/skills/testing/SKILL.md (or your agent's skills folder).
name
testing
description
Enforce TDD workflow and testing best practices for Penpot. Use when implementing features, fixing bugs, or modifying behavior. Reads testing memory for full guidance.

Testing Skill

Enforces test-driven development and Penpot testing conventions.

When to Use

  • Implementing new logic or behavior
  • Fixing any bug (reproduction test required)
  • Modifying existing functionality
  • Adding edge case handling

Skip: Pure configuration changes, documentation updates, or static content with no behavioral impact.

Workflow

Follow TDD (Red → Green → Refactor) whenever practical:

  1. RED — Write a failing test first
  2. GREEN — Write minimal code to pass
  3. REFACTOR — Clean up while tests stay green

For bug fixes, use the Prove-It Pattern: write a test that reproduces the bug, confirm it fails, implement the fix, confirm it passes.

Required Reading

Before writing any test, read:

  1. .serena/memories/testing.md — cross-cutting testing principles, TDD workflow, anti-patterns, execution discipline
  2. Module-specific testing memory for the affected module:
    • mem:common/testing — CLJC unit tests
    • mem:frontend/testing — CLJS unit tests, Playwright E2E
    • mem:backend/testing — JVM clojure.test conventions
    • mem:exporter/testing — exporter unit tests

Key Rules

  • Every behavior change needs a test
  • Test state, not interactions
  • DAMP over DRY — tests are specifications; duplication is OK if each test is self-contained and readable
  • Prefer Real > Fake > Stub > Mock
  • Arrange-Act-Assert structure
  • One assertion per concept
  • Never pipe test output to filters — redirect to file first
  • Register new test files in the module's runner/entrypoint

Verification

After completing implementation:

  • Every new behavior has a test
  • All tests pass for touched modules
  • Bug fixes include a reproduction test
  • Lint/formatter passes

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

Files

Just SKILL.md in .agents/skills/testing of penpot/penpot.

Open the folder on GitHubat commit fc8a126

Compare with similar skills

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.

Testing compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Testing this skillpenpot/penpot61k—~487Automated safety check: PassMPL-2.0
Designing TestsCloudAI-X/opencode-workflow275—~2.9kAutomated safety check: PassMIT
Perl Testingaffaan-m/ECC274k4 repos~2.8kAutomated safety check: PassMIT
Automated Test Planningtestdouble/han279—~6.7kAutomated safety check: PassMIT
Test Automatoraiskillstore/marketplace4308 repos~2.8kAutomated safety check: PassNone
Moai Ref Testing Pyramidmodu-ai/moai-adk1.2k—~1.8kAutomated safety check: PassApache-2.0

Similar skills

  • Designing Tests

    CloudAI-X/opencode-workflow

    Guides test strategy, TDD/BDD approaches, test coverage planning, and testing best practices.

    275 GitHub stars~2.9k tokensUpdated 9 mo ago
    Testing & QAAuto-check passed
  • Perl Testing

    affaan-m/ECC

    Perl testing patterns using Test2::V0, Test::More, prove runner, mocking, coverage with Devel::Cover, and TDD methodology.

    274k GitHub starsUsed in 4 repos~2.8k tokens
    Testing & QAAuto-check passed
  • Produce a standalone test plan by analyzing code for test coverage gaps and edge cases.

    279 GitHub stars~6.7k tokensUpdated 6 days ago
    Testing & QAAuto-check passed
  • Test Automator

    aiskillstore/marketplace

    Master AI-powered test automation with modern frameworks, self-healing tests, and comprehensive quality engineering.

    430 GitHub starsUsed in 8 repos~2.8k tokens
    Testing & QAAuto-check passed
  • Moai Ref Testing Pyramid

    modu-ai/moai-adk

    Test pyramid strategy, coverage targets, test patterns, and quality metrics reference.

    1.2k GitHub stars~1.8k tokensUpdated today
    Testing & QAAuto-check passed
  • Manual Test Planning

    testdouble/han

    Produce a plain-language manual test plan from the context supplied to it — an executive summary, a high-level list of named tests, and a detail section per test with the steps a person follows by…

    279 GitHub stars~2.9k tokensUpdated 6 days ago
    Testing & QAAuto-check passed

More from penpot/penpot

All 24 skills in this repo
  • Hardens code against vulnerabilities. An agent skill from penpot/penpot.

    61k GitHub starsUsed in 6 repos~4.7k tokens
    Auto-check: notes
  • Create PR

    penpot/penpot

    PR flow — open a new PR for the current task branch (validates base branch, commits, issue and push state) or update an existing PR's title or description to match Penpot conventions.

    61k GitHub stars~1.4k tokensUpdated today
    Auto-check passed
  • Bat Cat

    penpot/penpot

    A cat clone with syntax highlighting, line numbers, and Git integration - a modern replacement for cat.

    61k GitHub starsUsed in 2 repos~1.1k tokens
    Auto-check passed
  • Local CI

    penpot/penpot

    Run local CI-style checks with ./scripts/ci (lint, tests, format) per monorepo module.

    61k GitHub stars~822 tokensUpdated today
    Auto-check passed
  • Ste

    penpot/penpot

    Write or rewrite text in ASD-STE100 Simplified Technical English.

    61k GitHub stars~1.5k tokensUpdated today
    Auto-check passed
  • Code review criteria — the five review axes, core principles, severity format, and verdict for reviewing code changes.

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

Categories

Questions about Testing

What does Testing do?

Enforce TDD workflow and testing best practices for Penpot. An agent skill from penpot/penpot. Testing is an agent skill from penpot/penpot. Enforce TDD workflow and testing best practices for Penpot.

When should I use Testing?

Testing fits situations like: implementing features; modifying behavior.

How do I install Testing in Claude Code?

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

How do I install Testing in Codex?

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

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

What does Testing need to run?

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

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

Testing is published under the MPL-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Testing use?

About 487 tokens (SKILL.md is roughly 1.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Testing?

Skills that share tags, products or a category with Testing: Designing Tests (CloudAI-X/opencode-workflow, 275 stars), Perl Testing (affaan-m/ECC, 274k stars), Automated Test Planning (testdouble/han, 279 stars) and Test Automator (aiskillstore/marketplace, 430 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Testing?

penpot (a GitHub organization) maintains it in penpot/penpot, which has 60,770 GitHub stars. The repository holds 24 skills in this directory. The repository was last updated on October 7, 2026.

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