CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

principle-boundary-discipline

Apply when wiring validation, error handling, or framework adapters. Concentrate guards at system boundaries (CLI, config, network, external APIs); trust internal types and keep business logic in pure functions.

Quality

90%

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

92%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 body is an exemplar of a compact principle skill: lean, specific, and immediately applicable, with self-check questions that operationalize the rule. The only improvement space is a short before/after example to make the boundary pattern fully copy-paste concrete.

DimensionReasoningScore

Conciseness

The ~35-line body is lean and directive with no padding and no explanation of concepts Claude already knows; every line ("Validate config at parse time (the boundary), not inside business logic", "Prompt construction: structured state in, string out") earns its place. Nothing needs trimming, matching the anchor-5 example of assuming Claude's competence.

5 / 5

Actionability

For an instruction-only skill the guidance is concrete and checkable: specific rules like "No redundant nil checks deep in call chains if the boundary already validated" plus two applied test questions ("Is this data crossing a system boundary right now?"). Not a 5 because there is no worked example (e.g., a before/after code snippet) demonstrating the pattern in a common case.

4 / 5

Workflow Clarity

This is a simple single-purpose principle skill with no multi-step process, and the single action is unambiguous: the body moves from pattern to grouped applications to two self-check questions that function as verification checkpoints. Per the rubric's simple-skill guidance this warrants a 5; no destructive or batch operations are involved, so no cap applies.

5 / 5

Progressive Disclosure

The skill is under 50 lines with no need for external references (no references/, scripts/, or assets/ directories exist, and the body cites none), and it is organized into well-labeled sections (The pattern, Applications, The tests). Under the rubric's simple-skill guidance this earns a 5.

5 / 5

Total

19

/

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.

A strong description that explicitly states both what the skill does and when to apply it, using natural trigger terms and concrete boundary examples. Its only weaknesses are moderate trigger-breadth (missing common synonyms like "input validation" or "exception handling") and principle-level rather than task-level action phrasing.

Suggestions

Add common trigger synonyms such as "input validation", "exception handling", or "defensive checks" to the when-clause so users phrasing the need differently still match.

Broaden the trigger scenarios slightly (e.g., refactoring scattered validation, reviewing where error handling belongs) to cover more natural entry points to the skill.

DimensionReasoningScore

Specificity

The description lists several concrete directives — "Concentrate guards at system boundaries (CLI, config, network, external APIs)", "trust internal types", "keep business logic in pure functions" — rather than vague domain-naming. It falls short of a 5 because the actions are principle-level statements rather than a comprehensive list of concrete capabilities.

4 / 5

Completeness

Both questions are explicitly answered with concrete trigger phrases: the when is "Apply when wiring validation, error handling, or framework adapters" and the what is "Concentrate guards at system boundaries... trust internal types and keep business logic in pure functions". This matches the anchor-5 example's structure of an explicit capability statement plus an explicit trigger clause; it is clearly above the anchor-4 case where the when-clause is generic.

5 / 5

Trigger Term Quality

Natural terms users would say are present: "validation", "error handling", "framework adapters", "CLI", "config", "network", "external APIs". Not a 5 because common variations like "input validation", "exception handling", or "defensive programming" are missing.

4 / 5

Distinctiveness Conflict Risk

The boundary-discipline framing ("guards at system boundaries", "trust internal types") carves a clear niche with distinct triggers around validation placement and framework wiring. Minor overlap risk remains with general code-design or architecture-principle skills that also touch validation and error handling.

4 / 5

Total

17

/

20

Passed

Validation

100%

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

geut/factory-skills

Path

.agents/skills/principle-boundary-discipline/SKILL.md

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.