CtrlK
BlogDocsLog inGet started
Tessl Logo

browser-to-code

Gather context from Chrome browser tabs (Jira, Figma, docs) and hand off to a workflow skill (brainstorming, planning, debugging, code review)

64

Quality

75%

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 ./browser-to-code/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

88%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 content is highly actionable and clearly sequenced with validation checkpoints and feedback loops, and it is token-efficient. Progressive disclosure is sound for a self-contained skill but there are no bundle files to evaluate deeper reference structure.

DimensionReasoningScore

Conciseness

The body is efficient with concrete commands and error branches and assumes Claude's competence; the embedded markdown summary template and some prose add modest length that could be trimmed slightly.

4 / 5

Actionability

Fully executable guidance throughout — real chrome-cdp commands (list/shot/snap), specific AskUserQuestion usage, ready-to-show error messages, a structured summary template, and a workflow→skill mapping table cover the common cases.

5 / 5

Workflow Clarity

A clear 3-phase numbered sequence with a flow diagram, per-step validation (skip-with-warning on extraction failure, user-confirmed summary), an explicit feedback loop ('go back to Step 2'), and an 'Important' checklist.

5 / 5

Progressive Disclosure

A single self-contained SKILL.md with well-organized phase/step headers and no nested references; nothing needs splitting, but at ~130 lines with no bundle files the structure is good rather than exemplary.

4 / 5

Total

18

/

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 is specific and distinct, naming concrete sources and downstream workflows, but lacks an explicit 'Use when…' trigger clause which caps its completeness. Trigger-term coverage is good though not exhaustive.

Suggestions

Add an explicit 'Use when…' clause stating when Claude should invoke this skill (e.g., 'Use when the user has relevant context open in Chrome tabs — a Jira ticket, Figma design, or docs — and wants to start a development workflow').

Broaden trigger terms with natural synonyms users might say ('browser context', 'pull from my tabs', 'I have a ticket open').

Sharpen the action verbs beyond 'gather' and 'hand off' to better convey the extract-and-summarize pipeline.

DimensionReasoningScore

Specificity

Names the domain ('Gather context from Chrome browser tabs') plus two concrete actions ('Gather context', 'hand off'), but the action verbs are limited and not comprehensive despite helpful enumerations of sources and workflows.

3 / 5

Completeness

The 'what' is clear, but there is no explicit 'Use when…' trigger clause; per the guideline a missing trigger clause caps completeness at 3.

3 / 5

Trigger Term Quality

Includes natural terms a user would say ('Chrome browser tabs', 'Jira', 'Figma', 'docs', 'brainstorming', 'debugging', 'code review'); a few common synonyms or phrasings are missing.

4 / 5

Distinctiveness Conflict Risk

The live-Chrome-tab-context-to-workflow-handoff niche is mostly distinct with concrete tool names, with only minor overlap risk against general context-gathering skills.

4 / 5

Total

14

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
fernandezbaptiste/claude-playground-explorer
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.