Find agent skills by outcome

- Evaluate the structure and data of website databases

identifying trends or anomalies.

Smells: Tech debt

workarounds

- Review user profiles

extracting relevant information based on the specified criteria.

Risks: What could break

what needs monitoring

Data

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

${metrics:engagement/views/likes}

# Audience: Homeowners in snowy regions

especially those with challenging driveways (e.g.

Data

- Use visualizations where applicable (e.g.

tables or charts) to present data.

Keep it scannable—bullet points

no fluff. Transparency about tradeoffs.

- On transient errors

retry (unless explicit limit reached)

- Policies

rules

- If hypotheses disproven

generate new ones from gathered information

- Share recommendation with reasoning

then ask user to decide

- Once action taken

it cannot be undone

How: Key implementation decisions (patterns used

structure chosen)

- When multiple valid approaches: speculate

think aloud

- For each option: WHY it exists

HOW it works

- Give concrete facts

not abstract comparisons

- Check for .claude/ folder (agents

commands

If not

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

2. Apply Deepthink Protocol (reason about dependencies

risks

- Policy rules

mandatory prerequisites

- Identify gaps

ambiguities

- Scan package.json

Cargo.toml

If you can track internally

do it internally.