activitypub-testing

Testing patterns for PHPUnit and Playwright E2E tests. Use when writing tests, debugging test failures, setting up test coverage, or implementing test patterns for ActivityPub features.

Quality

78%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills_all/activitypub-testing/SKILL.md

Quality

Content

72%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-organized, mostly executable testing reference with clean progressive disclosure pointing to a single external doc. Its main weakness is workflow clarity: it catalogs patterns rather than sequencing a testing workflow with explicit validation checkpoints.

Suggestions

Add a short numbered testing workflow (e.g., write test from template -> run npm run env-test -> on failure isolate with --filter and debug output) with an explicit validate/fix/retry feedback loop.

Inline a minimal concrete example for the Test Data Factories and Coverage Reports sections instead of only linking out, so the body is actionable without the external file.

Trim the opening 'This skill provides guidance...' line since it restates the frontmatter description and adds no new information.

Dimension	Reasoning	Score
Conciseness	Mostly lean with executable code and command snippets and no padding about what PHPUnit/Playwright are; the opening line restates the description and a few sections are thin pointers, which keeps it just below fully efficient.	4 / 5
Actionability	Provides concrete executable commands ('npm run env-test', '--filter=test_specific_method') and copy-paste PHP/JS examples; sections like Test Data Factories and Coverage Reports defer entirely to the external reference, leaving minor gaps.	4 / 5
Workflow Clarity	The body is a pattern catalog rather than a sequenced workflow; the Debugging Tests section gives rough steps but there is no explicit multi-step sequence with validation checkpoints, which matches the anchor with implicit/missing checkpoints.	3 / 5
Progressive Disclosure	Clear overview structure with well-signaled one-level-deep references to ../../../tests/README.md using descriptive link text and section anchors, keeping key commands/examples inline and deferring detail appropriately.	5 / 5
	Total	16 / 20 Passed

Description

83%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description that clearly answers both what the skill does and when to trigger it, with concrete actions and natural trigger terms. It is well-scoped to ActivityPub testing, with only minor room to broaden keyword coverage.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions ('writing tests, debugging test failures, setting up test coverage, or implementing test patterns') tied to named tools (PHPUnit, Playwright), with minor gaps since the actions are variations of testing rather than fully distinct operations.	4 / 5
Completeness	Explicitly states both what it does ('Testing patterns for PHPUnit and Playwright E2E tests') and when to use it ('Use when writing tests, debugging test failures, setting up test coverage...') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Includes natural phrases users would say ('writing tests', 'debugging test failures', 'test coverage') plus tool names (PHPUnit, Playwright); a few synonyms or file extensions are missing so it is not fully comprehensive.	4 / 5
Distinctiveness Conflict Risk	Scoped to 'ActivityPub features' with specific tools, giving a clear niche with minimal conflict risk; minor overlap possible with a general testing skill because 'writing tests' and 'debugging test failures' are broad triggers.	4 / 5
	Total	17 / 20 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
relative_links	Relative link issues: 5 suspicious	Warning

	Total	15 / 16 Passed

Repository: Microck/ordinary-claude-skills
Path: skills_all/activitypub-testing/SKILL.md
Commit: 1056d29

Reviewed: ~8 hours ago

Table of Contents

Discovery Implementation Validation

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.