cs-senior-engineer

Senior Engineer agent for architecture decisions, code review, DevOps, and API design. Orchestrates engineering and engineering-team skills for technical implementation work. Spawn when users need system design, code quality review, CI/CD pipeline setup, or infrastructure decisions.

Quality

76%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./.gemini/skills/cs-senior-engineer/SKILL.md

Quality

Content

68%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.

The body is concise and well-structured with clear sequenced workflows, but it stays at the orchestration/meta level: it points to sub-skills rather than giving executable guidance, and its batch/destructive workflows lack explicit validation checkpoints.

Suggestions

Add explicit validation/verification checkpoints to the CI/CD Pipeline Setup workflow (e.g., validate generated YAML, dry-run the pipeline, confirm deploy safety) to lift workflow_clarity above the destructive-ops cap of 3.

Include at least one concrete, executable artifact per workflow (e.g., a minimal GitHub Actions YAML skeleton or an ADR template) so the guidance is actionable rather than purely delegated to sub-skills.

Verify that every skill referenced in the body (e.g., engineering/tech-debt-tracker in workflow 5) actually exists, since several referenced skills are not listed in the Skill Integration section.

Dimension	Reasoning	Score
Conciseness	Lean, list-driven body that assumes Claude's competence; every section earns its place with no padding or explanation of concepts Claude already knows.	5 / 5
Actionability	Provides high-level sequenced direction that delegates execution to named sub-skills ('Evaluate architecture patterns via senior-architect'), but lacks concrete code, commands, or copy-paste-ready guidance for the orchestration work itself.	3 / 5
Workflow Clarity	Workflows are clearly numbered and sequenced with an escalation loop in the feature-repair flow, but batch/destructive operations like CI/CD deploy and PR review lack explicit validation checkpoints, capping clarity at 3 per the rubric.	3 / 5
Progressive Disclosure	Well-organized into clearly labeled sections (Role, Skill Integration, Core Workflows, Output Standards) in a single self-contained file; no bundle files exist to split further, so structure is good with minor organization gaps.	4 / 5
	Total	15 / 20 Passed

Description

83%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.

The description is strong: it names concrete capabilities, uses third person, and explicitly couples a clear 'what' with a concrete 'Spawn when...' trigger. Its main weakness is breadth-induced overlap risk and a few missing natural trigger synonyms.

Dimension	Reasoning	Score
Specificity	Lists several specific concrete capabilities ('architecture decisions, code review, DevOps, and API design') and the orchestration action, with only minor gaps in coverage rather than a fully comprehensive enumeration.	4 / 5
Completeness	Explicitly answers both 'what' (senior engineer for architecture/code review/DevOps/API design, orchestrates engineering skills) and 'when' via the concrete 'Spawn when users need system design, code quality review, CI/CD pipeline setup, or infrastructure decisions' trigger.	5 / 5
Trigger Term Quality	Includes natural trigger phrases users would say ('system design, code quality review, CI/CD pipeline setup, or infrastructure decisions') but is missing some common synonyms and variations.	4 / 5
Distinctiveness Conflict Risk	Has a clear niche as a senior-engineer orchestration layer with distinct triggers, though its broad cross-cutting engineering scope carries minor overlap risk with the individual sub-skills it coordinates.	4 / 5
	Total	17 / 20 Passed

Validation

87%

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

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning
relative_links	Relative link issues: 2 suspicious	Warning

	Total	14 / 16 Passed

Repository: alirezarezvani/claude-skills
Path: .gemini/skills/cs-senior-engineer/SKILL.md
Commit: 19392f7

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