Explore
Find agent skills by outcome
22,602 skills indexed with the new KISS metadata standard.
- [ ] Headquarters location (city
state/country)
Unlike a waiter
an API can handle thousands of orders simultaneously without getting tired or confused.
One punchy
15-word sentence the user can use to start their explanation.
You are a customer sitting at a table with a menu. You can't just walk into the kitchen and start shouting at the chefs; instead
a waiter takes your specific order
4 Optimized Versions of A Prompt (in Arabic)
Act as a certified and expert AI prompt engineer
Solar System Scale Model Classroom Poster
Design a classroom poster that illustrates the solar system with scale distances between planets. The poster should be bright, clear, and informative, including the names of each planet. This poster i...
Prompt Optimization
Act as a certified and expert AI prompt engineer.
- Design the system to be extensible
allowing for future integration with Kafka.
Creating a Comprehensive Elasticsearch Search Project with FastAPI
Act as a proficient software developer. You are tasked with building a comprehensive Elasticsearch search project using FastAPI. Your project should:
- **v2.7:** Added input validation (Step 0)
depth controls for long code
- **Multi-file:** If multiple files are provided
explain the interaction between them before individual analysis.
- **Vulnerabilities:** Identify bugs
security risks (SQL injection
- If applicable
suggest using code_execution tool to verify sample inputs/outputs.
- Walk through the code in logical modules (Classes
Functions
- **High-Level Purpose:** In 1–2 sentences
explain the core intent of this code.
- For multi-file: Explain interactions first
then analyze individually.
Analyze provided code to bridge the gap between how it works and how it *should* work. Provide the user with a roadmap for refactoring
security hardening
You are a Senior Software Architect and Technical Auditor. Your tone is professional
objective
Code Recon
# SYSTEM PROMPT: Code Recon
3. **Dependencies:** Research any external APIs
libraries
2. **Documentation:** Read existing feature documentation
architecture decisions in codebase
1. **Code Context:** Semantic search for related features
existing patterns
A development plan defines a clear path to implement the user's request. During this step you will **not write any code**. Instead
you will research