CtrlK
BlogDocsLog inGet started
Tessl Logo

bolt

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

56

Quality

65%

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/bolt/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 is action-dense and well-sequenced for the Membrane CLI workflow, but it carries padding, a factually inconsistent overview, and a broken 'Step 2' cross-reference that slightly undermine clarity and token efficiency.

Suggestions

Fix the factual inconsistency: the 'Official docs' link points to Slack Bolt (api.slack.com/bolt) and the 'Bolt Overview' (Conversation/Message/Contact) contradicts the stated last-mile delivery purpose.

Remove the 'skip to Step 2' references or actually label a Step 2 heading so the sequence cross-references resolve.

Trim explanatory padding like 'so you can focus on the integration logic rather than auth plumbing' to improve token efficiency.

DimensionReasoningScore

Conciseness

The body is mostly efficient CLI commands, but includes unnecessary padding ('so you can focus on the integration logic rather than auth plumbing') and an odd filler 'Bolt Overview' list (Conversation/Message/Contact) that does not earn its tokens.

3 / 5

Actionability

It provides concrete, executable commands throughout (install, login, connection ensure, action list/run, request) with realistic flags, matching the anchor for mostly copy-paste-ready guidance with minor gaps.

4 / 5

Workflow Clarity

The install → auth → connect → poll-for-ready → search → run sequence is clear with state checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED) and a poll-again feedback loop, but the repeated 'skip to Step 2' references an unlabeled step, a minor gap.

4 / 5

Progressive Disclosure

No bundle files exist and the content is organized into clearly headed sections in a single file, giving good structure with minor organization gaps rather than a true multi-file overview-with-references layout.

4 / 5

Total

15

/

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 includes both a 'what' and an explicit 'Use when' trigger, which is its main strength, but the named actions are generic and the natural-language trigger terms are thin beyond the product name.

Suggestions

Replace generic actions ('Manage data, records') with concrete Bolt-specific capabilities (e.g. 'track shipments, manage orders, assign drivers') to lift specificity.

Add common trigger phrasings and synonyms a user would actually say (e.g. 'Bolt deliveries, shipments, order tracking') to broaden natural keyword coverage.

Disambiguate which 'Bolt' this targets in the description to reduce conflict risk with unrelated Bolt products.

DimensionReasoningScore

Specificity

Names the Bolt domain plus a few actions ('Manage data, records, and automate workflows'), but the actions are generic ('manage data') rather than concrete, matching the anchor for 1-2 named actions without comprehensive coverage.

3 / 5

Completeness

It states both what ('Bolt integration. Manage data, records, and automate workflows') and when ('Use when the user wants to interact with Bolt data'), matching the anchor where both are present but the 'when' could be more specific.

4 / 5

Trigger Term Quality

Natural terms are essentially limited to 'Bolt' and 'Bolt data'; common variations or synonyms are missing, matching the anchor for some relevant keywords but incomplete coverage.

3 / 5

Distinctiveness Conflict Risk

Naming the specific Bolt product gives it a mostly-distinct niche with minor overlap risk, though 'Bolt' is ambiguous (delivery, ride-hailing, Slack Bolt) so it does not fully reach minimal conflict risk.

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.