CtrlK
BlogDocsLog inGet started
Tessl Logo

live-dashboard

Notion-style team dashboard rendered as a Live Artifact. A single-page, self-contained HTML dashboard with KPIs, a 7-day sparkline, a real-time activity feed and a linked-database task table — wired to Notion via the Composio connector catalog. Refreshes on demand and when the artifact is opened. Falls back to seeded mock data when no connector is bound, so it works offline / in screenshots / in the picker preview.

65

Quality

79%

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 ./design-templates/live-dashboard/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

92%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 high-quality, actionable build spec: tightly sequenced with real validation gates and feedback loops, concrete markup/CSS/API details, and clean progressive disclosure into real reference files. Only minor editorial padding keeps conciseness just below 5.

DimensionReasoningScore

Conciseness

The body is dense and assumes Claude's competence — it does not explain what a KPI, sparkline, or Notion is — with only minor editorial padding ('Your output ships, not only renders.') that could be trimmed.

4 / 5

Actionability

Provides fully executable, copy-paste-ready guidance: exact file reads ('Read assets/template.html'), precise CSS ('font-variant-numeric: tabular-nums', 'letter-spacing -0.01em'), named classes ('<live-pill>', '.db-row.changed'), and a concrete API call 'POST /api/od/connectors/poll' with its JSON body shape.

5 / 5

Workflow Clarity

A clearly sequenced multi-step process with explicit validation checkpoints and feedback loops: a Pre-flight gating emit ('Do not emit while any P0 is unchecked'), a P0 checklist that must be quoted inline, and a Self-critique loop ('If Philosophy < 4, iterate ... before emitting').

5 / 5

Progressive Disclosure

The body is a well-organized overview with clearly signaled one-level-deep references to real bundle files — assets/template.html and references/{layouts,components,connectors,checklist}.md — each tied to a specific build step, with the bulk detail living in those files rather than inlined.

5 / 5

Total

19

/

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 is specific, concrete, and clearly distinguishes the skill's niche, but it omits an explicit 'Use when...' trigger clause, which caps completeness at 3 despite strong specificity and distinctiveness. Trigger-term coverage is good but not exhaustive.

Suggestions

Add an explicit 'Use when...' clause, e.g. 'Use when the user asks for a team or ops dashboard, a Notion-style live dashboard, or a Live Artifact showing KPIs and activity.'

Expand natural trigger terms in the description to include common synonyms like 'metrics board' or 'status dashboard'.

Lead with the primary action verb phrase (third person) before the feature list so the 'what' reads as capabilities rather than a product spec.

DimensionReasoningScore

Specificity

Lists several concrete features — 'KPIs, a 7-day sparkline, a real-time activity feed and a linked-database task table', 'wired to Notion via the Composio connector catalog', 'Falls back to seeded mock data' — with comprehensive coverage but framed as features rather than discrete actions.

4 / 5

Completeness

The 'what' is clearly and concretely answered, but there is no explicit 'Use when...' clause or equivalent trigger guidance in the description, which caps completeness at 3 per the boundary guideline.

3 / 5

Trigger Term Quality

Contains natural terms users would say — 'team dashboard', 'Notion-style', 'live dashboard', 'Live Artifact dashboard' — with good coverage and synonyms, though a few common phrasings (e.g. 'status page', 'metrics board') are absent.

4 / 5

Distinctiveness Conflict Risk

The niche is clearly defined — 'Live Artifact ... wired to Notion via the Composio connector catalog' — making it mostly distinct from generic dashboard skills with only minor overlap risk.

4 / 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
nexu-io/open-design
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.