CtrlK
BlogDocsLog inGet started
Tessl Logo

chimp-rewriter

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

57

Quality

66%

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/chimp-rewriter/SKILL.md
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.

The body is an efficient, actionable guide that walks through install, auth, connection, action discovery, and proxy use with real commands and explicit connection-state checkpoints. Its main weaknesses are a thin 'Popular actions' section that promises more than it delivers and a couple of small structural and padding issues.

Suggestions

Flesh out the 'Popular actions' section with the actual common Chimp Rewriter actions (e.g. rewrite article, generate spintax) rather than only repeating the discovery command.

Trim the motivational/background sentences (e.g. the opening product overview and the 'focus on the integration logic rather than auth plumbing' aside) to tighten token efficiency.

Reconcile the numbering — the '1b. Wait for the connection' heading has no matching '1a' — or present the install-through-run flow as one explicit numbered sequence with a final verification step.

DimensionReasoningScore

Conciseness

The body is mostly lean, built around executable commands with brief explanations, though a few sentences of background/motivational padding (e.g. the product overview paragraph and 'focus on the integration logic rather than auth plumbing') could be trimmed.

4 / 5

Actionability

It provides many concrete, copy-pasteable commands (login, connection ensure, action run, request with a flag table), with minor gaps such as placeholder substitution and a 'Popular actions' section that lists only a discovery command instead of actual popular actions.

4 / 5

Workflow Clarity

There is a clear install-to-run sequence, and the connection sub-flow has explicit state checkpoints (READY / CLIENT_ACTION_REQUIRED / CONFIGURATION_ERROR) with a poll-again feedback loop, though the overall flow is not presented as one numbered sequence with a final validation.

4 / 5

Progressive Disclosure

The self-contained body (~140 lines, no bundle files) is organized with clear section headers and all content appropriately inline; minor rough edges like an orphaned '1b' sub-heading and a thin 'Popular actions' section keep it just short of ideal.

4 / 5

Total

16

/

20

Passed

Description

57%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 correctly names the target product and includes an explicit Use-when trigger, but its action language is generic boilerplate rather than the concrete rewriting/spinning capabilities of Chimp Rewriter. Tightening the action verbs to reflect the tool's actual functions would lift specificity and trigger-term quality.

Suggestions

Replace generic verbs ('Manage data, records, and automate workflows') with concrete Chimp Rewriter actions, e.g. 'Rewrite and spin articles, generate unique content variants, and automate content workflows.'

Expand trigger terms to include natural phrases users say for this tool, such as 'article rewriting', 'content spinning', 'unique content', or 'spintax'.

Make the 'Use when' clause more specific to the tool's purpose, e.g. 'Use when the user wants to rewrite or spin articles and generate unique content variants in Chimp Rewriter.'

DimensionReasoningScore

Specificity

The description names the domain ('Chimp Rewriter integration') but its actions are minimal and generic — 'Manage data, records, and automate workflows' is boilerplate rather than concrete Chimp Rewriter actions like rewriting or spinning articles.

2 / 5

Completeness

It provides both a 'what' (integration, manage data/records, automate workflows) and an explicit 'when' ('Use when the user wants to interact with Chimp Rewriter data'), though the trigger could be more specific.

4 / 5

Trigger Term Quality

'Chimp Rewriter' is the natural product keyword users would say, but common synonyms and phrases (rewriting, article spinning, generating unique content) are missing, so coverage is partial.

3 / 5

Distinctiveness Conflict Risk

Naming a specific product gives a clear niche with minimal conflict risk, though the generic action verbs ('manage data, records, automate workflows') introduce minor overlap with broad data skills.

4 / 5

Total

13

/

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.