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

76%

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 ./skills/share-a-library/SKILL.md

Quality

Content

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

A tight, highly actionable single-purpose skill: exact commands, sensible preconditions, and guardrails covering the main failure modes. The only real gap is verification — nothing confirms the push landed or that the returned install command actually works, and the existing-repo branch lacks a concrete command.

Suggestions

Add an explicit verification checkpoint after publishing, e.g. confirm `git remote -v` shows origin and that `gh repo view <owner>/<repo>` succeeds before returning the install command.

Give the "repo already exists" guardrail a concrete command sequence (e.g., `git remote add origin <url> && git push -u origin main`) instead of directional guidance.

Trim the redundancy between Preconditions and step 1 (both restate the build-docs requirement) to tighten token efficiency.

Dimension	Reasoning	Score
Conciseness	The body is lean and command-first with no explanation of concepts Claude already knows, but Preconditions duplicates step 1's build-docs instruction and the "Done" section restates step 3's return value — minor trimmable redundancy.	4 / 5
Actionability	Copy-paste-ready commands cover the main path (build-docs, git init/add/commit, gh repo create --push) and both install variants, but the "repo already exists" branch gives only directional guidance ("connect the existing remote and push") without a concrete command.	4 / 5
Workflow Clarity	A clearly numbered three-step sequence with Preconditions as an entry checkpoint and a guardrail for the duplicate-repo failure mode, but there is no post-publish verification step (e.g., confirm the push succeeded or that the install command resolves).	4 / 5
Progressive Disclosure	The ~58-line body needs no external references and is cleanly sectioned (Goal, Preconditions, Workflow, Guardrails, Done) with nothing inlined that belongs in a separate file, matching the simple-skill case for a top score.	5 / 5
	Total	17 / 20 Passed

Description

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

A strong description with an explicit trigger clause, concrete outcomes, and third-person voice. Its main limitation is that the capability side relies on the generic phrase "GitHub publishing steps" instead of enumerated actions, and it lacks natural synonym triggers like "share" or "repo".

Suggestions

Enumerate the concrete actions in the description (e.g., "Initialize the git repo, create the GitHub repo with gh, push, and return the install command") instead of the generic "Run the GitHub publishing steps".

Add natural trigger synonyms users would say, such as "share", "publish", or "make the library installable", alongside "publish to GitHub".

Dimension	Reasoning	Score
Specificity	"Run the GitHub publishing steps" and "return the exact shareable install command" name several concrete actions, but "publishing steps" is never enumerated, leaving minor gaps in coverage.	4 / 5
Completeness	Both parts are present — an explicit "Use when a managed library is ready to publish to GitHub" trigger plus a clear what — but the what ("Run the GitHub publishing steps") stays at a slightly generalized level rather than enumerating concrete actions, so it sits between the 4 and 5 anchors.	4 / 5
Trigger Term Quality	"publish to GitHub", "install command", and "teammates" are phrases users would naturally say, but common synonyms such as "share", "repo", or "make public" are missing.	4 / 5
Distinctiveness Conflict Risk	The "managed library… install command… GitHub" framing carves a clear niche distinct from generic git skills, though "managed library" is internal jargon and generic GitHub-publishing skills retain minor overlap.	4 / 5
	Total	16 / 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: 6d95c78

Reviewed: 6 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.