r-testing
R package testing with testthat 3rd edition. Use when writing R tests, fixing failing tests, debugging errors, or reviewing coverage—e.g., "write testthat tests", "fix failing R tests", "snapshot testing", "test coverage".
90
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
89%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a strong skill description that excels in completeness and distinctiveness. It clearly identifies its niche (R/testthat 3rd edition) and provides excellent trigger terms that users would naturally use. The main weakness is that the capability description could be more specific about concrete actions beyond the general categories of writing, fixing, debugging, and reviewing.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (R package testing with testthat) and mentions some actions (writing tests, fixing tests, debugging errors, reviewing coverage), but doesn't list multiple concrete specific actions like 'create test fixtures', 'mock functions', or 'generate test reports'. | 2 / 3 |
Completeness | Clearly answers both what (R package testing with testthat 3rd edition) and when (writing R tests, fixing failing tests, debugging errors, reviewing coverage) with explicit 'Use when' clause and concrete example trigger phrases. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'write testthat tests', 'fix failing R tests', 'snapshot testing', 'test coverage', plus implicit triggers like 'R tests' and 'testthat'. These are phrases users would naturally use when needing this skill. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with clear niche: specifically R language, testthat framework, 3rd edition. The trigger terms like 'testthat', 'R tests', and 'snapshot testing' are unlikely to conflict with general testing skills or other language testing frameworks. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
85%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a strong, well-structured skill that provides actionable R testing guidance with executable code examples. The workflow clarity is excellent with explicit validation checkpoints and consequences for skipping steps. Minor verbosity in explanatory sections could be trimmed, but overall the content earns its token budget.
Suggestions
Trim explanatory text in 'Initial Setup' section - Claude knows what usethis::use_testthat creates; just show the command
Condense the 'Special files' bullet points - the parenthetical explanations add tokens without adding actionable value
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Generally efficient but includes some unnecessary explanation (e.g., explaining what setup-*.R files do, describing what usethis::use_testthat creates). Some sections like 'Design Principles' could be tightened while preserving clarity. | 2 / 3 |
Actionability | Provides fully executable R code examples throughout, including complete test patterns, withr usage, fixture creation, and custom expectations. All code is copy-paste ready with realistic examples. | 3 / 3 |
Workflow Clarity | Clear three-level testing hierarchy (micro/mezzo/macro), explicit validation steps for snapshots ('IMMEDIATELY after creating snapshots: testthat::snapshot_review'), and strong emphasis on feedback loops with warnings about consequences of skipping steps. | 3 / 3 |
Progressive Disclosure | Excellent structure with clear overview sections and well-signaled one-level-deep references to specialized topics (advanced.md, bdd.md, snapshots.md, fixtures.md). Each reference includes when to load it. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Reviewed
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.