New: 98,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

Official agent skill

Testing Guidelines

by getsentry in getsentry/toolkit

Guide for writing tests. An agent skill from getsentry/toolkit.

OfficialCustom licenceAuto-check passedTesting & QA

Install Testing Guidelines

skills CLI
$ npx skills add getsentry/toolkit --skill testing-guidelines -a claude-code

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

GitHub CLI
$ gh skill install getsentry/toolkit testing-guidelines --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/getsentry/toolkit.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/testing-guidelines .claude/skills/testing-guidelines && 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-guidelines
GitHub stars
917
Token cost
~847 tokens
SKILL.md length
441 words
Files
1
Skills in repo
4
Repo updated
First seen
Licence
Custom licence

At a glance

Guide for writing tests. An agent skill from getsentry/toolkit.

  • Works in 6 steps: Mock External Services, Use Real Fixtures → Prefer Integration Tests Over Unit Tests → Minimize Edge Case Testing → …
  • Adding new functionality
  • SKILL.md covers Core Principles, Technical Guidelines and Checklist Before Submitting
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Testing Guidelines is an agent skill from getsentry/toolkit, published by the product's own GitHub organization. Guide for writing tests. Use when adding new functionality, fixing bugs, or when tests are needed. Emphasizes integration tests, real-world fixtures, and regression coverage.

Its SKILL.md is about 850 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 Integration testing. The repository describes itself as: Agentic tooling for Sentry.

When your agent uses it

  • Adding new functionality
  • Tests are needed

Example prompts

  • “/testing-guidelines”

Workflow steps

6 steps, taken from the step headings in SKILL.md.

  1. Mock External Services, Use Real Fixtures
  2. Prefer Integration Tests Over Unit Tests
  3. Minimize Edge Case Testing
  4. Always Add Regression Tests for Bugs
  5. Cover Every User Entry Point
  6. Tests Validate Before Manual QA

What it can do on your machine

Read from SKILL.md and the folder at commit 4433449. 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 Guidelines loads about 847 tokens when it runs. Until then it costs about 48 tokens; SKILL.md has 441 words of instructions outside code blocks.

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

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

Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 441 words (~847 tokens).

“Follow these principles when writing tests.”

— opening of SKILL.md by getsentry, Custom licence
name
testing-guidelines

Read the full SKILL.md on GitHub

Files

Just SKILL.md in .agents/skills/testing-guidelines of getsentry/toolkit.

Open the folder on GitHubat commit 4433449

Used in 1 other repository

We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders. This page covers the copy in getsentry/toolkit, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Testing Guidelines 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 Guidelines compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Testing Guidelines this skillgetsentry/toolkit917—~847Automated safety check: PassCustom licence
Plugin Testingpolyipseity/obsidian-terminal948—~828Automated safety check: PassAGPL-3.0
Create Modulecartography-cncf/cartography4.1k—~2.5kAutomated safety check: PassApache-2.0
Td Integration Testmarcus/td251—~1.2kAutomated safety check: PassMIT
Integration E2E Testingshinpr/claude-code-workflows691—~3.5kAutomated safety check: PassMIT
JS-in-HTML Testingliaohch3/claude-tap3.3k—~924Automated safety check: PassMIT

Similar skills

  • Plugin Testing

    polyipseity/obsidian-terminal

    Skill for testing Obsidian plugin features in this repository.

    948 GitHub stars~828 tokensUpdated 4 days ago
    Testing & QAAuto-check passed

  • Create Module

    cartography-cncf/cartography

    Author a new Cartography intel module end-to-end (entry point, sync GET/TRANSFORM/LOAD/CLEANUP, declarative data model, integration test, schema docs).

    4.1k GitHub stars~2.5k tokensUpdated today
    Testing & QAAuto-check passed

  • Td Integration Test

    marcus/td

    Write integration tests for the td-sync admin API using the TestHarness in internal/api/testharnesstest.go.

    251 GitHub stars~1.2k tokensUpdated 7 days ago
    Testing & QAAuto-check passed

  • Integration E2E Testing

    shinpr/claude-code-workflows

    Integration and E2E test design principles, ROI calculation, test skeleton specification, and review criteria.

    691 GitHub stars~3.5k tokensUpdated 6 days ago
    Testing & QAAuto-check passed

  • JS-in-HTML Testing

    liaohch3/claude-tap

    Tests JavaScript embedded in an HTML file in two layers: pytest checks of the logic ported to Python, and Playwright runs in a real browser for the DOM.

    3.3k GitHub stars~924 tokensUpdated 15 days ago
    Testing & QAAuto-check passed

  • Crosvm Testing

    google/crosvm

    Official

    Skill to assist with running tests and managing test VMs in the crosvm repository.

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

More from getsentry/toolkit

  • Logging Observability

    getsentry/toolkit

    Official

    Review code for correct logging and error handling patterns.

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

  • MCP QA

    getsentry/toolkit

    Official

    QA MCP tool changes with local CLI and real agent clients. An agent skill from getsentry/toolkit.

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

  • MCP Audit

    getsentry/toolkit

    Official

    Audit MCP servers for protocol compliance, metadata drift, and compatibility regressions.

    917 GitHub stars~1.5k tokensUpdated today
    Auto-check passed

Categories

Questions about Testing Guidelines

What does Testing Guidelines do?

Guide for writing tests. An agent skill from getsentry/toolkit. Testing Guidelines is an agent skill from getsentry/toolkit, published by the product's own GitHub organization. Guide for writing tests.

When should I use Testing Guidelines?

Testing Guidelines fits situations like: adding new functionality; tests are needed.

How do I install Testing Guidelines in Claude Code?

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

How do I install Testing Guidelines in Codex?

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

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

What does Testing Guidelines need to run?

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

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

Testing Guidelines has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.

How many tokens does Testing Guidelines use?

About 847 tokens (SKILL.md is roughly 3.4k 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 Guidelines?

Skills that share tags, products or a category with Testing Guidelines: Plugin Testing (polyipseity/obsidian-terminal, 948 stars), Create Module (cartography-cncf/cartography, 4.1k stars), Td Integration Test (marcus/td, 251 stars) and Integration E2E Testing (shinpr/claude-code-workflows, 691 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Testing Guidelines?

getsentry (a GitHub organization, an official publisher) maintains it in getsentry/toolkit, which has 917 GitHub stars. The repository holds 4 skills in this directory. The repository was last updated on October 8, 2026.

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