CtrlK
BlogDocsLog inGet started
Tessl Logo

apptweak

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

59

Quality

68%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/apptweak/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 content is highly actionable with executable commands and a clear connection workflow including feedback loops. The main weakness is mild verbosity in the intro and a few padded phrases that could be trimmed for token efficiency.

Suggestions

Trim the ASO platform intro and phrases like "so you can focus on the integration logic rather than auth plumbing" to reduce token overhead.

Add an explicit validation/checkpoint for action results (e.g. inspect the `output` field and handle error states) to complete the workflow feedback loop.

Fix the typo "burn less tokens" -> "use fewer tokens" in the Best practices section.

DimensionReasoningScore

Conciseness

The body is mostly efficient with dense command examples, but includes unnecessary explanation Claude already knows (the ASO platform intro) and padded phrasing like "so you can focus on the integration logic rather than auth plumbing" and "burn less tokens", matching the 'mostly efficient but includes some unnecessary explanation' anchor; not a 4 due to several trimmable passages.

3 / 5

Actionability

Provides fully executable, copy-paste-ready commands across install, login, connection ensure, action list/run, and proxy requests, plus a flags table covering the common cases, matching the 'fully executable; copy-paste ready' anchor.

5 / 5

Workflow Clarity

The connection flow is a clear sequence with explicit state checks (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) and a polling feedback loop, but action-result validation is only implicit, matching the 'clear sequence with most checkpoints present; minor validation gaps' anchor; not a 5 since not every step has an explicit checkpoint.

4 / 5

Progressive Disclosure

A single SKILL.md is well organized into clear sections (Overview, Working with AppTweak, Popular actions, Best practices) with no nested references and no bundle files, matching the 'good structure; most content appropriately placed' anchor; not a 5 because the proxy/API material could be split out as the file grows.

4 / 5

Total

16

/

20

Passed

Description

62%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 covers both what and when with a clear app-specific niche, but its action verbs and trigger terms are generic. Adding concrete ASO actions and natural trigger phrases (keywords, competitors, rankings) would raise it from good to strong.

Suggestions

Replace generic verbs with concrete ASO actions, e.g. "Research keywords, analyze competitors, and track app rankings in the App Store and Google Play".

Expand the 'Use when' clause with natural trigger phrases users actually say: "Use when the user wants to research ASO keywords, analyze competitor apps, or track app store rankings."

Include file-format or domain synonyms (ASO, app store optimization, App Store, Google Play) to improve trigger term coverage.

DimensionReasoningScore

Specificity

Names the AppTweak domain plus 2-3 actions ("Manage data, records, and automate workflows"), but the verbs are generic rather than concrete ASO actions, matching the 'names domain and 1-2 concrete actions' anchor; not a 4 since nothing is as specific as 'extract keywords' or 'analyze competitors'.

3 / 5

Completeness

States both what ("AppTweak integration. Manage data, records, and automate workflows") and when ("Use when the user wants to interact with AppTweak data"), but the trigger is generic rather than concrete, matching the 'has both what and when; when could be more explicit' anchor; not a 5 due to lack of concrete trigger phrases.

4 / 5

Trigger Term Quality

Includes "AppTweak", "data", "records", and "workflows" as keywords, but misses common ASO variations users would say (keywords, competitors, rankings, app store, ASO), fitting the 'some relevant keywords but missing common variations' anchor.

3 / 5

Distinctiveness Conflict Risk

The named app (AppTweak) establishes a clear niche with low conflict risk, but the generic action verbs (manage data, records, workflows) create minor overlap potential, matching the 'mostly distinct; minor overlap risk' anchor.

4 / 5

Total

14

/

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.