CtrlK
BlogDocsLog inGet started
Tessl Logo

pantheon-ai/frame-problem

Classify a problem using Cynefin triangulation before acting — routes to the right skill chain (investigate, brainstorm, probe, troubleshoot).

89

Quality

89%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

Overview
Quality
Evals
Security
Files

Quality

Discovery

89%

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 is a well-crafted description for a meta-level routing/framing skill. Its strongest aspects are the explicit trigger terms that match natural user language expressing uncertainty, the clear 'Use when' clause, and the helpful exclusion clause that reduces conflict risk. The main weakness is that the specific actions could be slightly more concrete — 'Cynefin triangulation (3 tests + decomposition)' is somewhat jargon-heavy for the specificity dimension.

DimensionReasoningScore

Specificity

Names the domain (problem classification/sense-making) and a specific methodology (Cynefin triangulation with 3 tests + decomposition), but the concrete actions are somewhat abstract — 'classify problem' and 'route to the right skill chain' describe a meta-process rather than multiple specific tangible actions.

2 / 3

Completeness

Clearly answers both 'what' (classify problems using Cynefin triangulation to route to the right skill chain) and 'when' (explicit 'Use when:' clause with multiple trigger phrases, plus a helpful exclusion 'NOT for known tasks'). The explicit trigger guidance is well-structured.

3 / 3

Trigger Term Quality

Includes a strong set of natural trigger terms users would actually say: 'how should I start', 'where to begin', 'unsure what to do', 'what approach', 'which skill', 'frame'. These closely match how users express uncertainty about how to proceed.

3 / 3

Distinctiveness Conflict Risk

This is a clearly distinct meta-skill for problem framing and routing, not a task-execution skill. The explicit exclusion ('NOT for known tasks — just do them') and the specific Cynefin methodology make it highly unlikely to conflict with other skills that handle actual task execution.

3 / 3

Total

11

/

12

Passed

Implementation

85%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This is a strong, well-architected skill that provides a complete decision framework with concrete tools (triangulation questions, routing table, output templates) rather than abstract theory. The workflow is clearly sequenced with appropriate validation checkpoints and error-handling guidance. Minor verbosity in some sections (anti-pattern explanations, inline warnings) could be tightened, but the complexity of the Cynefin framework justifies most of the length.

DimensionReasoningScore

Conciseness

The skill is fairly dense and information-rich, but includes some redundancy (e.g., the anti-patterns section restates points already made inline like LLM bias toward Complicated). The AskUserQuestion guard and triangulation logic are necessary but could be slightly tighter. Overall mostly efficient for the complexity of the framework being taught.

2 / 3

Actionability

Highly actionable with concrete question templates (T1/T2/T3 with specific answer options mapped to domains), a complete routing table with exact skill chains, specific output format templates for classification results, and clear decision logic at each step. The usage examples show concrete input→output patterns.

3 / 3

Workflow Clarity

Excellent multi-step workflow with clear sequencing (auto-classify → triangulate → decompose if needed → classify+route → handoff). Each step has explicit decision points, convergence/divergence logic for triangulation results, and validation checkpoints (Adjacent Domain Challenge, user confirmation at decomposition and handoff). The misclassification traps serve as error-recovery guidance.

3 / 3

Progressive Disclosure

Well-structured with a clear overview flow at the top, detailed steps inline (appropriate for a decision-framework skill), and six clearly-signaled one-level-deep reference files for handoff templates. The When to Use / When Not to Use / Anti-Patterns sections are appropriately placed at the end for reference without cluttering the main workflow.

3 / 3

Total

11

/

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.

Validation10 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

Total

10

/

11

Passed

Reviewed

Table of Contents