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

Testing Best Practices

by anonaddy in anonaddy/anonaddy

Laravel test design and review. An agent skill from anonaddy/anonaddy.

MITAuto-check passedTesting & QA

Install Testing Best Practices

skills CLI
$ npx skills add anonaddy/anonaddy --skill testing-best-practices -a claude-code

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

GitHub CLI
$ gh skill install anonaddy/anonaddy testing-best-practices --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/anonaddy/anonaddy.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.junie/skills/testing-best-practices .claude/skills/testing-best-practices && 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-best-practices
GitHub stars
4.9k
Used in
5 other repos
Token cost
~1k tokens
SKILL.md length
525 words
Files
10
Skills in repo
6
Repo updated
First seen
Licence
MIT

At a glance

Laravel test design and review. An agent skill from anonaddy/anonaddy.

  • Works in 5 steps: Read the code under test. Read the tests… → Select every applicable branch in the… → Report each defect in the code before… → …
  • Selecting coverage
  • SKILL.md covers Consistency First, What to Test, How to Apply and Rule Index
  • Reaches docs.phpunit.de

What it does

Testing Best Practices is an agent skill from anonaddy/anonaddy. Laravel test design and review. Use when selecting coverage, naming or structuring tests, choosing assertions or test data, isolating dependencies, testing HTTP or security boundaries, improving suite performance, or reviewing test value. Use framework guidance or search-docs for Pest and PHPUnit syntax.

Its SKILL.md is about 1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 10 other files (for example `rules/assertions.md`, `rules/endpoint-tests.md` and `rules/finding-features.md`).

It sits in Testing & QA, covering Test strategy, Backend development and Test data and fixtures. It works with Laravel. The repository describes itself as: Anonymous email forwarding. The licence is MIT.

When your agent uses it

  • Selecting coverage
  • Structuring tests
  • Choosing assertions
  • Isolating dependencies

Example prompts

  • “/testing-best-practices”

Workflow steps

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

  1. Read the code under test. Read the tests in the same directory. Identify every decision in the code.
  2. Select every applicable branch in the rule index. Read every selected rule file.
  3. Report each defect in the code before you write a test. Examples are a method with no body, a policy that no action calls, and a write…
  4. Write the tests. Run the smallest set of tests that covers the change. The tests must pass.
  5. Check every applicable item in rules/review.md and every selected rule file. Resolve every mismatch before completion.

What it can do on your machine

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

    Hosts in commands or code, which the agent is likely to contact:

    • docs.phpunit.de

    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 Best Practices loads about 1k tokens when it runs. Until then it costs about 82 tokens; SKILL.md has 525 words of instructions outside code blocks.

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

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 anonaddy/anonaddy at commit 150983e, republished under its MIT licence (© anonaddy). 525 words, ~1,046 tokens.

