CtrlK
BlogDocsLog inGet started
Tessl Logo

architect

Architect orchestrator Nicolify. Lee 01-spec.md + 02-design-{ui,agentic}.md. Decide qué surfaces toca (BE/FE/agentic). Spawna sub-architects en paralelo (/architect-be, /architect-fe, /architect-agentic). Reúne sus 03-arch-*.md y produce 04-tickets.yaml ordenado con dependencias + owner_eligibility (qwen vs Opus) + acceptance criteria + quality gates. Activa cuando user dice: '/architect', 'diseñemos la arq', 'tickets', 'qué tickets salen', 'arquitectura técnica', 'cómo lo construimos técnicamente'.

68

Quality

84%

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

SKILL.md
Quality
Evals
Security

Quality

Content

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

A tightly structured orchestration skill with concrete yaml templates, clear sequencing, and explicit validation/escalation checkpoints. Trimming redundant anti-patterns that restate Step 4 rules and inlining or更好地 signaling the external ticket template would push it higher.

Suggestions

Remove anti-patterns that merely restate Step 4 rules (e.g., 'Mezclar agentic + BE en MISMO ticket' and 'Asignar Opus a tickets BE/FE non-agentic') to reduce redundancy and token cost.

Inline the key fields of docs/specs/templates/04-tickets-template.yaml (or add a short schema sketch) so the ticket-production step is self-contained rather than relying on an external template.

Convert the {id}/{m} placeholders in the Agent spawn prompts into a brief fill-in convention so the prompts are directly executable without inference.

DimensionReasoningScore

Conciseness

Dense, table- and yaml-driven content that assumes Claude's competence and avoids explaining known concepts, though the Anti-patterns section repeats rules already stated in Step 4 (e.g., owner eligibility and agentic/BE separation).

4 / 5

Actionability

Provides concrete, mostly copy-pasteable yaml templates (dependencies, acceptance criteria, notes_for_downstream) and Agent spawn prompts, with minor gaps from {id}/{m} placeholders and references to external templates not inlined.

4 / 5

Workflow Clarity

Six clearly sequenced steps with explicit validation (Step 5 checklist) and a feedback loop (Step 3 cross-module audit escalating to /pm when NEW is proposed against shared), satisfying the validation requirement for this batch operation.

5 / 5

Progressive Disclosure

Well-organized into clear sections that reference one-level-deep project files (01-spec.md, 02-design-*.md, 04-tickets-template.yaml, anti-duplication.md) as inputs; no nested references, though no skill bundle files exist to split content further.

4 / 5

Total

17

/

20

Passed

Description

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

A strong description that pairs a concrete multi-step 'what' with an explicit 'when' trigger clause and highly specific internal artifact references. Minor improvement possible by adding a few more natural-language synonyms alongside the existing trigger phrases.

DimensionReasoningScore

Specificity

Lists several concrete actions ('Lee 01-spec.md', 'Decide qué surfaces toca', 'Spawna sub-architects en paralelo', 'Reúne sus 03-arch-*.md y produce 04-tickets.yaml ordenado con dependencias + owner_eligibility + acceptance criteria + quality gates'), giving comprehensive orchestration coverage with only minor gaps in sub-step detail.

4 / 5

Completeness

It explicitly answers both 'what' (orchestrates, reads, decides, spawns, gathers, produces 04-tickets.yaml) and 'when' ('Activa cuando user dice: ...') with concrete trigger phrases.

5 / 5

Trigger Term Quality

The 'Activa cuando user dice' clause supplies natural phrases a user would say ('/architect', 'diseñemos la arq', 'tickets', 'qué tickets salen', 'arquitectura técnica', 'cómo lo construimos técnicamente'), with good coverage though a few synonyms are missing.

4 / 5

Distinctiveness Conflict Risk

The architect-orchestrator niche, specific artifact names (01-spec.md, 02-design-*.md, 04-tickets.yaml) and sub-architect routing give it a clear niche with distinct triggers and minimal conflict risk.

5 / 5

Total

18

/

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

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

Total

15

/

16

Passed

Repository
alpacapurpura/ap_sales_agent
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.