CtrlK
BlogDocsLog inGet started
Tessl Logo

speckit-git-remote

Detect Git remote URL for GitHub integration

66

1.42x
Quality

51%

Does it follow best practices?

Impact

98%

1.42x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No known issues

Fix and improve this skill with Tessl

tessl review fix ./.claude/skills/speckit-git-remote/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

70%

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

A well-structured, focused skill for detecting Git remote URLs. Its main weakness is that it describes the URL parsing logic rather than providing executable code for it, and there's some redundancy between the Prerequisites and Graceful Degradation sections. The workflow is clear and appropriate for this single-purpose task.

Suggestions

Add executable parsing code (regex or string manipulation) for extracting owner/repo from both HTTPS and SSH URL formats instead of just describing the extraction.

Consolidate the 'Graceful Degradation' section into 'Prerequisites' to eliminate redundancy — both sections cover the 'Git not available' case.

DimensionReasoningScore

Conciseness

Mostly efficient but has some redundancy — the 'Graceful Degradation' section largely repeats what's already covered in 'Prerequisites', and the explanation of extracting owner/repo from URLs is somewhat verbose for Claude's capabilities.

2 / 3

Actionability

Provides the concrete git commands to run, but lacks executable parsing code for extracting owner/repo from the URL formats. The extraction logic is described rather than implemented, leaving Claude to figure out the regex or string parsing.

2 / 3

Workflow Clarity

For this simple, single-purpose skill, the workflow is clear and well-sequenced: check prerequisites → execute command → parse output → handle failures. The graceful degradation section provides explicit guidance on error handling.

3 / 3

Progressive Disclosure

This is a simple, focused skill under 50 lines with no need for external references. The content is well-organized into logical sections (Prerequisites, Execution, Output, Graceful Degradation) with clear headers.

3 / 3

Total

10

/

12

Passed

Description

32%

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 very terse, naming only a single action (detecting Git remote URL) without explaining when Claude should use this skill or providing broader context about its capabilities. It lacks a 'Use when...' clause and misses common user-facing trigger terms, making it difficult for Claude to reliably select this skill from a large pool.

Suggestions

Add an explicit 'Use when...' clause, e.g., 'Use when the user needs to identify the GitHub repository associated with a local Git project, or when resolving remote origin URLs.'

Expand the capability description to include additional concrete actions if applicable, such as 'Detects and parses Git remote URLs, identifies GitHub owner and repository name, and validates remote connectivity.'

Include more natural trigger terms users might say, such as 'origin', 'repo URL', 'repository remote', or 'GitHub repo link'.

DimensionReasoningScore

Specificity

Names the domain (Git/GitHub) and one action (detect Git remote URL), but only describes a single narrow action without listing additional concrete capabilities.

2 / 3

Completeness

Describes what it does (detect Git remote URL) but has no 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill, which per the rubric caps completeness at 2 at best—and since the 'what' is also quite thin, this lands at 1.

1 / 3

Trigger Term Quality

Includes relevant keywords like 'Git', 'remote URL', and 'GitHub integration', but misses common user variations such as 'origin', 'repo URL', 'repository', or 'push/pull remote'.

2 / 3

Distinctiveness Conflict Risk

Somewhat specific to Git remote URL detection for GitHub, but could overlap with other Git-related or GitHub integration skills since the scope is not clearly delineated.

2 / 3

Total

7

/

12

Passed

Validation

81%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation9 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

9

/

11

Passed

Repository
mixpanel/mixpanel-headless
Reviewed

Table of Contents

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.