CtrlK
BlogDocsLog inGet started
Tessl Logo

architectural-proposals

How to write comprehensive architectural proposals that drive alignment before code is written

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 ./.copilot/skills/architectural-proposals/SKILL.md
SKILL.md
Quality
Evals
Security

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.

The content is a well-organized, actionable instruction skill with concrete templates, filled examples, a clear multi-step sequence, and a review checklist, scoring solidly across all dimensions. The main improvement opportunities are tightening the Patterns/Anti-Patterns redundancy and making the proposal-review validation an explicit feedback loop.

DimensionReasoningScore

Conciseness

The body is largely lean and free of explanations of concepts Claude already knows, with only minor redundancy between the Patterns and Anti-Patterns sections that could be trimmed, fitting anchor 4 rather than the fully-lean anchor 5.

4 / 5

Actionability

Concrete, copy-paste-ready templates and filled examples (decision framing with the ink example, per-risk documentation format) give mostly executable guidance, with minor gaps such as example file paths that are illustrative from the source case rather than generally applicable.

4 / 5

Workflow Clarity

A clear sequence is present (7 required sections, the 10-step 'Key patterns demonstrated', and numbered wave-restructuring steps) plus a 'Red flags in proposal reviews' checklist serving as validation, but there is no explicit validate-then-fix feedback loop, matching anchor 4.

4 / 5

Progressive Disclosure

No bundle files exist; the skill is self-contained and well-sectioned into Context, Patterns, Examples, and Anti-Patterns. At over 50 lines it does not qualify for the simple-skill anchor 5, but its structure is good with only minor organization gaps, fitting anchor 4.

4 / 5

Total

16

/

20

Passed

Description

53%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 clearly states what the skill does and carves out a recognizable niche, but it lacks an explicit 'Use when…' trigger clause and natural keyword variations, which caps completeness and trigger quality at the midpoint. Adding concrete trigger phrases would lift the weaker dimensions.

Suggestions

Add an explicit 'Use when…' clause naming concrete triggers (e.g., 'Use when architecture shifts invalidate assumptions, product direction changes, or multiple waves are affected by a decision').

Include natural keyword variations and synonyms users would actually say ('architecture proposal', 'design proposal', 'tech design doc', 'RFC') to improve trigger-term coverage.

List 2-3 more specific actions (e.g., 'restructure waves, frame decisions with sign-off, document risks with mitigations') to lift specificity beyond one core action.

DimensionReasoningScore

Specificity

Names the domain and 1-2 concrete actions ('write comprehensive architectural proposals that drive alignment'), but does not list several specific actions, matching the anchor 3 example and falling short of the multi-action anchor 4.

3 / 5

Completeness

The 'what' is clear (write proposals that drive alignment), but the 'when' is only weakly implied by 'before code is written' with no explicit 'Use when…' clause, which per the guidelines caps completeness at 3.

3 / 5

Trigger Term Quality

'architectural proposals' and 'alignment' are relevant keywords, but it lacks the natural 'Use when…' phrasing and common synonyms/variations users would say, fitting anchor 3 rather than the comprehensive anchor 4.

3 / 5

Distinctiveness Conflict Risk

'Architectural proposals' is a fairly distinct niche with minor overlap risk against general planning or documentation skills, matching anchor 4 rather than the fully-distinct anchor 5 which requires concrete distinguishing trigger phrases.

4 / 5

Total

13

/

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

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
bradygaster/squad
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.