CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

75

Quality

92%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

85%

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

An information-dense, well-structured, highly actionable reference that succeeds without code by giving exact URL forms and a validation-backed workflow. Its main weakness is conciseness: the same rules are restated across several sections and could be consolidated.

Suggestions

Collapse the redundant restatements of the absolute-GitHub-URL and hosted-docs-URL rules: keep one authoritative form in the decision table / 'The forms' and have 'Hard rules' and the 'pass' checklist reference it rather than re-deriving it.

The 'pass' checklist largely re-derives the decision table; consider making it a short verification gate ('did you apply the matching row above?') plus the pre-commit check, instead of restating each form.

Trim the philosophical framing that recurs (e.g., 'A link is correct or broken at the surface it is rendered on' reappears conceptually in the three-questions intro and the pass) to a single statement.

DimensionReasoningScore

Conciseness

The content is dense and almost entirely project-specific knowledge Claude lacks (grida hosts, `/_/` universal routes, engine-repo split, docs site no longer publishing engine clusters), so it is not padded with basics — but the same guidance is restated across the decision table, Grida URLs table, 'The forms', 'Hard rules', and the 'pass' checklist (e.g., the absolute-GitHub-URL rule appears ~4 times), so not every token earns its place. It could be tightened by collapsing the redundant restatements.

2 / 3

Actionability

Instruction-only yet highly actionable: exact URL templates (`https://grida.co/docs/<path>`, `…/blob/main/<path>`), explicit transforms (`docs/<path>.md` → drop the `docs/` prefix and extension), distinct file vs directory forms, and a copy-paste-ready pass checklist with verification commands (`git ls-files` / `git check-ignore`).

3 / 3

Workflow Clarity

A clearly sequenced 7-step 'pass' applied to every link, with an explicit validation checkpoint (step 7 pre-commit gate verifying the target is tracked/public). For a single-purpose skill this satisfies the explicit-validation/checklist anchor.

3 / 3

Progressive Disclosure

No bundle files exist, so the skill is a self-contained reference organized into clear, navigable sections (surfaces, decision table, Grida URLs, forms, hard rules, pass), with one one-level-deep, clearly-signaled external reference ('Defined in docs/wg/platform/universal-docs-routing.md; register new user-facing pages there') and no nested indirection.

3 / 3

Total

11

/

12

Passed

Description

100%

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, specific description that names concrete actions, lists natural trigger terms across multiple surfaces, and includes an explicit 'Use when…' clause. It is clearly niched to link-authoring correctness and unlikely to conflict with other skills.

DimensionReasoningScore

Specificity

Lists multiple concrete actions and surfaces — 'Write any link or URL so it resolves where it is rendered', across 'docs, source docstrings, READMEs (incl. npm-published), or product UI' with concrete triggers like 'see SECURITY.md', universal `/_/` routes, GitHub URLs. It goes beyond naming a domain to enumerate specific cases, matching the 'multiple specific concrete actions' anchor.

3 / 3

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 via an explicit 'Use when authoring or editing a link — in docs, source docstrings, READMEs…' clause, satisfying the 'Use when…' requirement.

3 / 3

Trigger Term Quality

Covers natural terms users would actually say — 'link', 'URL', 'docs', 'READMEs', 'product UI', 'GitHub URLs', 'see SECURITY.md' — with good breadth of common variations rather than jargon.

3 / 3

Distinctiveness Conflict Risk

A clear niche — link/URL render-surface correctness — with distinct triggers unlikely to fire for unrelated skills, written in third-person imperative voice with no first/second person.

3 / 3

Total

12

/

12

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
gridaco/grida
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.