share-a-library

Use when a managed library is ready to publish to GitHub and hand to teammates as an install command. Run the GitHub publishing steps, then return the exact shareable install command.

Quality

85%

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

Quality

Content

87%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 lean, executable, and well-structured for a simple publishing workflow. The main gap is the absence of an explicit verification step (e.g. confirm the repo exists and the push succeeded) before declaring the install command ready.

Suggestions

Add an explicit validation step after publishing — e.g. 'Verify the remote pushed: run `git ls-remote origin` or confirm `gh repo view` succeeds — only then return the install command.'

Include a checkpoint that the install command actually resolves the published repo (e.g. a dry-run install or confirming the collection name matches) before handing it to teammates.

State what to do if `gh repo create` or the push fails partway, so the agent can recover rather than return a stale install command.

Dimension	Reasoning	Score
Conciseness	The body is lean with no padded explanations of concepts Claude already knows; every section (Goal, Preconditions, Workflow, Guardrails, Done) earns its place.	5 / 5
Actionability	Commands are fully executable and copy-paste ready (git/gh/npx), with explicit branching for the collection vs. whole-library install case covering the common scenarios.	5 / 5
Workflow Clarity	The numbered sequence is clear and guardrails offer recovery guidance, but destructive/batch operations (git init, gh repo create, git push) lack an explicit validation checkpoint before returning the install command, capping this at 3.	3 / 5
Progressive Disclosure	A short, single-purpose skill under 50 lines with no bundle files, organized into clear well-labeled sections, qualifying for the simple-skill exception at 5.	5 / 5
	Total	18 / 20 Passed

Description

82%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 concise, explicit, and clearly distinguishes the skill with both a 'what' and a 'when'. It would benefit from naming a couple more specific actions to lift specificity above 3.

Dimension	Reasoning	Score
Specificity	Names the domain (publishing a managed library to GitHub) and two concrete actions ('Run the GitHub publishing steps', 'return the exact shareable install command'), but coverage is not comprehensive enough for a 4.	3 / 5
Completeness	The 'Use when a managed library is ready to publish...' clause gives an explicit trigger, and 'Run the GitHub publishing steps, then return the exact shareable install command' clearly states what it does.	5 / 5
Trigger Term Quality	Natural trigger terms like 'publish to GitHub', 'install command', and 'shareable' appear with an explicit 'Use when' clause, but a few common synonyms ('share a library', 'GitHub repo') are missing.	4 / 5
Distinctiveness Conflict Risk	The combination of 'managed library', 'publish to GitHub', and 'install command' defines a clear niche with distinct triggers and minimal overlap with other skills.	5 / 5
	Total	17 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: MoizIbnYousaf/ai-agent-skills
Path: skills/share-a-library/SKILL.md
Commit: 1159592

Reviewed: 18 days 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.