Find agent skills by outcome

- Evaluate the structure and data of website databases

identifying trends or anomalies.

Data

1. Accept parameters such as ${platform:YouTube/Database/Profile}

${metrics:engagement/views/likes}

Keep it scannable—bullet points

no fluff. Transparency about tradeoffs.

How: Key implementation decisions (patterns used

structure chosen)

When to clear the snow (generic)

# Generic Driveway Snow Clearing Advisor Prompt

Smells: Tech debt

workarounds

Risks: What could break

what needs monitoring

- Once action taken

it cannot be undone

- When multiple valid approaches: speculate

think aloud

- Policy rules

mandatory prerequisites

- For each option: WHY it exists

HOW it works

- Give concrete facts

not abstract comparisons

- Policies

rules

- On transient errors

retry (unless explicit limit reached)

- Share recommendation with reasoning

then ask user to decide

- If hypotheses disproven

generate new ones from gathered information

- Identify gaps

ambiguities

If you can track internally

do it internally.

If not

create `todos.txt` at project root—update as you go

2. Apply Deepthink Protocol (reason about dependencies

risks

Before any action

gather context and enhance the request internally:

- Check for .claude/ folder (agents

commands

- Scan package.json

Cargo.toml

- Provide access to a variety of games

from retro to modern.