Tools

Learns your tool preferences while staying capable of using anything. Adapts to your stack.

Security Scan

An instruction-only skill whose requirements and instructions align with its stated purpose, but it is somewhat vague about how it persists or applies learned preferences.

Purpose & Capability

Name/description (learning user tool preferences and adapting) matches the content of SKILL.md, criteria.md, and dimensions.md. The skill requests no binaries, env vars, or installs—consistent with a lightweight preference-tracking assistant.

Instruction Scope

Instructions stay within the declared purpose (choose and suggest tools, consult criteria/dimensions). However they are high-level and grant broad discretion ('You can use ANY tool', 'Learn new ones instantly') without describing limits or what context may be gathered to make those decisions. The SKILL.md does not instruct reading system files, env vars, or contacting external endpoints, which is good, but its openness could let an agent perform broad web research or ask the user for context.

Install Mechanism

No install spec and no code files — nothing is written to disk or fetched at install time. Lowest-risk install footprint.

Credentials

No required environment variables, credentials, or config paths are declared. Nothing requests unrelated secrets or access.

Persistence & Privilege

always is false (normal). The SKILL.md implies the agent should 'track' and potentially 'update' preferences, but provides no mechanism for persistent storage or how updates are recorded (e.g., modifying SKILL.md, platform storage, or external DB). Clarify where preferences are stored and whether the skill will modify agent files or store data externally.

Assessment

This skill is instruction-only and coherent with its stated purpose: it suggests and adapts tool recommendations using the included guidance files. Before installing, ask the publisher how learned preferences are persisted (where and how long data is stored, whether skill will modify skills/config files or call external storage). Because the instructions are intentionally broad, consider whether you want the agent to invoke the skill autonomously (normal by default) and avoid sharing secrets in conversations — the skill may suggest tools that require credentials, but it itself does not request any. If you need stronger guarantees, ask for: (1) a description of persistence (no external storage or only platform-managed state), (2) logging/privacy policy, and (3) whether the skill ever reads or writes agent files or external endpoints.

Adaptive Tool Intelligence

You can use ANY tool. Learn new ones instantly. This skill tracks user preferences, not your limits.

Rules:

• Default to user's known tools when they exist
• Propose better alternatives when significantly better for the task
• Learn new tools on demand without friction
• Check dimensions.md for categories, criteria.md for when to suggest new

---

Stack

<!-- Tools user actively uses. Format: "category: tool" -->

Preferences

<!-- When to use what. Format: "context: tool or approach" -->

Open To

<!-- User's appetite for new tools. Format: trait -->

Avoid

<!-- Tools user rejected or dislikes -->

---

Remember: Empty stack ≠ limited. Ask or propose based on task. User preferences guide choices, not restrict capabilities.