CtrlK
BlogDocsLog inGet started
Tessl Logo

context-awareness

How the agent knows what the user is looking at. Use when exposing UI state to the agent, implementing view-screen or navigate actions, wiring navigation state, or debugging agent context issues.

62

Quality

75%

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 ./.agents/skills/context-awareness/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

65%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

Highly actionable with excellent executable code and clear guardrails, but it is a monolithic ~200-line document with motivational padding and no progressive disclosure into bundle files, and lacks explicit validation checkpoints.

Suggestions

Trim the 'Why' section to one line or drop it; the Rule already conveys the purpose without motivational framing Claude can infer.

Split detailed material (Jitter Prevention internals, the Gold-Standard mail template walkthrough) into reference files under references/ and link to them from the body so SKILL.md stays an overview.

Add an explicit verification step to the navigate/view-screen flow (e.g., confirm the consumed command was deleted, or assert view-screen returns data for the active view) so the workflow has a checkpoint.

DimensionReasoningScore

Conciseness

Mostly efficient with dense, executable code, but the 'Why' section ('the agent is blind', 'feels like a collaborator rather than a disconnected chatbot') is motivational framing Claude could infer, and the ~200-line body could be tightened — matching 'mostly efficient but includes some unnecessary explanation'.

2 / 3

Actionability

Provides complete, copy-paste-ready TypeScript/TSX for the UI hook, agent-side reads, view-screen, navigate, and root.tsx sync — fully executable, specific examples.

3 / 3

Workflow Clarity

Core patterns are numbered 1-4 with agent-side/UI-side breakdowns and Do/Don't guardrails, but there are no explicit validation or verification checkpoints, matching 'steps listed but validation gaps; checkpoints missing'.

2 / 3

Progressive Disclosure

Sections are well-organized and Related Skills are signaled, but everything (detailed patterns, jitter-prevention internals, gold-standard example) is inline with no bundle files to offload detail into — content that could be split is inline.

2 / 3

Total

9

/

12

Passed

Description

85%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A specific, well-targeted description with an explicit Use-when trigger clause and third-person voice. The only weakness is trigger phrasing that uses product-specific jargon rather than the most natural user wording.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'exposing UI state to the agent, implementing view-screen or navigate actions, wiring navigation state, or debugging agent context issues' — matching the anchor for several specific concrete actions.

3 / 3

Completeness

Clearly states what ('How the agent knows what the user is looking at') and an explicit 'Use when...' clause with multiple triggers, satisfying both what and when.

3 / 3

Trigger Term Quality

Relevant triggers are present, but phrasing leans framework-specific jargon ('wiring navigation state', 'view-screen or navigate actions') rather than the natural terms a user would say, so it sits at 'some relevant keywords but missing common variations' rather than the top anchor.

2 / 3

Distinctiveness Conflict Risk

Targets a clear niche (agent UI context awareness) with distinct triggers unlikely to fire for unrelated skills.

3 / 3

Total

11

/

12

Passed

Validation

81%

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

Validation13 / 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

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

13

/

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.