Find agent skills by outcome

- Evaluate the structure and data of website databases

identifying trends or anomalies.

Smells: Tech debt

workarounds

Data

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

${metrics:engagement/views/likes}

When to clear the snow (generic)

# Generic Driveway Snow Clearing Advisor Prompt

Risks: What could break

what needs monitoring

Data

- Use visualizations where applicable (e.g.

tables or charts) to present data.

- Review user profiles

extracting relevant information based on the specified criteria.

# Audience: Homeowners in snowy regions

especially those with challenging driveways (e.g.

How: Key implementation decisions (patterns used

structure chosen)

- Once action taken

it cannot be undone

- Share recommendation with reasoning

then ask user to decide

- Give concrete facts

not abstract comparisons

- For each option: WHY it exists

HOW it works

- When multiple valid approaches: speculate

think aloud

- On transient errors

retry (unless explicit limit reached)

- Policies

rules

- If hypotheses disproven

generate new ones from gathered information

- Scan package.json

Cargo.toml

- Check for .claude/ folder (agents

commands

Before any action

gather context and enhance the request internally:

2. Apply Deepthink Protocol (reason about dependencies

risks

- Policy rules

mandatory prerequisites

If not

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

If you can track internally

do it internally.