CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

test-integration

Run and extend Phoenix's executable integration documentation checks. Use when changing an integration doc, its runnable example, or the CI harness.

Quality

81%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

75%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, information-dense instruction skill for a CI harness: concrete commands, clear local-run and add-integration workflows, and an explicit verify-before-enabling checkpoint. It falls just short of top marks on actionability and disclosure because credential/schemas for new entries are referenced but not shown.

Suggestions

Show the `integrations.json` entry schema (or a minimal example entry with the stable id, language, env vars, setup rules, output expectations, and verifier fields) so step 2 of 'Add an integration' is executable without reading the config.

Name the required credential environment variables (or point to where in `integrations.json` they are declared) in the local-run section instead of 'set the credentials required by the selected integration'.

Re-indent the skip-configuration paragraph under step 3 (or move it under step 3) so the numbered 'Add an integration' list reads as one continuous sequence.

DimensionReasoningScore

Conciseness

The body is dense with repo-specific facts Claude cannot infer (shard behavior, `llama3.2:1b`, per-language SDK choices, skip semantics) with almost no conceptual padding. A few spots could be tightened — e.g. the CI behavior bullet list and the run-on lint-only paragraph ('bytecode-compiled, JavaScript is syntax-checked, TypeScript is compiled with tsc, Go is compiled with go vet...') — which fits anchor 4 rather than 5.

4 / 5

Actionability

Gives copy-pasteable commands (`make test-integration-docs`, `make test-integration-docs INTEGRATION_DOCS_ARGS="--doc ..."`), a concrete endpoint (`http://127.0.0.1:6006`), `PHOENIX_ENDPOINT`, and an enumerated checklist of `integrations.json` entry fields. Minor gaps remain — required credential env vars and the setup-rule/verifier schema are named but never specified, so it is 'mostly executable with minor gaps' (anchor 4), not fully self-sufficient (anchor 5).

4 / 5

Workflow Clarity

Both workflows are clearly sequenced: local runs list prerequisites (start Phoenix, set credentials, run make) and 'Add an integration' is a numbered 1-4 process ending in an explicit validation step ('Run the document locally... inspect both the generated report and the spans in its unique project before enabling it in CI'). It lacks the explicit error-recovery feedback loop of anchor 5, and the unindented skip-config paragraph between steps 3 and 4 visually breaks the list, so anchor 4 is the best fit.

4 / 5

Progressive Disclosure

Three clear sections appropriately organize the content, and referenced paths (`integrations.json`, `INTEGRATION_CHECKS.md`, `scripts/skip_config.json`) are signaled inline with one-level-deep pointers; the bundled `scripts/skip_config.json` exists. Not anchor 5 because the skill is ~75 lines with several bundled/config files whose structure is not surfaced (no reference section or field schema), and some detail (skip-config route semantics) could live in the referenced files.

4 / 5

Total

16

/

20

Passed

Description

82%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: third-person, concise, with an explicit and concrete 'Use when' trigger clause and a clearly distinct niche. Its only weakness is that the capability statement covers just two actions rather than the fuller set the skill actually performs.

Suggestions

Expand the 'what' clause to name one or two more concrete capabilities, e.g. 'Run and extend Phoenix's executable integration documentation checks; parse runnable examples, install their dependencies, and verify spans in Phoenix'.

Add a natural synonym or two to the trigger clause, such as 'updating an integration's example' or 'changing CI routing/skip config', to broaden match coverage.

DimensionReasoningScore

Specificity

'Run and extend Phoenix's executable integration documentation checks' names the domain plus two concrete actions (run, extend), matching anchor 3 ('Names domain and 1-2 concrete actions, but not comprehensive'). It is below anchor 4 because only two actions are listed — no mention of parsing examples, installing dependencies, span verification, or routing/skip configuration.

3 / 5

Completeness

Both halves are explicit and concrete: what — 'Run and extend Phoenix's executable integration documentation checks'; when — 'Use when changing an integration doc, its runnable example, or the CI harness'. Like the anchor-5 example, it pairs a clear capability statement with an explicit multi-trigger 'Use when' clause; there is nothing left implicit, so anchor 4's 'could be more explicit' does not apply.

5 / 5

Trigger Term Quality

The 'Use when' clause supplies natural trigger phrases users of this repo would say: 'changing an integration doc, its runnable example, or the CI harness'. Good coverage but a few natural variants are missing (e.g. 'integration test', 'skip config', 'shards', 'spans'), so it fits anchor 4 rather than anchor 5's comprehensive synonym coverage, and clearly exceeds anchor 3's partial coverage.

4 / 5

Distinctiveness Conflict Risk

The niche is unambiguous — Phoenix integration documentation checks and their CI harness — and the triggers ('integration doc', 'runnable example', 'CI harness') are scoped to this exact workflow, giving minimal overlap with any other skill, matching anchor 5's 'clear niche with distinct triggers'.

5 / 5

Total

17

/

20

Passed

Validation

81%

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

Validation — 13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

referenced_paths_exist

Referenced path issues: 1 missing, 1 deeper-than-1-level

Warning

Total

13

/

16

Passed

Repository

Arize-ai/phoenix

Path

.agents/skills/test-integration/SKILL.md

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.