Download SKILL.mdSave it as .claude/skills/testing-best-practices/SKILL.md (or your agent's skills folder). This skill also uses 9 other files; get the full folder from GitHub.
name
testing-best-practices
description
Laravel test design and review. Use when selecting coverage, naming or structuring tests, choosing assertions or test data, isolating dependencies, testing HTTP or security boundaries, improving suite performance, or reviewing test value. Use framework guidance or search-docs for Pest and PHPUnit syntax.
license
MIT
metadata.author
laravel

Testing Best Practices

This skill provides rules for designing Laravel tests. Each rule file explains what to do and why. Use search-docs for Laravel API syntax. Fetch https://docs.phpunit.de/en/13.3/ for PHPUnit API syntax. This project uses PHPUnit. Follow the corresponding guidance in each rule.

Consistency First

Read nearby tests before you choose syntax and organization.

A pattern repeated throughout the project is a convention, and project conventions take precedence over this skill. Follow them and give new tests the same structure.

These rules govern the tests you write now. An existing test that follows a project convention is not defective merely because it conflicts with this skill. Do not delete or rewrite it. If the convention has drawbacks, explain them and let the user decide.

What to Test

Read this section before you write a test.

  • Test observable behavior and application contracts. A test must pass after an implementation change if the behavior stays the same.
  • Cover every changed decision and each applicable high-value failure mode. A decision is a branch, a validation, a calculation, or an authorization.
  • Exercise declarations through behavior instead of repeating their text.
  • Leave framework behavior to framework tests. Testing project configuration is not testing the framework. A constrained relationship, cast, scope, or validation rule belongs to this project.
  • Keep every test that can detect a distinct defect. When two tests detect the same defect, trim the higher-layer test to one case and report the duplication. Do not delete an existing test.
  • Write a feature test first. Write a unit test only for logic that does not use the framework.
  • Write a feature test for every behavior reachable through a request. Real-browser tests require laravel/dusk and a browser download, neither of which this project installs. Mention the package only if the user asks for a real-browser test.
  • Use the test tools that the project installs. Add a new test dependency, plugin, or browser only after the user asks for it.
Show full SKILL.md (202 more words)Show less

How to Apply

  1. Read the code under test. Read the tests in the same directory. Identify every decision in the code.
  2. Select every applicable branch in the rule index. Read every selected rule file.
  3. Report each defect in the code before you write a test. Examples are a method with no body, a policy that no action calls, and a write action with no validation. Test the actual behavior. Report the defect to the user.
  4. Write the tests. Run the smallest set of tests that covers the change. The tests must pass.
  5. Check every applicable item in rules/review.md and every selected rule file. Resolve every mismatch before completion.

Rule Index

Most changes need more than one rule file.

SubjectRule File
Test framework features that may already do the workrules/finding-features.md
File layout, test names, and groupsrules/naming.md
Arrange-act-assert and choosing the correct assertionrules/assertions.md
Endpoint coverage, authentication, authorization, tenant isolation, validation, and browser testsrules/endpoint-tests.md
Factories, test data ownership, and repeated input valuesrules/test-data.md
Fakes, mocks, outbound HTTP, time, randomness, and databasesrules/isolation.md
Escaping, injection, cross-tenant access, and privilege checksrules/security.md
Environment and CI settings for a slow suiterules/performance.md
Reviewing a test or suiterules/review.md

© anonaddy, 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 9 other files in .junie/skills/testing-best-practices of anonaddy/anonaddy.

  • SKILL.md
  • rules/assertions.md
  • rules/endpoint-tests.md
  • rules/finding-features.md
  • rules/isolation.md
  • rules/naming.md
  • rules/performance.md
  • rules/review.md
  • rules/security.md
  • rules/test-data.md

Open the folder on GitHubat commit 150983e

Used in 5 other repositories

We found 11 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 5 other GitHub owners. This page covers the copy in anonaddy/anonaddy, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Testing Best Practices 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 Best Practices compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Testing Best Practices this skillanonaddy/anonaddy4.9k5 repos~1kAutomated safety check: PassMIT
Python Testing Strategiesc0x12c/ai-toolkit106—~747Automated safety check: PassNone
Laravel TestingHoangNguyen0403/agent-skills-standard570—~989Automated safety check: PassMIT
Pest Testingliberusoftware/real-estate-laravel1121 repos~1.8kAutomated safety check: PassMIT
Pest TestingMineTrax/minetrax115—~787Automated safety check: PassMIT
133 Java Testing Acceptance Testsjabrena/plinth445—~1.3kAutomated safety check: PassApache-2.0

Similar skills

  • Python Testing Strategies

    c0x12c/ai-toolkit

    Testing patterns for FastAPI with pytest-asyncio, httpx AsyncClient, fixtures, and test data factories.

    106 GitHub stars~747 tokensUpdated 3 mo ago
    Testing & QAAuto-check passed

  • Laravel Testing

    HoangNguyen0403/agent-skills-standard

    Write Pest feature tests with RefreshDatabase, mock external services, and create test data with Eloquent Factories in Laravel.

    570 GitHub stars~989 tokensUpdated today
    Backend & APIsAuto-check passed

  • Pest Testing

    liberusoftware/real-estate-laravel

    A skill your agent uses for Pest PHP testing in Laravel projects only.

    112 GitHub starsUsed in 1 repo~1.8k tokens
    Testing & QAAuto-check passed

  • Pest Testing

    MineTrax/minetrax

    A skill your agent uses for Pest PHP testing in Laravel projects only.

    115 GitHub stars~787 tokensUpdated 1 mo ago
    Testing & QAAuto-check passed

  • 133 Java Testing Acceptance Tests

    jabrena/plinth

    A skill your agent uses when you need to implement acceptance tests from maintainer-sanitized Gherkin scenario facts for framework-agnostic Java (no Spring Boot, Quarkus, Micronaut) — confirming…

    445 GitHub stars~1.3k tokensUpdated today
    Testing & QAAuto-check passed

  • Rails Testing

    pproenca/dot-skills

    Ruby on Rails testing best practices for writing effective, maintainable test suites with RSpec.

    214 GitHub stars~2.1k tokensUpdated 1 mo ago
    Testing & QAAuto-check passed

More from anonaddy/anonaddy

  • Tailwindcss Development

    anonaddy/anonaddy

    Always invoke when the user's message includes 'tailwind' in any form.

    4.9k GitHub starsUsed in 10 repos~865 tokens
    Auto-check passed

  • Laravel Best Practices

    anonaddy/anonaddy

    Apply this skill whenever writing, reviewing, or refactoring Laravel PHP code.

    4.9k GitHub starsUsed in 13 repos~1.2k tokens
    Auto-check passed

  • Inertia Vue Development

    anonaddy/anonaddy

    Develops Inertia.js v3 Vue client-side applications. An agent skill from anonaddy/anonaddy.

    4.9k GitHub starsUsed in 3 repos~3.4k tokens
    Auto-check passed

  • Infer Conventions

    anonaddy/anonaddy

    A skill your agent uses to analyze how a Laravel application is actually written and record its conventions as shared rules.

    4.9k GitHub starsUsed in 5 repos~3.1k tokens
    Auto-check passed

  • Debugging Output And Previewing HTML Using Ray

    anonaddy/anonaddy

    A skill your agent uses when user says "send to Ray," "show in Ray," "debug in Ray," "log to Ray," "display in Ray," or wants to visualize data, debug output, or show diagrams in the Ray desktop…

    4.9k GitHub stars~2.3k tokensUpdated yesterday
    Auto-check passed

Works with

Categories

Questions about Testing Best Practices

What does Testing Best Practices do?

Laravel test design and review. An agent skill from anonaddy/anonaddy. Testing Best Practices is an agent skill from anonaddy/anonaddy. Laravel test design and review.

When should I use Testing Best Practices?

Testing Best Practices fits situations like: selecting coverage; structuring tests; choosing assertions; isolating dependencies.

How do I install Testing Best Practices in Claude Code?

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

How do I install Testing Best Practices in Codex?

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

Can I use Testing Best Practices 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 anonaddy/anonaddy --skill testing-best-practices -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-best-practices, .gemini/skills/testing-best-practices, .github/skills/testing-best-practices and .opencode/skills/testing-best-practices in your project.

What does Testing Best Practices need to run?

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

Does Testing Best Practices access the network?

SKILL.md names 1 domain. In commands or code: docs.phpunit.de; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.

Is Testing Best Practices 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 Best Practices use?

Testing Best Practices is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Testing Best Practices use?

About 1k tokens (SKILL.md is roughly 4.2k 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 Best Practices?

Skills that share tags, products or a category with Testing Best Practices: Python Testing Strategies (c0x12c/ai-toolkit, 106 stars), Laravel Testing (HoangNguyen0403/agent-skills-standard, 570 stars), Pest Testing (liberusoftware/real-estate-laravel, 112 stars) and Pest Testing (MineTrax/minetrax, 115 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Testing Best Practices?

anonaddy (a GitHub organization) maintains it in anonaddy/anonaddy, which has 4,885 GitHub stars. The repository holds 6 skills in this directory. The repository was last updated on October 6, 2026.

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