frontend-build

빌드/배포 에이전트. 빌드 설정과 배포 파이프라인을 관리합니다.

Install with Tessl CLI

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

What are skills?

Quality

35%

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-build/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 (build and deployment management) but is too brief and lacks critical elements. The absence of explicit trigger guidance ('Use when...') and limited trigger terms significantly reduce Claude's ability to correctly select this skill from a large pool of options.

Suggestions

Add a 'Use when...' clause with explicit triggers like 'Use when the user asks about CI/CD pipelines, deployment automation, build configuration, or mentions tools like Jenkins, GitHub Actions, or Docker deployments'

Include more specific concrete actions such as 'configure CI/CD workflows, manage environment variables, trigger deployments, monitor build status, rollback releases'

Add common user trigger terms and file types: 'CI/CD', 'continuous integration', 'release pipeline', '.yml config files', 'GitHub Actions', 'Jenkins', 'deploy to staging/production'

Dimension	Reasoning	Score
Specificity	Names the domain (build/deploy) and mentions some actions ('빌드 설정과 배포 파이프라인을 관리합니다' - manages build settings and deployment pipelines), but lacks specific concrete actions like 'configure CI/CD', 'run tests', 'deploy to staging'.	2 / 3
Completeness	Describes what it does (manages build settings and deployment pipelines) 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 '빌드' (build), '배포' (deploy), '파이프라인' (pipeline), but missing common variations users might say such as 'CI/CD', 'continuous integration', 'release', 'deploy to production', or specific tool names.	2 / 3
Distinctiveness Conflict Risk	The build/deploy domain is somewhat specific, but '에이전트' (agent) is vague and could overlap with other automation or DevOps-related skills. Lacks distinct file types or specific tool references.	2 / 3
	Total	7 / 12 Passed

Implementation

37%

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

This skill is essentially a role description rather than actionable guidance. While it's concise and well-structured, it completely lacks the concrete instructions, code examples, and workflows that would enable Claude to actually perform build and deployment tasks. It reads more like a job description than a skill file.

Suggestions

Add concrete code examples for common tasks: sample next.config.js optimization, Dockerfile template, and GitHub Actions workflow YAML

Include a step-by-step workflow for deployment with validation checkpoints (e.g., build -> test -> validate -> deploy -> verify)

Provide specific commands for build operations (e.g., `npm run build`, `docker build -t app .`, deployment commands)

Add references to detailed documentation files for Docker configuration, CI/CD setup, and environment variable management

Dimension	Reasoning	Score
Conciseness	The content is extremely lean with no unnecessary explanations. Every line serves a purpose - role definition, responsibilities, triggers, and output locations are all stated without padding.	3 / 3
Actionability	The skill provides no concrete guidance, code examples, or executable instructions. It only lists abstract responsibilities like '빌드 설정 최적화' without showing how to actually perform any of these tasks.	1 / 3
Workflow Clarity	No workflow or process steps are defined. The skill lists areas of responsibility but provides no sequence, validation steps, or guidance on how to execute build/deploy operations.	1 / 3
Progressive Disclosure	The content is well-organized with clear sections, but it lacks any references to detailed documentation. For a build/deploy agent, there should be links to configuration guides, Docker setup instructions, or CI/CD pipeline examples.	2 / 3
	Total	7 / 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.