links

Write any link or URL so it resolves where it is rendered, not where it lives in the repo. Use when authoring or editing a link — in docs, source docstrings, READMEs (incl. npm-published), or product UI: docs cross-refs, "see SECURITY.md", universal `/_/` routes, GitHub URLs.

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

82%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 reference whose decision tables and exact URL templates leave little ambiguity about what to do, anchored by a verification-gated checklist. Slight room remains to trim framing prose and to consider splitting the URL-reference or hard-rules material into a bundled reference file.

Suggestions

Trim rhetorical framing lines (e.g., 'This skill is the single source of truth for which form to use; docs/AGENTS.md defers here' and 'Everything below is just the answer table') to tighten conciseness without losing the decision content.

Consider moving the Grida-URL reference table and/or the Hard rules into a references/ file linked from the body, which would shorten the inline SKILL.md and give progressive_disclosure a clearer one-level-deep structure.

Strengthen workflow_clarity by reframing 'The pass' as an explicit validate→fix→retry loop for the pre-commit gate (step 7), so a failed git ls-files / git check-ignore check routes back to 'replace with a committed path / public URL' rather than ending the checklist.

Dimension	Reasoning	Score
Conciseness	Dense, table-driven reference that largely assumes Claude's competence and earns most of its prose (e.g., rationale for hosted docs URLs, why relative links break across hosts); a few framing sentences ('the single source of truth', 'Question 3 is the one that must not break') could be trimmed without loss.	4 / 5
Actionability	Fully actionable instruction-only guidance: exact URL templates (grida.co/docs/<path>, github.com/gridaco/grida/blob/main/<path>), a render-host→target→form decision table, and concrete transforms (drop the docs/ prefix and the extension) that cover the common cases copy-paste ready.	5 / 5
Workflow Clarity	'The pass' gives a clear 7-step numbered checklist with an explicit validation gate (step 7: verify the referent exists via git ls-files / git check-ignore) and the three-questions framing, but it is a one-way checklist rather than a validate→fix→retry feedback loop.	4 / 5
Progressive Disclosure	Well organized into clear headed sections (Surfaces, Decision table, Grida URLs, The forms, Hard rules, The pass) with tables for easy navigation, but no bundle files exist and the content exceeds 50 lines, so the simple-skill auto-5 does not apply and nothing is split out.	4 / 5
	Total	17 / 20 Passed

Description

87%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, well-targeted description that cleanly states what the skill does and when to use it, with concrete surfaces and trigger phrases. The only mild weakness is that the action framing is essentially a single verb applied across surfaces rather than a list of distinct capabilities.

Dimension	Reasoning	Score
Specificity	Names a concrete action (write links/URLs so they resolve at the render surface) and enumerates several concrete surfaces with examples — docs, source docstrings, READMEs (incl. npm-published), product UI, with 'see SECURITY.md', universal `/_/` routes, GitHub URLs — but the core action is essentially singular rather than a list of multiple distinct actions.	4 / 5
Completeness	Explicitly answers both what ('Write any link or URL so it resolves where it is rendered, not where it lives in the repo') and when ('Use when authoring or editing a link — in docs, source docstrings, READMEs (incl. npm-published), or product UI') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Good coverage of natural terms a user would say — 'link', 'URL', 'docs', 'README', 'GitHub URLs', 'SECURITY.md' — with synonyms (link/URL), though a few common variants like 'markdown link', 'relative path', or 'anchor' are absent.	4 / 5
Distinctiveness Conflict Risk	A clear niche — link/URL resolution keyed to render surface rather than repo location — with distinct, specific triggers (docs cross-refs, universal `/_/` routes, GitHub URLs, npm READMEs) and minimal overlap with other skills.	5 / 5
	Total	18 / 20 Passed

Validation

100%

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

Validation for skill structure

No warnings or errors.

Repository: gridaco/grida
Path: .agents/skills/links/SKILL.md
Commit: 8ef5e53

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