frontend-api

API 통합 에이전트. API 클라이언트와 데이터 페칭을 구현합니다.

Install with Tessl CLI

npx tessl i github:shaul1991/shaul-agents-plugin --skill frontend-api

What are skills?

Quality

27%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/frontend-api/SKILL.md

SKILL.md

Review

Evals

Discovery

32%

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

This description provides a basic understanding of the skill's domain (API integration) but lacks the explicit trigger guidance needed for Claude to reliably select it from a large skill library. The description is too brief and missing a 'Use when...' clause, which significantly limits its effectiveness for skill selection.

Suggestions

Add an explicit 'Use when...' clause with trigger terms like 'API 호출', 'REST API', 'HTTP 요청', 'fetch data', 'API endpoint', '외부 서비스 연동'

Expand specific capabilities to include actions like authentication setup, error handling, response parsing, rate limiting, or specific API types (REST, GraphQL)

Include common file extensions or patterns like '.json responses', 'axios', 'fetch()', or framework-specific terms users might mention

Dimension	Reasoning	Score
Specificity	Names the domain (API integration) and mentions some actions ('API 클라이언트와 데이터 페칭을 구현합니다' - implements API clients and data fetching), but lacks comprehensive specific actions like authentication handling, error handling, or specific API types.	2 / 3
Completeness	Describes what it does (implements API clients and data fetching) but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill.	1 / 3
Trigger Term Quality	Contains relevant keywords like 'API', '통합' (integration), '클라이언트' (client), '데이터 페칭' (data fetching), but missing common variations users might say like 'REST', 'HTTP requests', 'endpoints', 'fetch data', or specific API names.	2 / 3
Distinctiveness Conflict Risk	Somewhat specific to API work but could overlap with general coding skills, backend development skills, or HTTP/networking skills. The term '에이전트' (agent) adds some distinction but 'API integration' is still fairly broad.	2 / 3
	Total	7 / 12 Passed

Implementation

22%

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

This skill content is essentially a role description rather than actionable guidance. It lists what the agent should do (API clients, data fetching, error handling, caching) but provides zero concrete implementation details, code examples, or workflows. Claude would gain almost no actionable knowledge from this skill.

Suggestions

Add executable code examples for API client implementation (e.g., fetch wrapper, axios configuration, error interceptors)

Include specific error handling patterns with code showing retry logic, error boundaries, and status code handling

Provide a concrete workflow for implementing a new API endpoint integration with validation steps

Add examples of caching strategies with actual implementation code (e.g., React Query, SWR, or custom caching)

Dimension	Reasoning	Score
Conciseness	The content is brief but lacks substance - it's essentially a role description with bullet points rather than actionable instructions. While not verbose, it doesn't provide enough value for the tokens used.	2 / 3
Actionability	No concrete code, commands, or executable guidance provided. Only vague descriptions like 'API 클라이언트 구현' and '에러 핸들링' without any specific implementation details, patterns, or examples.	1 / 3
Workflow Clarity	No workflow or process steps defined. The skill lists responsibilities but provides no sequence, validation steps, or guidance on how to actually implement API clients or handle errors.	1 / 3
Progressive Disclosure	Output locations are specified which is helpful, but there are no references to detailed documentation, examples, or related files. The structure exists but lacks navigation to deeper content.	2 / 3
	Total	6 / 12 Passed

Validation

90%

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 — 10 / 11 Passed

Validation for skill structure

Criteria	Description	Result
allowed_tools_field	'allowed-tools' contains unusual tool name(s)	Warning

	Total	10 / 11 Passed

Reviewed: 15 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.