CtrlK
BlogDocsLog inGet started
Tessl Logo

writer

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

48

Quality

52%

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

Quality

Content

67%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 delivers concrete, executable Membrane CLI guidance with a well-sequenced connection lifecycle and feedback loops. Its main weaknesses are a duplicated actions section, a dangling "Step 2" reference, and minor vagueness in the overview.

Suggestions

Remove or merge the "Popular actions" section, which restates the discovery command from "Searching for actions" without adding concrete popular actions.

Fix the dangling "skip to Step 2" reference by either defining Step 2 or relabeling it to the actual next section (e.g. "Searching for actions").

Trim the "Writer Overview" placeholder ("Use action names and parameters as needed") or replace it with the real action names it advertises.

DimensionReasoningScore

Conciseness

Mostly efficient CLI guidance, but the "Popular actions" section duplicates the earlier search command and the vague "Writer Overview / Use action names and parameters as needed" filler could be trimmed, fitting the mostly-efficient-but-could-be-tighter anchor.

3 / 5

Actionability

Concrete, copy-paste-ready commands with real flags populate connection, action, and proxy flows; minor gaps remain (placeholder values and the Popular actions section restating discovery rather than showing real popular actions).

4 / 5

Workflow Clarity

The connection lifecycle is clearly sequenced with a state machine and a re-poll feedback loop (CLIENT_ACTION_REQUIRED -> user acts -> poll again), but the dangling "skip to Step 2" reference (no Step 2 is ever defined) and the duplicated actions sections are minor clarity gaps.

4 / 5

Progressive Disclosure

No bundle files exist, so all content is one ~140-line file with well-organized headers and no nested references; good structure, though some detailed reference material (the clientAction schema, the proxy flag table) could be split into separate files to reach the ideal.

4 / 5

Total

15

/

20

Passed

Description

37%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 includes an explicit "Use when" trigger and names the target product, but its capability verbs are generic and Writer-agnostic, and its trigger keywords are ambiguous. It is adequate but indistinct.

Suggestions

Replace generic verbs ("Manage data, records, and automate workflows") with concrete Writer-specific actions such as creating or editing documents, paragraphs, and images.

Sharpen the trigger to user-natural phrasing tied to Writer artifacts, e.g. "Use when the user wants to create or edit Writer documents, add images or paragraphs, or enforce brand style."

Disambiguate "Writer" in the trigger so it does not collide with writing-style or general content skills.

DimensionReasoningScore

Specificity

"Manage data, records, and automate workflows" are generic abstractions with no Writer-specific concrete actions, matching the anchor that names the domain but offers only minimal or generic actions.

2 / 5

Completeness

A "Use when" clause is present, but the "what" is vague ("Manage data, records, and automate workflows") rather than a clear capability statement, which keeps it at the clear-but-weak-when level rather than a confident 4.

3 / 5

Trigger Term Quality

The trigger "Use when the user wants to interact with Writer data" plus "data, records" offers only generic keywords; the lone term "Writer" is ambiguous and the natural phrases a user would actually say are missing.

2 / 5

Distinctiveness Conflict Risk

It names the specific Writer product so it is not entirely generic, yet "manage data, records, automate workflows" overlaps heavily with many other app-integration skills, fitting the somewhat-specific-but-overlapping anchor.

3 / 5

Total

10

/

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.