CtrlK
BlogDocsLog inGet started
Tessl Logo

human-architect-mindset

Systematic architectural thinking for irreplaceable human capabilities - domain modeling, systems thinking, constraint navigation, and AI-aware problem decomposition. Use proactively when detecting architectural decisions, system design discussions, or multi-component planning.

56

Quality

64%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./human-architect-mindset/skills/human-architect-mindset/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

45%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 skill contains a genuinely useful, well-sequenced 5-phase architectural workflow and concrete question banks, but it is severely overlong, heavily philosophical, and monolithic. No bundle files or external references are used, so progressive disclosure is minimal despite content (the SDD extension, tool catalogues) that clearly belongs in separate files.

Suggestions

Move the Spec Driven Development extension and the detailed tool/self-learning tables into separate reference files (e.g. references/sdd.md, references/ai-tools.md) and link to them one level deep from a leaner SKILL.md overview.

Cut the philosophical framing sections ('The AI Perfection Trap', 'The Human Moat', 'Why AI can't replace this') and the duplicated 'Questions to Always Ask' list, which re-asks questions already covered in the pillar sections.

Tighten each pillar to its actionable core (what it is, the concrete questions to ask, the teaching point) and remove abstract exhortation like 'navigate corporate reality' that does not instruct Claude what to do.

DimensionReasoningScore

Conciseness

At ~800 lines the body is noticeably verbose, padded with philosophical framing ("The AI Perfection Trap", "The Human Moat") and a duplicated "Questions to Always Ask" section that re-asks questions already in the pillar sections; not a 1 because the structured phases and tool tables are not pure padding.

2 / 5

Actionability

Some concrete guidance exists (the 5-phase process with per-phase Goals/Outputs, specific question banks, and tool tables with "When to Consider" columns), but much of the skill is abstract exhortation ("navigate corporate reality", "maintain irrational loyalty") without specific steps.

3 / 5

Workflow Clarity

The Architect Process is a clearly sequenced 5-phase workflow (Domain Discovery → Systems Analysis → Constraint Mapping → AI Decomposition Planning → Solution Synthesis) each with Goal, Process, Key questions, and Output; no validation gates between phases, but none are warranted for a non-destructive thinking skill.

4 / 5

Progressive Disclosure

No bundle files exist and no external references are linked; the body is a monolithic wall of text in which clearly separable material (the ~170-line SDD extension, the detailed tool/self-learning tables) is fully inlined rather than split into one-level-deep reference files.

2 / 5

Total

11

/

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 clearly states the skill's capabilities and gives an explicit 'Use proactively when...' trigger clause. It is concise, third-person, and well-scoped to architecture/system-design decisions. The main weakness is that the listed capabilities are conceptual rather than concrete technical actions, and a few natural synonyms are missing.

DimensionReasoningScore

Specificity

Lists several concrete capability areas ("domain modeling, systems thinking, constraint navigation, and AI-aware problem decomposition"), though as conceptual thinking modes rather than executable technical actions; minor coverage gaps keep it below a 5.

4 / 5

Completeness

Explicitly answers both what ("Systematic architectural thinking for irreplaceable human capabilities - domain modeling...") and when ("Use proactively when detecting architectural decisions, system design discussions, or multi-component planning") with concrete trigger phrases.

5 / 5

Trigger Term Quality

Includes natural trigger phrases users would say ("architectural decisions, system design discussions, or multi-component planning") with good coverage, but a few common synonyms (e.g., "tech choices", "design review") are absent.

4 / 5

Distinctiveness Conflict Risk

The architectural-thinking niche is mostly distinct with specific triggers, but broad terms like "system design discussions" carry minor overlap risk with general design or planning skills.

4 / 5

Total

17

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (802 lines); consider splitting into references/ and linking

Warning

Total

15

/

16

Passed

Repository
bencium/bencium-marketplace
Reviewed

Table of Contents

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.