CtrlK
BlogDocsLog inGet started
Tessl Logo

docomo-digital

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

58

Quality

67%

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

Quality

Content

68%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 strong connection-state feedback loop, but it repeats the action-discovery command, has inconsistent step numbering, and omits validation before destructive action/proxy calls. Organization is solid for a reference-free skill.

Suggestions

Add a validation/confirmation checkpoint before destructive operations (e.g., prompt to confirm before `membrane action run` or proxy `-X POST/PUT/DELETE`, and verify the response state).

Fix step numbering so the connection flow reads as a clean Step 1 → Step 2 sequence (label the initial connection step "1a"/"Step 1").

De-duplicate the action-discovery command by merging "Popular actions" into "Searching for actions" to tighten the token budget.

DimensionReasoningScore

Conciseness

The body is mostly executable commands, a flag table, and operational state handling with little concept padding, but the action-list command is repeated ("Searching for actions" and "Popular actions") and the overview is slightly redundant.

4 / 5

Actionability

Copy-paste-ready CLI commands cover install, auth, connection, search, run, and proxy with a thorough flag table, but examples lean on placeholders (<actionId>, CONNECTION_ID) and never show a concrete completed DOCOMO action invocation.

4 / 5

Workflow Clarity

The connect→wait→handle-client-action→re-poll feedback loop is explicit, but step numbering is inconsistent ("Step 2"/"1b" with no Step 1/1a) and, because action runs and proxy requests support destructive verbs (POST/PUT/DELETE) with no pre-flight validation, the destructive-operations cap applies.

3 / 5

Progressive Disclosure

No bundle files exist; the single SKILL.md is well-organized with clear section headers and no nested references, but at ~143 lines with everything inline (and some redundant sections) it is not maximally lean or split.

4 / 5

Total

15

/

20

Passed

Description

66%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 answers both what and when with a clear brand-specific trigger, but its capability verbs are generic and it offers only one distinctive natural keyword. Distinctiveness is strong thanks to the proprietary niche.

Suggestions

Replace generic verbs ("Manage data, records, and automate workflows") with concrete DOCOMO Digital operations such as "list partners, fetch notifications, run reports".

Add a couple of natural trigger synonyms or related phrases users might say (e.g., "DOCOMO Digital API", "DOCOMO Digital records") to broaden keyword coverage.

DimensionReasoningScore

Specificity

"Manage data, records, and automate workflows" names the domain plus a few actions, but the verbs/nouns ("manage data", "records") are generic rather than concrete operations, matching the domain-plus-1-2-actions anchor.

3 / 5

Completeness

Both a "what" (DOCOMO Digital integration; manage data, records, automate workflows) and an explicit "when" ("Use when the user wants to interact with DOCOMO Digital data") are present, though the trigger clause is single and the actions somewhat generic.

4 / 5

Trigger Term Quality

The natural trigger "DOCOMO Digital" appears, with supporting terms "data", "records", "workflows", but there is only one distinctive keyword and no synonyms or extensions, leaving common variations missing.

3 / 5

Distinctiveness Conflict Risk

The named proprietary brand "DOCOMO Digital" forms a clear niche with a distinct trigger, making overlap with other skills unlikely despite the generic secondary verbs.

5 / 5

Total

15

/

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.