CtrlK
BlogDocsLog inGet started
Tessl Logo

anonyflow

AnonyFlow integration. Manage data, records, and automate workflows. Use when the user wants to interact with AnonyFlow data.

58

Quality

67%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/anonyflow/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

68%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.

The body is highly actionable with executable commands and a clear connection-state workflow, but it pads a few filler sections and omits validation steps for its destructive and batch operations. Organization is solid for a single-file skill with only minor navigation gaps.

Suggestions

Add a validation/verification step before destructive and batch actions, e.g. confirm vault/token existence and preview affected items before running delete-vault, delete-token, batch-tokenize, or batch-detokenize.

Remove the low-value 'AnonyFlow Overview' bullet list and 'Use action names and parameters as needed.' filler, and de-duplicate the best-practices section against the earlier 'Discover before you build' guidance.

Fix the 'Skip to Step 2' references by labeling the 'Searching for actions' section as Step 2, or reword to 'skip to Searching for actions'.

DimensionReasoningScore

Conciseness

The bulk is lean command-focused documentation, but the 'AnonyFlow Overview' bullet list, the filler line 'Use action names and parameters as needed.', and best-practices items that restate earlier guidance are unnecessary and could be tightened.

3 / 5

Actionability

It provides copy-paste-ready, fully executable commands throughout (install, login, connection ensure, action list/run, request) plus flag and action tables covering the common cases, matching the score-5 anchor.

5 / 5

Workflow Clarity

The connection workflow has explicit state-polling checkpoints (BUILDING/READY/CLIENT_ACTION_REQUIRED), but destructive and batch actions (delete-vault, delete-token, batch-tokenize) are presented with no validation or verification steps, which caps workflow clarity at 3 per the batch/destructive guidance.

3 / 5

Progressive Disclosure

It is a single well-sectioned file with clear headers and no external references, but the inlined 16-row action catalog and a broken 'Skip to Step 2' cross-reference (no matching Step 2 header) are minor organization gaps keeping it below 5.

4 / 5

Total

15

/

20

Passed

Description

66%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.

The description cleanly answers both what the skill does and when to use it, with strong distinctiveness from the named AnonyFlow platform. Its main weakness is generic action verbs and narrow trigger-term coverage that lack synonyms or variations.

Suggestions

Replace generic verbs with concrete capabilities, e.g. 'Tokenize and detokenize sensitive data, manage vaults, and search audit logs' instead of 'Manage data, records, and automate workflows'.

Broaden trigger terms to include natural synonyms users might say, such as 'anonymous feedback', 'PII tokenization', or 'vault management'.

DimensionReasoningScore

Specificity

Names the AnonyFlow domain plus two-to-three actions ('Manage data, records, and automate workflows'), but the verbs are generic ('manage', 'automate') rather than concrete, matching the anchor that names the domain with limited concrete actions.

3 / 5

Completeness

It states both a 'what' ('AnonyFlow integration. Manage data, records, and automate workflows.') and an explicit 'when' ('Use when the user wants to interact with AnonyFlow data.'), but the 'what' is somewhat generic so it stops short of the comprehensive score-5 anchor.

4 / 5

Trigger Term Quality

The natural trigger is essentially just 'AnonyFlow' and 'AnonyFlow data' with no synonyms or variations, so it has relevant keywords but misses common variations, fitting the score-3 anchor.

3 / 5

Distinctiveness Conflict Risk

Tying triggers to the named product 'AnonyFlow' creates a clear niche with distinct triggers and minimal overlap risk with other skills, matching the score-5 anchor.

5 / 5

Total

15

/

20

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
membranedev/application-skills
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.