CtrlK
BlogDocsLog inGet started
Tessl Logo

donedone

DoneDone integration. Manage Projects, Companies. Use when the user wants to interact with DoneDone data.

61

Quality

72%

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/donedone/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

82%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, and it is well structured for its size, though it carries minor prose padding and inlines bulk reference material that could eventually move to a separate file.

DimensionReasoningScore

Conciseness

The body is mostly lean with executable commands, but carries minor padding such as the product background paragraph and "so you can focus on the integration logic rather than auth plumbing".

4 / 5

Actionability

It provides copy-paste-ready commands for install, login, connection ensure/poll, action search/run, and proxying, plus a concrete popular-actions table covering the common cases.

5 / 5

Workflow Clarity

The connection flow is clearly sequenced with state-based checkpoints (READY / CLIENT_ACTION_REQUIRED / error) and a poll-again feedback loop, but the connect→search→run path is spread across sections without one unified numbered sequence.

4 / 5

Progressive Disclosure

Sections are well organized with no nested references, but all content lives in a single file with a ~20-row actions table inlined that could be split into a reference file if the skill grows.

4 / 5

Total

17

/

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 names the product and a couple of actions and includes a usable trigger clause, but it undersells the skill's real breadth (tasks, conversations, mailboxes, releases) and relies on generic trigger language.

Suggestions

Expand the action list to reflect full coverage, e.g. "Manage Projects, Companies, Tasks, Conversations, and Mailboxes in DoneDone."

Make the trigger clause concrete: "Use when the user wants to manage DoneDone projects, tasks, issues, or conversations."

Add natural synonyms users actually say (tasks, issues, bugs, tickets) to improve trigger matching.

DimensionReasoningScore

Specificity

"Manage Projects, Companies" names the domain plus one to two concrete actions, but coverage is thin (no mention of tasks, conversations, mailboxes, or releases seen later in the body).

3 / 5

Completeness

It states a clear "what" (Manage Projects, Companies) and an explicit "when" ("Use when the user wants to interact with DoneDone data"), though the trigger clause is generic rather than enumerating concrete situations.

4 / 5

Trigger Term Quality

It surfaces "DoneDone", "Projects", and "Companies", but misses common natural variations users would say (tasks, issues, bugs, tickets) and file/URL cues.

3 / 5

Distinctiveness Conflict Risk

"DoneDone integration" targets a named product niche with distinct triggers, with only minor overlap risk against generic issue-tracker skills.

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.