CtrlK
BlogDocsLog inGet started
Tessl Logo

safety-and-boundaries

Hard rules — what the Agent Builder MUST NOT do regardless of user request. Load IMMEDIATELY if a request feels like it crosses into raw-secret handling, unprompted promotion, irreversible deletion, or impersonation of another user.

72

Quality

88%

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

77%Weight 40%Scale 1-3

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

A strong, highly actionable safety skill with clear confirmation-gated workflows, weakened only by length that could be trimmed and a monolithic structure with a dangling external reference. The guidance itself is excellent.

Suggestions

Tighten rule 5 (public auth): the four-step procedure plus the 'when in doubt' default can be condensed without losing the hard-pause semantics.

Resolve or remove the 'secrets-and-integrations playbook' reference, or create that file under references/ so the inline citation points to a real bundle asset.

Consider splitting the 'Choosing an approval type' section into a references/ file and keeping SKILL.md as a concise overview, which would improve progressive disclosure.

DimensionReasoningScore

Conciseness

Mostly efficient and concrete (no padding explaining concepts Claude already knows), but at ~260 lines some sections — notably rule 5 on public auth — repeat and elaborate beyond what the procedure needs, so it could be tightened.

2 / 3

Actionability

Provides exact executable procedures with named tools ('call posthog__agent-applications-revisions-promote-create'), literal confirmation phrases ('promote', 'ship', 'go'), and concrete bad-pattern quotes to refuse — fully actionable instruction-only guidance.

3 / 3

Workflow Clarity

Destructive flows (promote, public auth, destroy) are sequenced with explicit human-confirmation checkpoints ('State → Ask → Wait → Then call'), which serve as the required validation gate for risky operations.

3 / 3

Progressive Disclosure

Well-organized into clear sections, but it is a single monolithic file with all content inline and one unresolvable reference (the 'secrets-and-integrations' playbook) that has no corresponding bundle file in references/.

2 / 3

Total

10

/

12

Passed

Description

100%Weight 40%Scale 1-3

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 tight, well-constructed description: it states the skill's purpose, names concrete prohibited actions, and gives explicit load-time triggers in a distinct niche. It would benefit from no changes.

DimensionReasoningScore

Specificity

Lists multiple concrete actions the builder must avoid — 'raw-secret handling', 'unprompted promotion', 'irreversible deletion', 'impersonation of another user' — matching the anchor for enumerating several specific actions rather than vague language.

3 / 3

Completeness

Explicitly answers both 'what' ('Hard rules — what the Agent Builder MUST NOT do') and 'when' ('Load IMMEDIATELY if a request feels like it crosses into ...'), with explicit trigger guidance.

3 / 3

Trigger Term Quality

The 'Load IMMEDIATELY if a request feels like it crosses into ...' clause surfaces natural scenario terms (secrets, promote, delete, impersonate) a user would actually invoke; not jargon-only nor generic.

3 / 3

Distinctiveness Conflict Risk

Occupies a clear, narrow niche (Agent Builder safety boundaries) with triggers unlikely to fire for unrelated skills; no overlap risk with general skills.

3 / 3

Total

12

/

12

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
PostHog/posthog
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.