CtrlK
BlogDocsLog inGet started
Tessl Logo

improve-app

Guided journey from a shipped app that works but feels rough to a product that fits the job, flows without friction, reads clearly, and persuades honestly. Orchestrates nine skills phase by phase - jobs-to-be-done, ux-heuristics, design-everyday-things, refactoring-ui, microinteractions, made-to-stick, influence-psychology, high-perf-browser, steve-jobs-design-review - asking the user questions at every decision point and recording results in the project docs/ folder (CUSTOMER.md, DESIGN.md, POSITIONING.md, IMPROVE-APP-PLAN.md) so the journey resumes across sessions. Use when the user wants to fix a clunky product, cut UX friction, sharpen in-app copy, or says 'the app works but feels rough'. Not for code, tests, or hardening - use improve-code-quality (fresh prototype) or remove-technical-debt (aged); no app yet, create-app; needs growth loops, grow-app; marketing-site friction, improve-website; one leaking flow, conversion-optimization. For one framework in isolation, invoke that skill directly.

75

Quality

92%

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

85%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 a well-sequenced, validation-rich orchestration guide that pushes detail into a single one-level-deep reference. Its main weakness is conciseness: the per-phase scaffolding repeats structure across nine phases and could be compressed without losing actionability.

Suggestions

Collapse the repeated per-phase Purpose/Brief/Invoke/Decide/Artifact/Done-when scaffolding into a single template applied once, then keep only phase-specific deltas, to tighten conciseness.

Factor the nine phase blocks into a compact table plus a shared 'phase block format' definition so the body reads as a journey rather than nine parallel essays.

Move the Common Mistakes table into the reference file (or behind a short pointer) to keep the main body focused on the operating workflow.

DimensionReasoningScore

Conciseness

The body is dense and directive with little padding, assuming Claude's competence by referencing frameworks by name, but the nine-phase scope plus repeated per-phase scaffolding leaves some sections that could be tightened.

4 / 5

Actionability

Each phase supplies a Purpose, a concrete Brief fallback, an Invoke line naming the skill slug, explicit decide-with-the-user options, and an Artifact spec with section headings and table columns; mostly executable with minor gaps around literal commands.

4 / 5

Workflow Clarity

Nine phases are sequenced via the Journey Map with eight Operating Rules each ending in an explicit 'Done when' checkpoint, GATE constraints, skip heuristics, resume-first and evidence-before-redesign feedback loops, and an exit checklist.

5 / 5

Progressive Disclosure

SKILL.md stays an overview while the full document skeletons are correctly split into references/artifact-templates.md, which is referenced once, clearly signaled, one level deep, and confirmed present in the bundle.

5 / 5

Total

18

/

20

Passed

Description

100%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 is specific, trigger-rich, and complete with explicit use-when and not-for guidance that cleanly separates it from sibling skills. It is one of the strongest possible descriptions, though its length is on the heavier side given how much routing detail it carries.

DimensionReasoningScore

Specificity

Lists multiple concrete actions (fix a clunky product, cut UX friction, sharpen in-app copy, persuade honestly) and details the nine-phase orchestration with artifact destinations, giving comprehensive coverage.

5 / 5

Completeness

Explicitly answers both what (a guided nine-phase journey from a rough-but-working app to a polished product) and when (an explicit 'Use when' clause with concrete triggers) plus a not-for boundary.

5 / 5

Trigger Term Quality

Includes natural phrases users actually say ('the app works but feels rough', 'fix a clunky product', 'cut UX friction') plus synonyms and the explicit trigger sentence, covering the term space comprehensively.

5 / 5

Distinctiveness Conflict Risk

Names and routes away from sibling skills (improve-code-quality, remove-technical-debt, create-app, grow-app, improve-website, conversion-optimization) and directs single-framework cases to invoke that skill directly, leaving minimal conflict risk.

5 / 5

Total

20

/

20

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
wondelai/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.