client-methods

Client method surface rules. Use when wiring browser/client code to actions, application state, framework routes, app APIs, uploads, auth, or settings.

Quality

92%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

100%

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

The content is lean, highly actionable, and well-structured with concrete import paths, executable examples, and a clearly signaled one-level reference to a real bundle file. It assumes Claude's competence throughout and avoids restating known concepts, making it a strong rule-style skill body.

Dimension	Reasoning	Score
Conciseness	The body is lean and prescriptive across Rule, Why, How, Exceptions, Don't, Related Skills, and References with no padding or restating of concepts Claude already knows; every token earns its place.	3 / 3
Actionability	Provides a concrete need-to-method table with exact import paths (e.g. 'useActionQuery ... from @agent-native/core/client/hooks'), executable TS snippets, and a precise callAction signature 'callAction(name, params, { method, signal, timeoutMs })' — copy-paste ready.	3 / 3
Workflow Clarity	A clear three-step sequence ('Look for an existing client API first' → 'add the narrowest helper at the boundary' → 'Teach the helper, not the route') with explicit placement rules and focused test guidance; this rule-based skill needs no destructive/batch validation checkpoint.	3 / 3
Progressive Disclosure	Well-organized overview body with a single one-level-deep reference ('references/legacy-client-fetch-audit-2026-06-03.md', a confirmed real file) that is clearly signaled and described, matching the score-3 anchor.	3 / 3
	Total	12 / 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.

The description is concise, third-person, and pairs a clear 'what' with an explicit 'Use when' trigger clause covering concrete surface areas. Specificity is strong on wiring targets but reads as enumerated surfaces rather than discrete concrete actions, capping that dimension at 2.

Dimension	Reasoning	Score
Specificity	Quotes 'wiring browser/client code to actions, application state, framework routes, app APIs, uploads, auth, or settings' — names the domain and enumerates surfaces, but these are wiring targets rather than multiple distinct concrete actions as in the score-3 anchor.	2 / 3
Completeness	Clearly answers both: 'what' via 'Client method surface rules' and 'when' via the explicit 'Use when wiring browser/client code to ...' clause, satisfying the score-3 anchor.	3 / 3
Trigger Term Quality	The explicit 'Use when' clause covers natural trigger terms a user or agent would name — 'actions, application state, framework routes, app APIs, uploads, auth, or settings' — giving good coverage of likely phrasings.	3 / 3
Distinctiveness Conflict Risk	Scoped to a clear niche (client method surface rules) with triggers tied to specific surface areas, making it unlikely to fire for an unrelated skill.	3 / 3
	Total	11 / 12 Passed

Validation

81%

Warnings & errors only

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

Validation — 13 / 16 Passed

Validation for skill structure

Criteria	Description	Result
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
Path: .agents/skills/client-methods/SKILL.md
Commit: c1ee18b

Reviewed: 5 days ago

Table of Contents

Discovery Implementation Validation

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.