CtrlK
BlogDocsLog inGet started
Tessl Logo

agent-page

The full-page Agent surface (/agent) with Context, Files, Connections, Jobs, and Access tabs. Use when mounting the Agent page in a template, adding an app-specific tab, surfacing context transparency, MCP servers, A2A agents, recurring jobs, or external-client connect flows in the UI.

74

Quality

93%

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

SKILL.md
Quality
Evals
Security

Quality

Content

87%

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 tight, actionable overview with exact paths, props, and a clear mounting checklist. Its only gap is the absence of explicit validation checkpoints in the mounting workflow, which is low-risk but keeps workflow clarity below the top anchor.

Suggestions

Add an explicit verification step to the mounting workflow (e.g. 'Open /agent#context and confirm the tab renders; verify the nav item and command-palette entry appear') to reach the top workflow-clarity anchor.

Clarify how to validate that built-in tabs were correctly hidden via hiddenTabs (e.g. a note on confirming the underlying capability is genuinely absent before hiding).

DimensionReasoningScore

Conciseness

Lean and information-dense with no explanation of concepts Claude already knows; uses a compact table and bullets, and every line (design principles, tab contents, mounting steps) earns its place.

3 / 3

Actionability

Provides concrete, copy-paste-ready specifics — exact paths ('packages/core/src/client/agent-page/', 'app/routes/agent.tsx'), component and prop names ('AgentTabsPage', 'showMcpServers={false}', 'extraTabs'), and hash deep-links — which is highly actionable for an instruction skill.

3 / 3

Workflow Clarity

The 'Mounting In A Template' section is a clear ordered 5-step sequence, but it lacks explicit validation checkpoints (e.g. verifying the route loads or nav appears), matching the 'steps listed but checkpoints missing or implicit' anchor rather than the top anchor.

2 / 3

Progressive Disclosure

Well-organized into clear sections (Tabs, Mounting, Scope) with one-level, clearly signaled references to sibling skills and no nested/deep references; no bundle files exist to verify, and the single-file overview is appropriately structured.

3 / 3

Total

11

/

12

Passed

Description

100%

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 concise, concrete, and uses third person with an explicit 'Use when' trigger clause. It clearly communicates both what the skill covers and when to invoke it, occupying a distinct niche.

DimensionReasoningScore

Specificity

Lists multiple concrete capabilities — 'mounting the Agent page in a template, adding an app-specific tab, surfacing context transparency, MCP servers, A2A agents, recurring jobs, or external-client connect flows' — matching the anchor for listing multiple specific concrete actions.

3 / 3

Completeness

Explicitly answers what ('The full-page Agent surface (/agent) with Context, Files, Connections, Jobs, and Access tabs') and when via an explicit 'Use when...' clause, satisfying the top completeness anchor.

3 / 3

Trigger Term Quality

Natural domain terms a developer would say ('Agent page', 'app-specific tab', 'MCP servers', 'A2A agents', 'recurring jobs', 'connect flows') give good coverage, above the 'some relevant keywords but missing variations' anchor.

3 / 3

Distinctiveness Conflict Risk

Targets a specific /agent page surface with distinct triggers, making it unlikely to fire for unrelated skills despite referencing sibling capabilities.

3 / 3

Total

12

/

12

Passed

Validation

87%

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

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

Total

14

/

16

Passed

Repository
BuilderIO/agent-native
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.