CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

openai-knowledge

Compatibility alias for OpenAI platform documentation guidance. Delegate to the canonical local `openai-docs` payload while preserving route compatibility.

42

Quality

53%

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

Fix and improve this skill with Tessl

tessl review fix ./bundled/skills/openai-knowledge/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

50%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 content is a cleanly structured, lean alias stub, but its entire value is a redirect to a sibling openai-docs skill that is not present in this workspace, leaving it without executable guidance or working references. Scores are pulled down by the dangling cross-skill references and the absence of any local payload.

Suggestions

Either include the openai-docs sibling in the bundle or replace the cross-directory references with content that exists, so the workflow is actually followable.

Add a fallback note describing what to do if the canonical sibling is absent, so the skill degrades gracefully instead of pointing at nothing.

Since the alias carries no local material, consider collapsing the resolution steps into a single explicit instruction to reduce redundancy between Purpose and Resolution Order.

DimensionReasoningScore

Conciseness

The body is lean and sectioned without explaining concepts Claude already knows; the only slack is mild redundancy between the Purpose bullets and the Resolution Order list, which keeps it just below a 5.

4 / 5

Actionability

It offers only high-level hints ('Read ../openai-docs/SKILL.md', 'Use canonical references and scripts from ../openai-docs/') pointing at a sibling directory that does not exist in this workspace, so there is no executable guidance to follow.

2 / 5

Workflow Clarity

The Minimal Workflow lists a sequenced three-step delegation, but the meaningful workflow is deferred to the missing ../openai-docs/SKILL.md, leaving the actual process and any checkpoints unresolved.

3 / 5

Progressive Disclosure

Sections are well-organized and the skill is appropriately thin for an alias, but every reference points to a non-existent sibling (../openai-docs/SKILL.md, references/**, scripts/**), so the navigation signaled in the body does not resolve.

3 / 5

Total

12

/

20

Passed

Description

33%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 explains the skill's aliasing role in third person but is framed as internal infrastructure jargon with no user-facing trigger guidance. It is capped on completeness by the missing 'Use when...' clause and scores low on distinctiveness because an alias inherently conflicts with its canonical counterpart.

Suggestions

Add a 'Use when...' clause with natural trigger phrases a caller would actually say (e.g. 'Use when a caller requests openai-knowledge for OpenAI platform documentation guidance').

Replace internal jargon ('payload', 'route compatibility') with user-facing language about what guidance is provided.

Clarify how this alias differs in behavior from the canonical openai-docs skill so it is distinguishable rather than a pure duplicate.

DimensionReasoningScore

Specificity

Names the domain ('OpenAI platform documentation guidance') but the only stated actions — 'Delegate to the canonical local openai-docs payload' and 'preserving route compatibility' — are minimal and generic rather than concrete capabilities.

2 / 5

Completeness

It gives a clear 'what' (an alias that delegates to openai-docs) but no 'when' trigger guidance; per the rubric a missing 'Use when...' clause caps completeness at 3.

3 / 5

Trigger Term Quality

The natural term 'OpenAI platform documentation' appears, but the framing leans on internal jargon ('compatibility alias', 'payload', 'route compatibility') that a user would never say when they need this skill.

2 / 5

Distinctiveness Conflict Risk

As an explicit alias it deliberately duplicates the canonical openai-docs skill, creating direct overlap with its sibling and making it not independently distinguishable.

2 / 5

Total

9

/

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

foryourhealth111-pixel/Vibe-Skills

Path

bundled/skills/openai-knowledge/SKILL.md

Revision

5ce2258

Reviewed

Table of Contents

DiscoveryImplementationValidation

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.

Claim skill