openai-knowledge

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

Quality

42%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

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

Quality

Content

50%

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

The content is well-organized into clear sections and free of unnecessary concept explanations, but it is mildly repetitive and its core value — delegation to a canonical sibling skill — is undercut because that sibling bundle does not exist. No verification step guards the delegation.

Suggestions

Collapse the redundant Purpose, Resolution Order, and Minimal Workflow sections into a single concise section to remove the threefold restatement of the same routing instruction.

Add a validation checkpoint that confirms ../openai-docs/SKILL.md exists and is readable before delegating, with a fallback if the canonical payload is missing.

Either include the canonical openai-docs bundle so the referenced paths resolve, or note explicitly that this alias requires the sibling openai-docs skill to be installed.

Dimension	Reasoning	Score
Conciseness	The body is short and free of concept-explanation bloat, but the Purpose, Resolution Order, and Minimal Workflow sections restate the same 'delegate to openai-docs, keep this thin' idea three times and could be tightened.	2 / 3
Actionability	It gives concrete file paths and a concrete reporting rule, but the canonical payload it delegates to (../openai-docs/SKILL.md and its references/scripts) does not exist in the bundle, leaving the guidance pointing at a missing target.	2 / 3
Workflow Clarity	Resolution Order and Minimal Workflow provide a clearly numbered sequence, but there is no validation checkpoint confirming that the sibling openai-docs payload actually resolved before reporting under the alias.	2 / 3
Progressive Disclosure	The body is cleanly sectioned and signals one-level-deep references to ../openai-docs, but the referenced sibling bundle is absent, so the signaled navigation does not resolve to real files.	2 / 3
	Total	8 / 12 Passed

Description

35%

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 clearly states the alias's purpose and names its domain, but relies on internal routing jargon rather than natural user triggers and omits any 'when to use it' guidance. It also overlaps deliberately with the canonical openai-docs skill it delegates to.

Suggestions

Add an explicit 'Use when...' clause stating when this alias should be selected (e.g. 'Use when a caller requests openai-knowledge or OpenAI platform documentation guidance').

Replace internal jargon like 'canonical local payload' and 'route compatibility' with natural trigger terms a user would actually say, such as 'OpenAI docs', 'OpenAI API reference', or 'platform documentation'.

Differentiate the alias from the canonical openai-docs skill in the description, or clarify it is purely a routing shim, to reduce distinctiveness/conflict risk.

Dimension	Reasoning	Score
Specificity	It names a domain (OpenAI platform documentation) and one concrete action ('Delegate to the canonical local `openai-docs` payload'), but does not list multiple specific concrete capabilities.	2 / 3
Completeness	It clearly states what the skill does, but there is no 'Use when...' clause or any explicit when-to-use trigger, capping completeness at 2 per the rubric.	2 / 3
Trigger Term Quality	The terms used ('compatibility alias', 'canonical local payload', 'route compatibility') are internal technical jargon rather than natural keywords a user would say; only 'OpenAI platform documentation' is remotely user-facing.	1 / 3
Distinctiveness Conflict Risk	It targets a specific named niche (OpenAI docs via the openai-docs skill), but as an alias it deliberately mirrors that canonical skill's purpose, creating real overlap/conflict risk.	2 / 3
	Total	7 / 12 Passed

Validation

100%

Warnings & errors only

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
Commit: f627ab5

Reviewed: about 2 hours ago

Table of Contents

Discovery Implementation Validation

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.