github-repo-management

Clone/create/fork repos; manage remotes, releases.

Quality

51%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

High

Do not use without reviewing

Fix and improve this skill with Tessl

tessl review fix ./skills/github/github-repo-management/SKILL.md

Quality

Content

42%

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

The content is highly actionable with executable commands throughout, but it is excessively verbose and monolithic — repeating `gh`/`curl` recipes and an endpoint table inline rather than offloading detail to the provided cheatsheet reference and adding validation checkpoints.

Suggestions

Collapse the `gh` + `git + curl` duplication: lead with the canonical command and reference references/github-api-cheatsheet.md for the raw API endpoints instead of restating them inline.

Link the existing references/github-api-cheatsheet.md from the body (e.g. a '## API reference' section) so the cheatsheet bundle is actually discoverable rather than orphaned.

Add validation checkpoints for destructive/batch operations (verify a fork or release was created before cloning/uploading, confirm branch protection was applied) to raise workflow clarity.

Dimension	Reasoning	Score
Conciseness	At ~500 lines the body is a dense catalog of near-duplicate `gh` and `git + curl` recipes plus inline python3 formatters and a quick-reference table restating the same endpoints, padding the context with repetition Claude does not need.	1 / 3
Actionability	Every section provides fully executable, copy-paste-ready `gh`, `git`, and `curl` commands with real endpoints, payloads, and inline python3 parsing snippets for concrete GitHub operations.	3 / 3
Workflow Clarity	Operations are grouped by task, but destructive/batch operations (repo create, branch protection, secret set, release upload) have no validation checkpoints or feedback loops to confirm success before proceeding.	2 / 3
Progressive Disclosure	The body is a monolithic wall of inline reference material; the existing references/github-api-cheatsheet.md bundle is never linked from the body, so detail that belongs in a separate file is duplicated inline with no navigation.	1 / 3
	Total	7 / 12 Passed

Description

60%

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 specific and concise, listing concrete GitHub repository operations, but it lacks an explicit "Use when..." trigger clause and broader natural trigger terms, which limits completeness and trigger quality.

Suggestions

Add an explicit trigger clause, e.g. 'Use when creating, cloning, forking, or managing GitHub repositories and releases.'

Broaden trigger terms to include natural phrasings like 'GitHub repository', 'push', 'pull', or 'backup a repo' that users would actually say.

Sharpen distinctiveness from sibling skills (github-pr-workflow, github-issues) by scoping the description to repository lifecycle rather than general git operations.

Dimension	Reasoning	Score
Specificity	The description names multiple concrete actions — "Clone/create/fork repos; manage remotes, releases." — listing five distinct operations rather than vague language.	3 / 3
Completeness	It clearly answers "what" (clone/create/fork; manage remotes/releases) but lacks any "Use when..." or equivalent explicit "when" trigger guidance, which caps completeness at 2 per the guidelines.	2 / 3
Trigger Term Quality	It includes relevant terms (repos, remotes, releases, clone, fork) but omits common natural variations users would say such as "GitHub", "repository", "push", "pull", or "backup".	2 / 3
Distinctiveness Conflict Risk	The scope (clone/create/fork/remotes/releases) is reasonably specific but could still overlap with generic git skills or the related github-pr-workflow/github-issues skills, so it is not a clearly distinct niche.	2 / 3
	Total	9 / 12 Passed

Validation

75%

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

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (517 lines); consider splitting into references/ and linking	Warning
metadata_version	'metadata.version' is missing	Warning
metadata_field	'metadata' should map string keys to string values	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	12 / 16 Passed

Repository: NousResearch/hermes-agent
Path: skills/github/github-repo-management/SKILL.md
Commit: 6a8d318

Reviewed: about 14 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.