CtrlK
BlogDocsLog inGet started
Tessl Logo

debugbear

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

49

Quality

54%

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/debugbear/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 mostly executable, well-sequenced guidance with genuine validation checkpoints around connection state, but carries some rhetorical padding and a thin Overview section that could be tightened for token efficiency.

Suggestions

Trim rhetorical padding such as "so you can focus on the integration logic rather than auth plumbing" and "This is the fastest way to get a connection" to improve conciseness.

Fix the broken step numbering (the text references "Step 2" without a labeled Step 1/Step 2) so the workflow sequence is unambiguous.

Replace or supplement the placeholder-only examples (CONNECTION_ID, <actionId>, QUERY) with at least one fully concrete end-to-end example to lift actionability toward 5.

DimensionReasoningScore

Conciseness

The body is mostly executable commands, but trimmable padding remains ("focus on the integration logic rather than auth plumbing", "This is the fastest way to get a connection…", and an uninformative DebugBear Overview stub listing only Test/Result/Check).

3 / 5

Actionability

Concrete, runnable commands appear throughout (login, connection ensure/get with --wait, action list/run, request with a flags table), with only minor gaps from placeholders like CONNECTION_ID and <actionId> instead of a worked end-to-end example.

4 / 5

Workflow Clarity

A clear install → auth → connect → poll → search → run → proxy sequence exists with real validation checkpoints (poll until not BUILDING, re-poll after user action, inspect error on CONFIGURATION_ERROR/SETUP_FAILED), though broken "Step 1/Step 2" referencing muddies the numbering.

4 / 5

Progressive Disclosure

Content is organized under clear section headers with CLI detail appropriately inline for an integration skill and no nested references, but the weak Overview stub and inlined bulkier proxy/flags material leave minor organization gaps that prevent a 5.

4 / 5

Total

15

/

20

Passed

Description

41%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 identifies the product and includes a Use-when clause, but its actions and triggers are generic, lacking the concrete DebugBear-specific capabilities and natural user phrases that would make it sharply actionable.

Suggestions

Replace generic verbs ("manage data, records, automate workflows") with concrete DebugBear capabilities such as monitoring page speed, SEO, and uptime, and retrieving test results.

Expand the trigger clause with natural user phrases, e.g. "Use when the user wants to check website performance, review DebugBear test results, or monitor uptime and SEO metrics."

Add domain-specific terms and likely synonyms (website monitoring, Lighthouse scores, Core Web Vitals) to improve trigger-term coverage and distinctiveness.

DimensionReasoningScore

Specificity

"Manage data, records, and automate workflows" names the DebugBear domain but the actions are generic with no product-specific concrete operations (no page-speed, SEO, uptime, monitoring, tests/results).

2 / 5

Completeness

Both a vague "what" (manage data/records/workflows) and an explicit "when" ("Use when the user wants to interact with DebugBear data") are present, but neither offers concrete trigger phrases, capping it below 4.

3 / 5

Trigger Term Quality

Triggers are essentially just the product name "DebugBear" and "interact with DebugBear data"; the natural phrases a user would say (website monitoring, page speed, uptime, SEO) are missing.

2 / 5

Distinctiveness Conflict Risk

Tying the description to the named product "DebugBear" gives it a clear niche and low conflict risk, though the generic body actions keep it from a 5.

4 / 5

Total

11

/

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.