Name: senior-architect
Rating: 37.6 (1 reviews)
Author: administrakt0r

Blog Docs Log in Get started

senior-architect

Complete toolkit for senior architect with modern tools and best practices.

Quality

35%

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 ./plugins/AI-Agents-Safe-Coding-Skills-claude/skills/senior-architect/SKILL.md

The canonical home for this skill is senior-architect in administrakt0r/AI-Agents-Safe-Coding-Skills

Quality

Content

46%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 well-structured with real, clearly linked reference files and scripts, but it is padded with generic boilerplate Claude already knows and offers script commands with placeholder arguments rather than concrete examples. Workflows lack explicit validation checkpoints.

Suggestions

Remove or move generic boilerplate ('Best Practices Summary', 'Common Commands', 'Tech Stack') that Claude already knows, keeping only non-obvious guidance.

Replace `[options]`/`[arguments]` placeholders with at least one concrete example invocation showing real flags and expected output.

Add a validation/feedback step to the Development Workflow (e.g. run the analyzer, review findings, fix, re-run until clean) before marking work complete.

Dimension	Reasoning	Score
Conciseness	Several sections are padded boilerplate Claude already knows (the generic 'Best Practices Summary' — 'Write clear code, Use consistent naming' — the 'Common Commands' like `npm run dev`, and the enumerated 'Tech Stack'), matching 'noticeably verbose; several unnecessary explanations or padded sections' rather than the mostly-efficient anchor (3).	2 / 5
Actionability	It provides real script invocations (`python scripts/project_architect.py <project-path>`) but leaves arguments as `[options]`/`[arguments]` placeholders with no concrete example and pairs them with vague feature bullets ('Deep analysis', 'Automated scaffolding'), fitting 'some concrete guidance but incomplete' rather than mostly-executable (4).	3 / 5
Workflow Clarity	The 'Development Workflow' gives a rough three-step sequence (setup → run checks → implement) but includes no validation checkpoints or error-feedback loops, matching 'steps listed but validation gaps' rather than the checkpointed anchor (4).	3 / 5
Progressive Disclosure	Structure is good with clearly signaled, one-level-deep references to three real reference files and the scripts directory, organized in dedicated 'Reference Documentation' and 'Resources' sections; minor gaps from inlined generic boilerplate keep it just below the fully-split anchor (5).	4 / 5
	Total	12 / 20 Passed

Description

25%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 generic and abstract: it names a target role but lists no concrete capabilities and provides no trigger guidance for when to invoke it. It would be hard for a user or router to distinguish this skill from many others.

Suggestions

Replace abstract language with concrete actions, e.g. 'Generates architecture diagrams, analyzes project structure, and audits dependencies for senior architects.'

Add an explicit trigger clause, e.g. 'Use when designing system architecture, generating architecture diagrams, or auditing project dependencies.'

Narrow the scope so it is distinguishable from general coding/architecture skills rather than claiming a 'complete toolkit'.

Dimension	Reasoning	Score
Specificity	The description names a domain ('senior architect') but offers no concrete actions — 'Complete toolkit', 'modern tools', and 'best practices' are pure abstract language, so it sits above the entirely-vague anchor (1) but well below listing concrete actions (3).	2 / 5
Completeness	It gives only a vague 'what' ('complete toolkit for senior architect') and contains no 'when'/'Use when' trigger guidance, matching the 'vague what and no when' anchor; the missing-trigger cap rules out 3 or above.	2 / 5
Trigger Term Quality	Only generic keywords ('toolkit', 'best practices', 'modern tools') appear; the natural phrases a user would actually say when needing this skill are missing, matching the 'one or two generic keywords' anchor rather than the relevant-keyword anchor (3).	2 / 5
Distinctiveness Conflict Risk	'Complete toolkit for senior architect with modern tools and best practices' is very broad and overlaps heavily with general architecture/coding skills, fitting the 'very broad; high overlap risk' anchor rather than the somewhat-specific anchor (3).	2 / 5
	Total	8 / 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: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: plugins/AI-Agents-Safe-Coding-Skills-claude/skills/senior-architect/SKILL.md
Commit: 57c135b

Reviewed: 1 day 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.