Find agent skills by outcome

<question>Look for pull requests that modified files in the /api directory and were merged between January 1 and January 31

2024. How many different contributors worked on these PRs?</question>

- In all tool call requests

use the `limit` parameter to limit results (<10)

- Make INCREMENTAL

SMALL

- Ensure each subagent is only performing READ-ONLY

NON-DESTRUCTIVE

- Use your intuition and understanding to create reasonable

realistic

- Understand input/output schemas

docstrings

Coding & Debugging

After understanding the API and tools

USE the MCP server tools:

- Message concept: message ID

message string

- If ambiguity exists

fetch additional information from the web

- Channel concept: channel ID

channel name

Research & Learning

- Example: if finding a paper name

be SPECIFIC enough so answer is not confused with papers published later

- User concept: user ID

user name

Creative

- Questions must be designed so there is a single

clear answer

- Answers must not require special formatting or complex

structured output

- Examples: names

first name

- Timestamp

datetime

- File ID

file name

- URL

title

- Channel ID

channel name

- Message ID

string

- User ID

user name

- Examples: Use YYYY/MM/DD.

Respond True or False.

- If the answer can be re-written in many formats

clearly specify the output format in the QUESTION

- Questions may require specific output formats (datetime vs. epoch time

JSON vs. MARKDOWN)