session-crosslink

Use when an agent session ran outside the repo whose commits should record it — e.g. launched from a higher-level folder, a non-Entire repo, or one repo but editing another — to attach the session to each affected Entire-enabled repo's HEAD commit.

Quality

88%

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

88%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 body is a tight, executable workflow with strong validation guardrails appropriate to a destructive batch operation. It scores high on actionability and workflow clarity; minor conciseness and organization tweaks would push it higher.

Dimension	Reasoning	Score
Conciseness	Lean and command-driven with no padding about concepts Claude already knows; the only trimmable excess is the closing "Why this skill exists" rationale and a few restated guardrail sentences.	4 / 5
Actionability	Provides fully executable bash commands with clearly marked parameters (e.g. `cd <repo> && entire session attach <session-id> --agent <agent> --force`) plus concrete preview-table and summary examples covering the common cases.	5 / 5
Workflow Clarity	A clear five-step sequence with explicit validation (preview-then-confirm before any HEAD amend), per-repo exit-status capture, and a failure-modes section giving error-recovery feedback loops for a destructive batch operation.	5 / 5
Progressive Disclosure	No bundle files exist, so all content lives in one well-organized file with clear section headers and no nested references; the single inline "Why this skill exists" block is a minor organization gap rather than a separate-file candidate.	4 / 5
	Total	18 / 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.

The description is well-constructed: it states a concrete action, gives explicit "Use when" triggers with realistic scenarios, and occupies a distinct niche. The only weakness is reliance on Entire-specific jargon in trigger terms.

Dimension	Reasoning	Score
Specificity	Names a concrete action ("attach the session to each affected Entire-enabled repo's HEAD commit") plus concrete trigger contexts (higher-level folder, non-Entire repo, one repo editing another), with only minor coverage gaps.	4 / 5
Completeness	Explicitly answers both what (attach session to affected repos' HEAD commit) and when ("Use when an agent session ran outside the repo ... e.g. ...") with concrete trigger phrases.	5 / 5
Trigger Term Quality	Includes natural trigger phrases ("session ran outside the repo", "launched from a higher-level folder", "one repo but editing another") but leans on tool-specific jargon ("Entire-enabled repo", "HEAD commit") that users may not always say.	4 / 5
Distinctiveness Conflict Risk	Targets a clear niche (crosslinking an out-of-repo agent session to Entire-enabled repos) with distinct triggers and minimal overlap risk 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: SnowingFox/ai-skills
Path: .agents/skills/session-crosslink/SKILL.md
Commit: d6882ad

Reviewed: ~15 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.