CtrlK
BlogDocsLog inGet started
Tessl Logo

session-link

Use when an agent must identify or link the Paper recording of its own running session, or link a known session or matched turn — "what's my session id", "link to this session", "share this session", "is this being recorded", "open this run in the console", "paper session link". Resolves the tapes session id with `paperctl sessions` and builds the console URL.

80

Quality

100%

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

100%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 executable, well-sequenced, and concise, leading with the one genuinely non-obvious trap (two ids) and backing every step with concrete commands and a verification checkpoint. Organization is clean and self-contained.

DimensionReasoningScore

Conciseness

Lean throughout: the only explanatory passages (the two-id trap, harness_session_id vs id) are domain knowledge Claude does not already have, and there is no padding or restatement of basic concepts.

5 / 5

Actionability

Provides copy-paste-ready commands for every common case — Claude Code lookup, any-harness footprint matching, `sessions get` verification, `whoami --json`, and explicit URL construction — plus a Quick reference table indexing them.

5 / 5

Workflow Clarity

A numbered workflow (resolve → verify → build link) with an explicit validation checkpoint (`sessions get`) and clear fallback branches for zero/multiple candidates; the operation is non-destructive so no batch cap applies.

5 / 5

Progressive Disclosure

No bundle files exist and none are needed; the body is organized into well-labeled sections (Overview, the trap, workflow, turn linking, quick reference, common mistakes, prerequisites) making navigation easy within a single file.

5 / 5

Total

20

/

20

Passed

Description

100%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 tight, third-person description that pairs concrete capabilities with a rich set of natural trigger phrases and an explicit use-when clause. It cleanly separates its niche from the sibling search skill.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — "identify or link the Paper recording of its own running session", "link a known session or matched turn", "Resolves the tapes session id with `paperctl sessions` and builds the console URL" — covering the full linking workflow comprehensively.

5 / 5

Completeness

Explicitly answers both what (resolves the tapes session id and builds the console URL) and when ("Use when an agent must identify or link the Paper recording...") with concrete trigger phrases.

5 / 5

Trigger Term Quality

Embeds natural user phrases users would actually say — "what's my session id", "link to this session", "share this session", "is this being recorded", "open this run in the console", "paper session link" — with strong synonym coverage.

5 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (session linking by identity) and explicitly carves it off from the `search` skill, leaving minimal overlap risk with neighboring skills.

5 / 5

Total

20

/

20

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
papercomputeco/skills
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.