speckit-git-remote

Detect Git remote URL for GitHub integration

Quality

66%

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 ./.claude/skills/speckit-git-remote/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.

The skill body is concise, actionable, and well-structured for a simple read-only detection task, with concrete commands and clear degradation behavior. Its only weak spot is that URL parsing is described narratively rather than given as executable code.

Dimension	Reasoning	Score
Conciseness	The body is lean with no padding about what Git is, using tight sections and concrete commands; the only minor redundancy is the opening line restating the description.	4 / 5
Actionability	It gives copy-paste-ready commands (`git rev-parse --is-inside-work-tree`, `git config --get remote.origin.url`) and concrete URL-parsing examples, though the parsing logic is described rather than provided as executable code.	4 / 5
Workflow Clarity	A clear Prerequisites → Execution → Output → Graceful Degradation sequence with a pre-check (Git availability) and a CAUTION guard is present; no validate-fix-retry loop is needed for this read-only task.	4 / 5
Progressive Disclosure	At under 50 lines with no external references needed, the content is well-organized into clearly labeled sections, meeting the simple-skill exception for progressive disclosure.	5 / 5
	Total	17 / 20 Passed

Description

53%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 clear and concrete about a single action but omits any explicit 'when to use' guidance and offers limited trigger-term variation. It is distinct enough to avoid most conflicts but would benefit from a Use-when clause.

Suggestions

Add an explicit trigger clause, e.g. 'Use when you need the GitHub remote owner/repo for issue creation or GitHub integration.'

Broaden trigger terms to include synonyms users naturally say, such as 'git remote', 'origin URL', or 'GitHub repo'.

Optionally name the extracted outputs (owner, repo, isGitHub) in the description to raise specificity.

Dimension	Reasoning	Score
Specificity	The phrase 'Detect Git remote URL' names the domain and one concrete action (detect) with a stated purpose ('for GitHub integration'), but coverage is limited to that single action rather than a comprehensive set.	3 / 5
Completeness	It clearly states what the skill does ('Detect Git remote URL for GitHub integration') but provides no 'Use when...' trigger clause, which caps completeness at 3 per the rubric.	3 / 5
Trigger Term Quality	It includes relevant natural terms ('Git remote URL', 'GitHub') that a user would say, but lacks common variations, synonyms, or file-format cues.	3 / 5
Distinctiveness Conflict Risk	The narrow niche of detecting a Git remote URL for GitHub integration is mostly distinct with only minor overlap risk against general git utility skills.	4 / 5
	Total	13 / 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
metadata_version	'metadata.version' is missing	Warning

	Total	15 / 16 Passed

Repository: unoplatform/uno
Path: .claude/skills/speckit-git-remote/SKILL.md
Commit: eaa505e

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