CtrlK
BlogDocsLog inGet started
Tessl Logo

builtwith

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

58

Quality

68%

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

Quality

Content

75%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 a well-structured, actionable CLI integration guide with clear sequencing and state-handling feedback loops, sacrificing only minor conciseness and lacking an explicit post-run verification step.

DimensionReasoningScore

Conciseness

The body is mostly tight commands, tables, and state-handling bullets with only minor over-explanation (e.g. 'so you can focus on the integration logic rather than auth plumbing'), fitting the efficient-with-minor-trim anchor.

4 / 5

Actionability

Provides concrete, copy-paste-ready commands with parameter and flag examples throughout (login, connection ensure, action list/run, request), with only minor gaps like placeholder CONNECTION_ID/QUERY tokens.

4 / 5

Workflow Clarity

Sequences install → auth → connect → poll → search → run with an explicit state-branching loop (READY/BUILDING/CLIENT_ACTION_REQUIRED) and polling feedback, though there is no explicit post-run verification checkpoint.

4 / 5

Progressive Disclosure

Well-organized into clear sections with a mostly inlined popular-actions table that is reasonable for an integration skill; no bundle files exist, but structure is good with only minor organization gaps.

4 / 5

Total

16

/

20

Passed

Description

61%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 successfully pairs a 'what' with an explicit 'Use when' clause and is anchored to a distinct named product, but its action verbs are generic and its trigger phrasing is narrow.

Suggestions

Replace generic verbs ('Manage data, records, and automate workflows') with concrete BuiltWith actions such as 'profile a website's tech stack, look up technologies, and find competitors'.

Broaden the trigger to capture natural phrasings, e.g. 'Use when the user wants to look up a website's tech stack, identify technologies, or find sites using a particular tool.'

DimensionReasoningScore

Specificity

Names the BuiltWith domain but the listed actions ('Manage data, records, and automate workflows') are generic and not concrete, matching the anchor for minimal/generic actions rather than 1-2 concrete actions.

2 / 5

Completeness

Has both a 'what' ('BuiltWith integration. Manage data, records, and automate workflows.') and an explicit 'when' ('Use when the user wants to interact with BuiltWith data.'), though the 'when' could be more specific.

4 / 5

Trigger Term Quality

Includes the natural trigger 'interact with BuiltWith data' but misses common synonyms users would say like 'tech stack', 'website technologies', or 'technology lookup'.

3 / 5

Distinctiveness Conflict Risk

Names a specific product (BuiltWith) with a clear niche and trigger, making conflict with other skills minimal.

5 / 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.