CtrlK
BlogDocsLog inGet started
Tessl Logo

add-thirdparty-service

Add a new third-party service to the privacy policy generator. Trigger when user says: "add {name} service", "add third party service", "add 3rd party service", "add new service entry", or when a user wants to contribute a new service to the app.

76

Quality

95%

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

100%Weight 40%Scale 1-3

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

The body is a tight, well-structured instruction set for a simple task: concrete paths, a complete YAML template, precise logo requirements, and a build-driven validation step. It avoids verbosity and conceptual padding entirely, leaving nothing unnecessary.

DimensionReasoningScore

Conciseness

The body is lean with no concept explanations Claude already knows — every line (file paths, a YAML template, logo specs, a build command) earns its place, matching the level-3 anchor for token efficiency.

3 / 3

Actionability

It gives concrete file paths, a copy-paste YAML template, exact logo dimensions (160×160), and a specific build command (make build), all directly executable and copy-paste ready.

3 / 3

Workflow Clarity

As a simple single-task skill, it presents a clear three-step sequence with the final "Validation" step functioning as the verification checkpoint and a warning not to edit the generated file directly, satisfying the simple-skill scoring note.

3 / 3

Progressive Disclosure

At under 50 lines with no need for external references, the well-organized sections (Workflow, YAML Entry Format, Logo Requirements, Validation) meet the level-3 anchor for simple skills with clear organization.

3 / 3

Total

12

/

12

Passed

Description

90%Weight 40%Scale 1-3

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

The description is concise, uses correct third-person voice, and explicitly pairs a concrete capability with natural-language triggers and their "when" guidance. Its only gap is that it lists a single action rather than multiple concrete actions, which leaves specificity just below the top anchor.

DimensionReasoningScore

Specificity

It names a concrete action ("Add a new third-party service") and target artifact ("privacy policy generator"), but enumerates only a single action rather than a comprehensive list, matching the level-2 anchor rather than the multiple-actions level-3 anchor.

2 / 3

Completeness

It answers both "what" (add a third-party service) and "when" through an explicit "Trigger when user says:" clause with multiple triggers, satisfying the level-3 anchor for explicit triggers.

3 / 3

Trigger Term Quality

It lists several natural phrases a user would actually say ("add third party service", "add 3rd party service", "add new service entry", "contribute a new service"), giving good coverage of common variations.

3 / 3

Distinctiveness Conflict Risk

The narrow niche (privacy policy generator + third-party service) paired with distinct trigger phrases makes it clearly distinguishable and unlikely to fire for unrelated skills.

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
nisrulz/app-privacy-policy-generator
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.