CtrlK
BlogDocsLog inGet started
Tessl Logo

operational-enterprise-ai

Create or redesign enterprise AI, automation, security, and operations product pages that explain system boundaries, approvals, auditability, exceptions, and rollback. Use for dark cinematic heroes, hairline grids, metric pauses, expandable solution rows, case-study evidence, security proof, and qualified demo or waitlist handoffs.

72

Quality

87%

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

82%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 a tight, well-organized instruction-only design guide with concrete prescriptive values, a clear narrative sequence, and a validation checklist. It loses only marginal points for lacking executable code and an explicit error-recovery loop.

DimensionReasoningScore

Conciseness

Lean bullet-driven guidance with no padding and no over-explanation of concepts Claude already knows; every line earns its place, e.g. 'Use 160-220ms for controls and 500-760ms for section entrances.'

5 / 5

Actionability

Concrete prescriptive guidance with specific values ('Keep parallax below 5%', 'hard grid lines, square media, low radii') and enumerated states, but as an instruction-only skill it offers no executable code or scaffolding, leaving it just short of fully copy-paste ready.

4 / 5

Workflow Clarity

A clear 5-step 'Establish the Story' sequence pairs with an explicit 'Validate' checklist and a corrective 'Avoid' list, but there is no explicit validate-fix-retry loop wording to reach a 5.

4 / 5

Progressive Disclosure

Self-contained and well-sectioned with clear headers and no nested references, but at ~80 lines (above the 50-line simple-skill threshold) the dense enumerated state lists could be tightened or split to fully earn a 5.

4 / 5

Total

17

/

20

Passed

Description

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

The description is strong: it states concrete capabilities, an explicit 'Use for' trigger clause, and a distinctive niche, all in third-person imperative voice. The only minor gap is that some trigger terms are specialized design vocabulary rather than the most common user phrasing.

DimensionReasoningScore

Specificity

Lists multiple concrete actions ('Create or redesign enterprise AI, automation, security, and operations product pages that explain system boundaries, approvals, auditability, exceptions, and rollback') with comprehensive coverage of the skill's scope.

5 / 5

Completeness

Explicitly answers both 'what' (create/redesign product pages that explain operational boundaries, approvals, auditability, exceptions, rollback) and 'when' via a clear 'Use for...' clause with concrete trigger phrases.

5 / 5

Trigger Term Quality

Good keyword coverage across both the domain ('enterprise AI, automation, security, operations product pages') and distinctive design triggers ('dark cinematic heroes', 'expandable solution rows', 'case-study evidence', 'waitlist handoffs'), though some terms lean on specialized design jargon and a few natural phrases like 'landing page' are absent.

4 / 5

Distinctiveness Conflict Risk

Targets a clear niche (enterprise operational AI/security product pages) with highly distinctive design and content triggers, making conflict with unrelated skills minimal.

5 / 5

Total

19

/

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
MengTo/Skills
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.