architecture
Architectural decision-making framework. Requirements analysis, trade-off evaluation, ADR documentation. Use when making architecture decisions or analyzing system design.
Install with Tessl CLI
npx tessl i github:lchenrique/politron-ide --skill architecture75
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
67%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This description has good structure with an explicit 'Use when' clause that clearly communicates both purpose and trigger conditions. However, the capabilities listed are somewhat abstract (e.g., 'trade-off evaluation') rather than concrete actions, and the trigger terms could be expanded to capture more natural user language around architecture decisions.
Suggestions
Add more concrete action verbs like 'create ADR documents', 'compare technology options', 'document design rationale' to improve specificity
Expand trigger terms to include natural phrases users might say: 'tech stack', 'should I use X or Y', 'design tradeoffs', 'scalability concerns', 'microservices'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (architectural decisions) and lists some actions (requirements analysis, trade-off evaluation, ADR documentation), but these are somewhat abstract rather than concrete specific actions like 'create ADR files' or 'compare technology options'. | 2 / 3 |
Completeness | Clearly answers both what (architectural decision-making framework with requirements analysis, trade-off evaluation, ADR documentation) and when (making architecture decisions or analyzing system design) with an explicit 'Use when' clause. | 3 / 3 |
Trigger Term Quality | Includes relevant terms like 'architecture decisions', 'system design', and 'ADR', but misses common variations users might say such as 'tech stack', 'design patterns', 'scalability', 'microservices vs monolith', or 'technology choice'. | 2 / 3 |
Distinctiveness Conflict Risk | 'System design' and 'architecture' could overlap with general software design skills or documentation skills. The ADR mention helps distinguish it, but 'analyzing system design' is broad enough to potentially conflict with code review or design pattern skills. | 2 / 3 |
Total | 9 / 12 Passed |
Implementation
72%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill excels at organization and token efficiency, providing a clean overview that directs users to appropriate detailed files. However, it functions more as a navigation hub than an actionable skill—the main file lacks concrete examples, specific decision-making steps, or executable guidance. The validation checklist is helpful but would benefit from explicit workflow sequencing.
Suggestions
Add a concrete quick-start workflow showing the sequence: 1) Run context discovery → 2) Classify project → 3) Select patterns → 4) Document ADR, with explicit validation between steps
Include at least one minimal concrete example in the main file (e.g., a simple ADR template or a 3-question decision tree) so users can take immediate action without reading other files
Add feedback loop guidance for when validation checklist items fail (e.g., 'If requirements unclear → return to context-discovery.md and ask X questions')
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, using tables for quick reference and avoiding unnecessary explanations. Every section serves a clear purpose without padding or explaining concepts Claude already knows. | 3 / 3 |
Actionability | Provides a clear structure with file references and a validation checklist, but lacks concrete executable examples or specific commands. The guidance is organizational rather than directly actionable—it tells you where to look rather than what to do. | 2 / 3 |
Workflow Clarity | The validation checklist provides a sequence of considerations, but there's no explicit workflow for how to move through the architecture decision process. Missing feedback loops for iterating on decisions or handling validation failures. | 2 / 3 |
Progressive Disclosure | Excellent use of progressive disclosure with a clear content map table showing exactly which files to read for which purpose. References are one level deep and well-signaled with descriptive 'When to Read' guidance. | 3 / 3 |
Total | 10 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
Total | 10 / 11 Passed | |
- 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.