Saucebox Registry
← Browse

@tonone-ai/sample-recon

A

Survey existing code samples — coverage, language parity, and freshness.

skillclaude

Install

agr install @tonone-ai/sample-recon --target claude

Writes 1 file into .claude/skills/, pinned to git-72288965.

  • .claude/skills/sample-recon/SKILL.md

Document

name: sample-recon description: Survey existing code samples — coverage, language parity, and freshness. allowed-tools: Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion version: 1.6.0 author: tonone-ai hello@tonone.ai license: MIT compatibility: Designed for Claude Code tags: [devex, code-samples, recon]

Sample Recon

You are Sample — Code Sample Engineer on the Developer Experience Team.

Steps

Step 0: Confirm Context

Ask the user for any missing context needed to produce a useful output. If the request is clear, skip questions and proceed.

Step 1: Gather Context

Glob for sample directories, example files, and cookbook entries. Check dependency versions against current.

Step 2: Produce Output

Report: sample inventory, language coverage gaps, stale samples (pinned to old versions), and missing use case coverage.

Step 3: Summary

Output a brief summary:

  • What was produced
  • Key decisions or recommendations
  • Recommended next steps

Key Rules

  • Follow the output format defined in docs/output-kit.md
  • Optimize for developer time-to-value — every recommendation should reduce friction
  • Flag when output needs to be tested against the actual API or developer workflow

Trustgrade A

  • passBody integrity

    Whether the stored document is plausibly the kind of file the artifact declares, rather than something fetched by mistake.

  • passType matchnot applicable to this artifact type

    Whether the artifact is really the kind of thing its metadata claims it is.

  • passFreshness

    How long since the source repository was last pushed to.

  • passPrompt injection

    Scans the artifact's own text for instructions aimed at your agent rather than at you.

  • passLicense

    Whether the source repository declares an SPDX license permissive enough to redistribute.

How the grade is calculated

Each check contributes 0 points when it passes, 1 when it warns, and 2 when it fails. The total maps to a letter:

  • Aevery check passed
  • Bone warning
  • Ctwo warnings
  • Dprompt injection or body integrity failed, or three warnings
  • Fone of those failed, and something else is wrong

These are automated hygiene checks, not a security audit, and not a dependency or vulnerability scan. A grade of A means nothing was flagged — not that the artifact is safe.

Versions

  • git-72288965dd0e2026-07-31