feat: add explain-like-socrates skill (#270)
Co-authored-by: Tejas Shinde <tejasashinde@users.noreply.github.com>
This commit is contained in:
@@ -2,7 +2,7 @@
|
||||
|
||||
Generated at: 2026-02-08T00:00:00.000Z
|
||||
|
||||
Total skills: 1245
|
||||
Total skills: 1246
|
||||
|
||||
## architecture (80)
|
||||
|
||||
@@ -600,7 +600,7 @@ no matching field, parse error, widget... | makepad, reference | makepad, refere
|
||||
| `zod-validation-expert` | Expert in Zod — TypeScript-first schema validation. Covers parsing, custom errors, refinements, type inference, and integration with React Hook Form, Next.js... | zod, validation | zod, validation, typescript, first, schema, covers, parsing, custom, errors, refinements, type, inference |
|
||||
| `zustand-store-ts` | Create Zustand stores with TypeScript, subscribeWithSelector middleware, and proper state/action separation. Use when building React state management, creati... | zustand, store, ts | zustand, store, ts, stores, typescript, subscribewithselector, middleware, proper, state, action, separation, building |
|
||||
|
||||
## general (294)
|
||||
## general (295)
|
||||
|
||||
| Skill | Description | Tags | Triggers |
|
||||
| --- | --- | --- | --- |
|
||||
@@ -695,6 +695,7 @@ no matching field, parse error, widget... | makepad, reference | makepad, refere
|
||||
evolve, evolution, contribute, contribution, self-improve, self-improvement,
|
||||
a... | evolution | evolution, critical, makepad, skills, self, contribution, triggers, evolve, contribute, improve, improvement, add |
|
||||
| `executing-plans` | Use when you have a written implementation plan to execute in a separate session with review checkpoints | executing, plans | executing, plans, written, plan, execute, separate, session, review, checkpoints |
|
||||
| `explain-like-socrates` | Explains concepts using Socratic-style dialogue. Use when the user asks to explain, teach or help understand a concept like socrates. | explain, like, socrates | explain, like, socrates, explains, concepts, socratic, style, dialogue, user, asks, teach, understand |
|
||||
| `expo-dev-client` | Build and distribute Expo development clients locally or via TestFlight | expo, dev, client | expo, dev, client, distribute, development, clients, locally, via, testflight |
|
||||
| `expo-ui-jetpack-compose` | expo-ui-jetpack-compose | expo, ui, jetpack, compose | expo, ui, jetpack, compose |
|
||||
| `expo-ui-swift-ui` | expo-ui-swift-ui | expo, ui, swift | expo, ui, swift |
|
||||
|
||||
12
README.md
12
README.md
@@ -1,7 +1,7 @@
|
||||
<!-- registry-sync: version=7.4.1; skills=1245; stars=23187; updated_at=2026-03-11T15:02:47+00:00 -->
|
||||
# 🌌 Antigravity Awesome Skills: 1,245+ Agentic Skills for Claude Code, Gemini CLI, Cursor, Copilot & More
|
||||
<!-- registry-sync: version=7.4.1; skills=1246; stars=23187; updated_at=2026-03-11T15:03:00+00:00 -->
|
||||
# 🌌 Antigravity Awesome Skills: 1,246+ Agentic Skills for Claude Code, Gemini CLI, Cursor, Copilot & More
|
||||
|
||||
> **The Ultimate Collection of 1,245+ Universal Agentic Skills for AI Coding Assistants — Claude Code, Gemini CLI, Codex CLI, Antigravity IDE, GitHub Copilot, Cursor, OpenCode, AdaL**
|
||||
> **The Ultimate Collection of 1,246+ Universal Agentic Skills for AI Coding Assistants — Claude Code, Gemini CLI, Codex CLI, Antigravity IDE, GitHub Copilot, Cursor, OpenCode, AdaL**
|
||||
|
||||
[](https://github.com/sickn33/antigravity-awesome-skills/stargazers)
|
||||
[](LICENSE)
|
||||
@@ -18,7 +18,7 @@
|
||||
[](apps/web-app)
|
||||
[](https://buymeacoffee.com/sickn33)
|
||||
|
||||
**Antigravity Awesome Skills** is a curated, battle-tested library of **1,245+ high-performance agentic skills** designed to work seamlessly across the major AI coding assistants.
|
||||
**Antigravity Awesome Skills** is a curated, battle-tested library of **1,246+ high-performance agentic skills** designed to work seamlessly across the major AI coding assistants.
|
||||
|
||||
**Welcome to the V7.4.0 Release!** This repository gives your agent reusable playbooks for planning, coding, debugging, testing, security review, infrastructure work, product thinking, and much more.
|
||||
|
||||
@@ -32,7 +32,7 @@
|
||||
- [🎁 Curated Collections (Bundles)](#curated-collections)
|
||||
- [🧭 Antigravity Workflows](#antigravity-workflows)
|
||||
- [📦 Features & Categories](#features--categories)
|
||||
- [📚 Browse 1,245+ Skills](#browse-1245-skills)
|
||||
- [📚 Browse 1,246+ Skills](#browse-1246-skills)
|
||||
- [🤝 How to Contribute](#how-to-contribute)
|
||||
- [💬 Community](#community)
|
||||
- [☕ Support the Project](#support-the-project)
|
||||
@@ -282,7 +282,7 @@ The repository is organized into specialized domains to transform your AI into a
|
||||
|
||||
Counts change as new skills are added. For the current full registry, see [CATALOG.md](CATALOG.md).
|
||||
|
||||
## Browse 1,245+ Skills
|
||||
## Browse 1,246+ Skills
|
||||
|
||||
- Open the interactive browser in [`apps/web-app`](apps/web-app).
|
||||
- Read the full catalog in [`CATALOG.md`](CATALOG.md).
|
||||
|
||||
Binary file not shown.
|
Before Width: | Height: | Size: 52 KiB After Width: | Height: | Size: 52 KiB |
@@ -1,6 +1,6 @@
|
||||
{
|
||||
"generatedAt": "2026-02-08T00:00:00.000Z",
|
||||
"total": 1245,
|
||||
"total": 1246,
|
||||
"skills": [
|
||||
{
|
||||
"id": "00-andruia-consultant",
|
||||
@@ -12108,6 +12108,32 @@
|
||||
],
|
||||
"path": "skills/executing-plans/SKILL.md"
|
||||
},
|
||||
{
|
||||
"id": "explain-like-socrates",
|
||||
"name": "explain-like-socrates",
|
||||
"description": "Explains concepts using Socratic-style dialogue. Use when the user asks to explain, teach or help understand a concept like socrates.",
|
||||
"category": "general",
|
||||
"tags": [
|
||||
"explain",
|
||||
"like",
|
||||
"socrates"
|
||||
],
|
||||
"triggers": [
|
||||
"explain",
|
||||
"like",
|
||||
"socrates",
|
||||
"explains",
|
||||
"concepts",
|
||||
"socratic",
|
||||
"style",
|
||||
"dialogue",
|
||||
"user",
|
||||
"asks",
|
||||
"teach",
|
||||
"understand"
|
||||
],
|
||||
"path": "skills/explain-like-socrates/SKILL.md"
|
||||
},
|
||||
{
|
||||
"id": "expo-api-routes",
|
||||
"name": "expo-api-routes",
|
||||
|
||||
161
skills/explain-like-socrates/SKILL.md
Normal file
161
skills/explain-like-socrates/SKILL.md
Normal file
@@ -0,0 +1,161 @@
|
||||
---
|
||||
name: explain-like-socrates
|
||||
description: >
|
||||
Explains concepts using Socratic-style dialogue. Use when the user asks to explain, teach or help understand a concept like socrates.
|
||||
risk: safe
|
||||
source: original
|
||||
date_added: "2026-03-11"
|
||||
---
|
||||
|
||||
# EXPLAIN LIKE SOCRATES
|
||||
|
||||
Explains ideas using the conversational reasoning style of Socratic dialogue. Instead of delivering lectures, the assistant guides the user toward understanding through reflective reasoning, small thought experiments, and a single simple analogy. The goal is not to deliver information quickly, but to help the user **arrive at clarity through thought.**
|
||||
|
||||
DO:
|
||||
- reason conversationally
|
||||
- build the idea step-by-step
|
||||
- ask reflective questions occasionally
|
||||
- guide the user's thinking
|
||||
|
||||
DO NOT:
|
||||
- present textbook explanations
|
||||
- dump large factual lists
|
||||
- overwhelm the user with terminology
|
||||
- sound like documentation
|
||||
|
||||
Avoid traditional lecture-style teaching and use style of Socrates, the original street philosopher from ancient Athens.
|
||||
|
||||
---
|
||||
|
||||
## WHEN TO USE
|
||||
|
||||
Use this skill when the user asks to:
|
||||
- explain a concept
|
||||
- teach how something works
|
||||
- help understand a technical idea
|
||||
- clarify a theory or system
|
||||
- explore a philosophical or abstract idea
|
||||
|
||||
Do NOT Use this skill when the user asks for:
|
||||
- quick definitions and troubleshooting
|
||||
- installation instructions
|
||||
- configuration commands
|
||||
- short factual lookup
|
||||
|
||||
---
|
||||
|
||||
# RESPONSE STRUCTURE
|
||||
|
||||
Responses should loosely follow this pattern. DO NOT output headings
|
||||
|
||||
## 1. Curiosity Opening
|
||||
|
||||
Begin each explanation in the voice of Socrates: By questioning assumptions, offering analogies or professing ignorance—to initiate a dialogue that invites reflection and seeks deeper understanding.
|
||||
|
||||
---
|
||||
|
||||
## 2. Guided Reasoning
|
||||
|
||||
Introduce the idea through reasoning rather than facts.
|
||||
|
||||
Build the concept gradually through:
|
||||
- small observations
|
||||
- simple thought experiments
|
||||
- reflective questions
|
||||
|
||||
Example pattern:
|
||||
"Suppose a system needed to remember something from a previous step. What benefit might that give us?"
|
||||
|
||||
---
|
||||
|
||||
## 3. Single Analogy
|
||||
|
||||
Introduce **one simple analogy** to illuminate the concept.
|
||||
|
||||
Rules:
|
||||
- use only one analogy per explanation
|
||||
- keep the analogy consistent
|
||||
- do not introduce additional metaphors
|
||||
|
||||
Example analogy:
|
||||
|
||||
A **vending machine dispensing snacks**.
|
||||
|
||||
Example use:
|
||||
"Imagine a vending machine remembering the last button pressed.
|
||||
Would that change how it behaves next time?"
|
||||
|
||||
---
|
||||
|
||||
## 4. Clarification
|
||||
|
||||
Gradually refine the idea.
|
||||
- connect reasoning steps
|
||||
- gently correct misconceptions
|
||||
- reinforce the emerging mental model
|
||||
Keep explanations concise and conversational.
|
||||
|
||||
---
|
||||
|
||||
## 5. Reflection
|
||||
|
||||
End with a reflective prompt.
|
||||
Examples:
|
||||
- "Does the idea appear clearer now?"
|
||||
- "What picture forms in your mind now?"
|
||||
- **"What clearer picture emerges now?"**
|
||||
|
||||
Encourage user to ask more if needed.
|
||||
|
||||
---
|
||||
|
||||
# RESPONSE LENGTH GUIDANCE
|
||||
|
||||
Responses should remain concise and conversational.
|
||||
Preferred format:
|
||||
- 4–8 short paragraphs
|
||||
- minimal or no jargon unless required
|
||||
- short reflective questions with reasoning
|
||||
|
||||
Avoid long philosophical monologues.
|
||||
|
||||
---
|
||||
|
||||
# MISCONCEPTION HANDLING
|
||||
|
||||
If the user expresses an incorrect belief:
|
||||
1. acknowledge their reasoning
|
||||
2. gently challenge the assumption
|
||||
3. guide toward a clearer interpretation
|
||||
|
||||
Example: "That is an interesting way to see it. But consider this…"
|
||||
|
||||
---
|
||||
|
||||
# TONE
|
||||
|
||||
Maintain a conversational tone just like Socrates that is reflective, curious, patient. Response should feel like **thinking through an idea together**, not delivering a lecture.
|
||||
|
||||
---
|
||||
|
||||
# FAILURE HANDLING
|
||||
|
||||
If the user insists on a direct answer: Provide the explanation but still frame it through reasoning.
|
||||
Example: "Let us think through it step by step."
|
||||
If the user remains confused: Return to the analogy and simplify the reasoning.
|
||||
|
||||
---
|
||||
|
||||
# TERMINATION
|
||||
|
||||
Conclude the explanation when:
|
||||
- the concept has been explored through reasoning
|
||||
- the user expresses understanding
|
||||
- the explanation naturally reaches clarity
|
||||
|
||||
Optionally invite reflection with a prompt such as:
|
||||
- "Does that interpretation make sense to you?"
|
||||
- "How does that idea appear to you now?"
|
||||
- "Does the picture feel clearer?"
|
||||
|
||||
Questions should appear naturally during reasoning, not as a mandatory closing statement.
|
||||
@@ -4939,6 +4939,16 @@
|
||||
"source": "community",
|
||||
"date_added": "2026-02-27"
|
||||
},
|
||||
{
|
||||
"id": "explain-like-socrates",
|
||||
"path": "skills/explain-like-socrates",
|
||||
"category": "uncategorized",
|
||||
"name": "explain-like-socrates",
|
||||
"description": "Explains concepts using Socratic-style dialogue. Use when the user asks to explain, teach or help understand a concept like socrates.\n",
|
||||
"risk": "safe",
|
||||
"source": "original",
|
||||
"date_added": "2026-03-11"
|
||||
},
|
||||
{
|
||||
"id": "expo-api-routes",
|
||||
"path": "skills/expo-api-routes",
|
||||
|
||||
Reference in New Issue
Block a user