AgentStack
Sign in Publish
MCP servers Skills Toolkits Why AgentStack Sell Docs
Sign in
SKILL verified MIT Self-run

Find Tool

skill-paulrberg-dot-agents-find-tool · by PaulRBerg

A Claude skill from PaulRBerg/dot-agents.

↗ Repository
— No reviews yet
0 installs
9 views
0.0% view→install

Install

$ agentstack add skill-paulrberg-dot-agents-find-tool

✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • ✓ Prompt-injection patterns
  • ✓ Secret / credential exfiltration
  • ✓ Dangerous shell & filesystem operations
  • ✓ Untrusted network calls
  • ✓ Known-malicious package signatures

What it can access

  • ✓ Network access No
  • ✓ Filesystem access No
  • ✓ Shell / process execution No
  • ✓ Environment & secrets No
  • ✓ Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

Are you the author of Find Tool? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

Find Tool

Recommend the current option that best fits the user's actual constraints, backed by fresh primary evidence.

Workflow

  1. Infer the ecosystem, existing stack, must-haves, switching cost, and decision criteria from the request and

repository. Ask only when an unknown would materially change the recommendation.

  1. Check whether the standard library, platform, or an already-installed tool is sufficient before adding a dependency.
  2. Search current authoritative sources. Read [references/find-tool.md](references/find-tool.md) only for the relevant

ecosystem's source routing, fallback criteria, install conventions, and red flags.

  1. Compare the viable options against the user's criteria. Use adoption, maintenance, security, documentation,

performance, operational cost, and ecosystem fit only where they affect this decision; do not force fixed weights or a fixed number of candidates.

  1. Recommend one option when the evidence supports it. State the decisive tradeoff, material red flags, and the closest

alternative. Say when the evidence is too close or no external tool is justified.

Defaults

  • With no repository evidence, default to JavaScript/TypeScript and Node.js tooling.
  • Prefer standard-library or platform primitives when adequate.
  • For JavaScript installs, prefer the repository's package manager and otherwise ni; for macOS CLIs, prefer an

official or well-maintained Homebrew formula.

  • Prefer registries, official docs, repositories, changelogs, and security advisories over secondary comparisons. For

agent skills, search registries and GitHub because no single index is complete.

Completion

The answer is complete when the recommendation is traceable to current sources, the deciding criteria are explicit, installation guidance matches the user's environment, and uncertainties or disqualifying risks are visible. Use a table only when repeated fields make the comparison easier to scan.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet — be the first.

Write a review

Versions

  • v0.1.0 Imported from the upstream source.

More in Agent Skills