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.

75

Quality

92%

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

100%

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

A well-crafted, instruction-only design skill: lean, concrete, and measurably actionable, with a clear sequenced workflow and an explicit validation phase. Content is appropriately self-contained with clean section navigation.

DimensionReasoningScore

Conciseness

Dense prescriptive bullets with no padding or explanation of concepts Claude already knows; every line adds skill-specific guidance, matching the lean-and-efficient anchor.

3 / 3

Actionability

Concrete, measurable directives throughout ('near-black, warm white, muted gray', '160-220ms for controls and 500-760ms for section entrances', 'Keep parallax below 5%', '200% zoom'), giving copy-paste-ready instruction-only guidance.

3 / 3

Workflow Clarity

A numbered 1-5 narrative sequence in 'Establish the Story' plus an explicit 'Validate' checklist (review against evidence, test, verify, remove unsupported claims) forms a clear build-then-validate feedback loop.

3 / 3

Progressive Disclosure

No bundle files exist and the body has no external references; the ~75 lines are organized into seven clear thematic sections, which is appropriate for a self-contained focused skill per the simple-skills scoring note.

3 / 3

Total

12

/

12

Passed

Description

85%

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 specific, complete, and distinctive description with a clear what-and-when structure. Its only weakness is trigger-term naturalness: the visual-style keywords lean toward design-specialist jargon rather than language a typical user would say.

Suggestions

Add plain-language trigger variants users actually say (e.g., 'SaaS landing page', 'B2B product page', 'enterprise software marketing site') alongside the specialized visual terms.

Soften or gloss the most niche aesthetic terms (e.g., 'metric pauses', 'hairline grids') with a more common equivalent so the trigger reads naturally to non-designers.

Keep the strong domain coverage ('enterprise AI, automation, security, and operations product pages') as the primary trigger since those are the most natural entry points.

DimensionReasoningScore

Specificity

Lists multiple concrete actions ('Create or redesign ... product pages that explain system boundaries, approvals, auditability, exceptions, and rollback'), matching the comprehensive-action anchor rather than the partial-coverage anchor at 2.

3 / 3

Completeness

Clearly states what the skill does and provides an explicit 'Use for ...' trigger clause for when to invoke it, satisfying the both-what-and-with-explicit-triggers anchor.

3 / 3

Trigger Term Quality

Domain terms ('enterprise AI, automation, security, operations product pages') are natural, but several visual triggers ('dark cinematic heroes', 'hairline grids', 'metric pauses') are specialized design jargon an average user would not naturally say, and common plain variations ('SaaS landing page', 'B2B product page') are absent.

2 / 3

Distinctiveness Conflict Risk

A highly specific niche (enterprise AI/automation/security/operations product pages with a dark cinematic aesthetic and an approval/rollback model) makes it unlikely to trigger for the wrong skill.

3 / 3

Total

11

/

12

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.