dev-workflow

The complete development workflow for SkillHub contributors including local dev, staging validation, testing, and PR creation. Ensures agents follow the correct sequence of steps.

Quality

57%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

High

Do not use without reviewing

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/dev-workflow/SKILL.md

Quality

Content

65%

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

The body is a dense, highly actionable command reference with a clear staged workflow. Its main weaknesses are missing validation checkpoints around destructive reset operations and inline reference content that would benefit from progressive disclosure into separate files.

Suggestions

Add explicit validation/confirmation steps before destructive commands (e.g., prompt or dry-run before `make dev-all-reset` and `make db-reset`) to lift workflow clarity.

Move the detailed smoke-test coverage list and per-command reference tables into separate reference files linked from the body to improve progressive disclosure.

Remove or relocate time-sensitive values such as the '2026' staging/bootstrap passwords (or mark them as examples) so they do not penalize conciseness over time.

Dimension	Reasoning	Score
Conciseness	The body is lean reference material (commands and tables) with no concept-explaining fluff, but time-sensitive values like the '2026' passwords and some duplicated command listings could be tightened, keeping it just below fully efficient.	2 / 3
Actionability	It provides concrete, copy-paste-ready commands throughout (`make dev-all`, `make test-backend`, `./scripts/smoke-test.sh`) in tables and fenced blocks, with specific access points and credentials — fully executable guidance.	3 / 3
Workflow Clarity	The Stage 1–4 sequence is clear and staging includes smoke-test validation, but destructive operations such as `make dev-all-reset` ('clears data volumes') and `make db-reset` lack explicit validation/confirmation checkpoints, which caps workflow clarity at 2.	2 / 3
Progressive Disclosure	Sections are well-organized and external references are signaled one level deep ('See docs/13-parallel-workflow.md for full details'), but substantial reference content (the 10-item smoke-test list and multiple command tables) is inline rather than split into bundle files, and no bundle files exist to offload it.	2 / 3
	Total	9 / 12 Passed

Description

50%

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 conveys a clear domain and the major workflow stages, but it reads as a scope summary rather than a trigger-oriented description. It lacks an explicit 'Use when...' clause and distinct natural-language triggers, which keeps most dimensions at the mid level.

Suggestions

Add an explicit 'Use when...' trigger clause listing the natural phrases contributors say (e.g., 'Use when setting up SkillHub local dev, running backend/frontend tests, validating staging, or opening a PR').

Replace phase labels with concrete actions to lift specificity (e.g., 'Start the full stack, run backend/frontend tests, validate the containerized staging build, and create a PR via gh').

Tighten distinctiveness by leading with the SkillHub-specific scope so it does not collide with generic development-workflow skills.

Dimension	Reasoning	Score
Specificity	Names the domain ('development workflow for SkillHub contributors') and several stages ('local dev, staging validation, testing, and PR creation'), but these are phase labels rather than concrete actions, so it is not comprehensive enough for a 3.	2 / 3
Completeness	Clearly states what the skill covers, but the 'when' is only implied — there is no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 2 per the rubric.	2 / 3
Trigger Term Quality	Contains relevant terms a contributor might say ('local dev', 'staging validation', 'PR creation') but lacks common variations and any explicit trigger phrasing, so coverage is only partial.	2 / 3
Distinctiveness Conflict Risk	The 'SkillHub contributors' niche is somewhat specific, but the description could still overlap with generic dev-workflow or PR-creation skills and lacks distinct explicit triggers that would separate it cleanly.	2 / 3
	Total	8 / 12 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
referenced_paths_exist	Referenced path issues: 5 missing	Warning

	Total	15 / 16 Passed

Repository: iflytek/skillhub
Path: .agents/skills/dev-workflow/SKILL.md
Commit: ac46ad5

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