Name: engineering-skills
Rating: 63.2 (1 reviews)
Author: alirezarezvani

engineering-skills

Index of the engineering-team skills bundle for Claude Code, Codex, Gemini CLI, Cursor, OpenClaw, and 6 more tools. Architecture, frontend, backend, QA, DevOps, security, AI/ML, data engineering, Playwright, Stripe, AWS, MS365 (stdlib-only Python tools). Use when browsing or choosing among engineering-team role skills — load only the one specialist SKILL.md you need, never bulk-load the bundle.

Quality

75%

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

Fix and improve this skill with Tessl

tessl review fix ./.gemini/skills/engineering-skills/SKILL.md

The canonical home for this skill is engineering-skills in alirezarezvani/claude-skills

Quality

Content

75%Weight 40%Scale 1-5

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

A compact, well-organized index body that uses tables efficiently and gives concrete Quick Start commands, fitting its catalog purpose. The main gaps are a skill-count inconsistency (32 stated vs 23 tabulated), an implicit select-then-load workflow, and external references (CLAUDE.md, scripts/) that are not verifiable within the provided bundle.

Suggestions

Reconcile the skill counts: the intro and Rules say 32 skills but the three overview tables total 23 (13+5+5) — either add the missing group or correct the headline number.

Make the selection workflow explicit with a short numbered list (e.g. 1. Identify the task domain, 2. Find the matching skill in the overview table, 3. Load only that skill's SKILL.md) so the flow does not have to be inferred.

Resolve the external references: either move 'Check CLAUDE.md' guidance into a bundled reference file with a clear path, or remove it so navigation stays within verifiable one-level-deep pointers.

Dimension	Reasoning	Score
Conciseness	Lean, table-driven index with no concept padding and copy-paste Quick Start commands; minor redundancy between the intro sentence and the Skills Overview category headers keeps it just below the 'every token earns its place' level.	4 / 5
Actionability	Provides concrete executable commands ('/read .../senior-fullstack/SKILL.md', 'npx agent-skills-cli add ...', 'python3 <skill>/scripts/<tool>.py --help') and folder paths, but the Python tools instruction is a template with placeholders rather than a concrete runnable example.	4 / 5
Workflow Clarity	The single action (load only one specialist SKILL.md, do not bulk-load) is unambiguous and reinforced by the Rules section, but the select-from-overview-then-load flow is implied rather than spelled out as an explicit numbered sequence.	4 / 5
Progressive Disclosure	Genuinely appropriate index structure — a concise overview with tables pointing one level deep to each specialist SKILL.md and clear navigation via the Folder/Focus columns; dinged because 'Check CLAUDE.md' and the scripts references point to files not present in this bundle and the category/count structure is slightly inconsistent.	4 / 5
	Total	16 / 20 Passed

Description

75%Weight 40%Scale 1-5

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

A well-constructed index skill description: it states a clear purpose, lists comprehensive domain coverage, and provides an explicit 'Use when...' trigger in third-person voice. Its main weaknesses are limited concrete actions (it catalogs rather than does) and substantial trigger overlap with the specialist skills it points to.

Suggestions

Tighten the action verbs beyond browse/choose/load — e.g., 'Locate the right specialist skill for a task and load only that SKILL.md' — to lift specificity toward the 'several specific actions' anchor.

Reduce conflict risk with the 32 specialist skills by making the index trigger conditional, e.g. 'Use when you are unsure which engineering role skill applies or need to compare them' rather than listing the shared domain keywords alone.

Dimension	Reasoning	Score
Specificity	Names the domain and a couple concrete actions ("browsing or choosing among engineering-team role skills", "load only the one specialist SKILL.md"), but as an index it does not enumerate comprehensive concrete actions, matching the 'domain + 1-2 actions' anchor rather than the 'several specific actions' level above.	3 / 5
Completeness	Explicitly answers both 'what' ("Index of the engineering-team skills bundle...") and 'when' ("Use when browsing or choosing among engineering-team role skills — load only the one specialist SKILL.md you need"), matching the anchor for clear what-and-when with concrete trigger phrases.	5 / 5
Trigger Term Quality	Good coverage of natural role/domain terms users would say ("architecture", "frontend", "backend", "QA", "DevOps", "security", "AI/ML", "Playwright", "Stripe", "AWS", "MS365"), though it lacks synonyms or file extensions that would push it to the comprehensive level.	4 / 5
Distinctiveness Conflict Risk	It carves a distinct meta-niche (index/chooser that redirects to a specialist), but the listed domains overlap heavily with the 32 specialist skills it catalogs, so it could still trigger when a specific role skill is wanted.	3 / 5
	Total	15 / 20 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
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: alirezarezvani/claude-skills
Path: .gemini/skills/engineering-skills/SKILL.md
Commit: 19392f7

Reviewed: ~7 hours 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.