How do I install the Find Reuse skill?

Run npx skillmds@latest add shkarupa-alex/find-reuse in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Find Reuse safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Find Reuse?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Find Reuse free to use?

Yes. Installing skills from SkillMD is free. This skill is licensed under MIT.

Who published Find Reuse?

shkarupa-alex (@shkarupa-alex) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Find Reuse by shkarupa-alex — Agent Skill

Name: Find Reuse
Author: shkarupa-alex

File contents

Find reusable solutions

This skill is a portable report producer. It knows no caller-specific paths, feature lifecycle, destination document or commit policy. It never writes repository files, installs tools, logs in, or asks for credential values.

Read Request and report contracts and Source adapter contract completely before searching.

Input

Accept only a Markdown request whose YAML block declares contract: find-reuse.request.v1. Reject an absent or unknown contract before searching. Preserve every business requirement id and priority.

Search

Detect applicable surfaces from the request, repository remotes, manifests, lockfiles and imports. A named private source remains applicable when auth is missing.
Probe each required tool and exact capability before use. Give OS-aware install or login help when unavailable, but do not install or authenticate.
Run commands as argument arrays. Never interpolate a query into a shell string. Record errors as coverage gaps, not empty results.
Perform required discovery on every applicable surface, then enrich each finalist from its source host and registry when both exist.
Merge identities only with authoritative package metadata or repository-owned evidence. Keep forks, mirrors and monorepo members distinct.
Compare requirements, integration cost, provenance, license, maintenance, adoption and security evidence. Preserve source, observation time and metric window; never compare popularity numbers across ecosystems as one scale.

For a new component without a fixed ecosystem, search GitHub and GitLab plus registries for the two most suitable allowed stacks and record the rationale.

Output

Return one complete find-reuse.report.v1 Markdown document and nothing that claims repository mutation. Include every required section and every applicable surface, including failures and unknowns.

build is allowed only with coverage: complete. If any required tool, auth, source or enrichment is unavailable, return status: unknown and coverage: partial|blocked. A genuine empty result is evidence only after a successful operation.

This skill does not decide where the report is saved or whether implementation may proceed after unknown; those decisions belong to its caller.

---name: find-reusedescription: Produce a portable, read-only evidence report about whether to reuse, extend, or build. Run only for an explicit reuse-research request; do not trigger for ordinary package questions.license: MIT---# Find reusable solutionsThis skill is a portable report producer. It knows no caller-specific paths, featurelifecycle, destination document or commit policy. It never writes repositoryfiles, installs tools, logs in, or asks for credential values.Read [Request and report contracts](references/contracts.md) and[Source adapter contract](references/adapters.md) completely before searching.## InputAccept only a Markdown request whose YAML block declares`contract: find-reuse.request.v1`. Reject an absent or unknown contract beforesearching. Preserve every business requirement id and priority.## Search1. Detect applicable surfaces from the request, repository remotes, manifests, lockfiles and imports. A named private source remains applicable when auth is missing.2. Probe each required tool and exact capability before use. Give OS-aware install or login help when unavailable, but do not install or authenticate.3. Run commands as argument arrays. Never interpolate a query into a shell string. Record errors as coverage gaps, not empty results.4. Perform required discovery on every applicable surface, then enrich each finalist from its source host and registry when both exist.5. Merge identities only with authoritative package metadata or repository-owned evidence. Keep forks, mirrors and monorepo members distinct.6. Compare requirements, integration cost, provenance, license, maintenance, adoption and security evidence. Preserve source, observation time and metric window; never compare popularity numbers across ecosystems as one scale.For a new component without a fixed ecosystem, search GitHub and GitLab plusregistries for the two most suitable allowed stacks and record the rationale.## OutputReturn one complete `find-reuse.report.v1` Markdown document and nothing thatclaims repository mutation. Include every required section and every applicablesurface, including failures and unknowns.`build` is allowed only with `coverage: complete`. If any required tool, auth,source or enrichment is unavailable, return `status: unknown` and`coverage: partial|blocked`. A genuine empty result is evidence only after asuccessful operation.This skill does not decide where the report is saved or whether implementationmay proceed after `unknown`; those decisions belong to its caller.

Frequently asked questions

Find Reuse