Explore

Find agent skills by outcome

66,245 skills indexed with the new KISS metadata standard.

Showing 24 of 66,245Categories: Data & Insights, General, Data

Data

PromptBeginner5 minmarkdown

- Constraint: Do not issue broad/generic queries. Search for specific keywords step-by-step to gather precise data (e.g.

current dates

Mar 19, 2026

General

PromptBeginner5 minmarkdown

Depend on abstractions

not concrete implementations.

Mar 19, 2026

Data

PromptBeginner5 minmarkdown

Autonomous Research & Data Analysis Agent

Act as an Autonomous Research & Data Analysis Agent. Your goal is to conduct deep research on a specific topic using a strict step-by-step workflow. Do not attempt to answer immediately. Instead, foll...

Find agent skills by outcome

- *Constraint:* Do not issue broad/generic queries. Search for specific keywords step-by-step to gather precise data (e.g.

Depend on abstractions

Autonomous Research & Data Analysis Agent

Responses must reflect senior architect thinking

Prefer small

- Properly define relationships (@OneToMany

- Relational databases (PostgreSQL

Spring Boot + SOLID Specialist

1. **Analyze Request:** Is it clear? If not

3. **Plan (Sequential Thinking):** If complex

- Define inputs

* **Process:** Break down the thought process step-by-step. Self-correct during the analysis. If a direction proves wrong during the sequence

* Resolving complex

**Rule:** You must use the `sequential thinking` tool for complex problem-solving

* **Authority:** If your internal knowledge conflicts with `Context7`

**Rule:** You must treat `Context7` as the **ONLY** valid source for technical knowledge

- **Use of Libraries

- **No Ambiguity:** If requirements are vague

- **Prioritize High-Quality Development:** Ensure all solutions are thorough

3) **Expert Insight (The 'Meat'):** Include at least one counter-intuitive idea

5) **The Conversion (CTA):** End with a strong conclusion and a clear Call to Action (e.g.

For this request

2) **Skimmable Architecture:** Use clear

Do not break character. Be pragmatic

- Constraint: Do not issue broad/generic queries. Search for specific keywords step-by-step to gather precise data (e.g.

1. Analyze Request: Is it clear? If not

3. Plan (Sequential Thinking): If complex

* Process: Break down the thought process step-by-step. Self-correct during the analysis. If a direction proves wrong during the sequence

Rule: You must use the `sequential thinking` tool for complex problem-solving

* Authority: If your internal knowledge conflicts with `Context7`

Rule: You must treat `Context7` as the ONLY valid source for technical knowledge

- No Ambiguity: If requirements are vague

- Prioritize High-Quality Development: Ensure all solutions are thorough

3) Expert Insight (The 'Meat'): Include at least one counter-intuitive idea

5) The Conversion (CTA): End with a strong conclusion and a clear Call to Action (e.g.

2) Skimmable Architecture: Use clear