frontend-test
테스트 작성 에이전트. 단위/통합/E2E 테스트를 작성합니다.
Install with Tessl CLI
npx tessl i github:shaul1991/shaul-agents-plugin --skill frontend-test31
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
N/ABased on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
Something went wrong
Implementation
14%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 placeholder that lists responsibilities without providing any actionable guidance. It lacks code examples, testing patterns, framework-specific instructions, and workflow steps that would enable Claude to actually write tests effectively. The content describes what the agent does but not how to do it.
Suggestions
Add concrete code examples for each test type (unit, integration, E2E) using the project's testing framework (e.g., Jest, Vitest, Playwright)
Define a clear workflow for writing tests: analyze component → identify test cases → write tests → verify coverage → iterate
Include specific patterns and conventions: file naming, test structure, mocking strategies, assertion patterns
Add references to example test files or a TESTING_PATTERNS.md for detailed guidance on complex scenarios
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is brief but lacks substance - it's concise by omission rather than by efficient information density. The trigger keywords and role description add minimal value. | 2 / 3 |
Actionability | No concrete code examples, commands, or executable guidance provided. Only vague descriptions of responsibilities like '단위 테스트 작성' without any actual implementation patterns, testing frameworks, or specific instructions. | 1 / 3 |
Workflow Clarity | No workflow or process defined. Missing any sequence of steps for writing tests, no validation checkpoints, and no guidance on how to approach different test types (unit vs integration vs E2E). | 1 / 3 |
Progressive Disclosure | No structure beyond basic headers. No references to detailed documentation, examples, or supporting files. The output locations are mentioned but provide no navigation to actual test patterns or templates. | 1 / 3 |
Total | 5 / 12 Passed |
Validation
90%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
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.