Loading...
Loading...
Found 4,654 Skills
Get Shit Done (GSD) orchestrator. Runs the full project pipeline from idea to implementation to documentation: setup → PRD → task list → implementation → decisions doc. Use when the user wants to build something end-to-end, says "let's GSD", "build this from scratch", "get shit done", or wants to run the full development workflow. Coordinates gsdl-setup-project, gsdl-create-prd, gsdl-create-plan, gsdl-execute-plan, and gsdl-document-decisions skills. Spawns subagents per parent task during implementation to preserve context. Accepts an optional project name or source URL: /gsdl [project-name] OR /gsdl [linear|notion|slite] [url] OR /gsdl [url].
Trigger: Call this skill when the problem is complex, has multiple conflicting factors, unclear priorities, or you don't know what to solve first; common signals include trade-off, bottleneck, unknown root cause, unclear priority order, and mutual restraint between multiple problems. Trigger when a problem contains competing forces, unclear priorities, or no obvious entry point. Use this skill to identify contradictions, isolate the principal contradiction, classify its nature, and choose the right response.
Synchronize the base44-cli skill with the latest CLI source code from the Base44 CLI repository
Investigate incidents, debug performance issues, analyze logs, and manage observability resources in Dynatrace using the dtctl CLI. Use this skill whenever the user asks about error rates, latency spikes, service health, crash-looping pods, web vitals, SLO status, open problems, root cause analysis, log patterns, trace analysis, or building dashboards — even if they don't mention Dynatrace by name. Also covers DQL queries, workflow management, notebook and dashboard creation, settings configuration, and any operations against a Dynatrace environment.
Apply when working with MasterData v2 entities, schemas, or MasterDataClient in VTEX IO apps, or when anyone designing or implementing a solution must scrutinize whether Master Data is the correct storage. The skill prompts hard questions: native Catalog or other VTEX stores, OMS, or an external database may be better; do not default to MD because it is convenient. Covers JSON Schema, CRUD, triggers, search and scroll, schema lifecycle, purchase-path avoidance, single source of truth, and BFF handoffs. Use for justified custom persistence while avoiding the 60-schema limit.
Ingest any raw text data, conversation logs, chat exports, or unstructured documents into the Obsidian wiki. Use this skill when the user wants to process data that isn't standard documents or Claude history — things like ChatGPT exports, Slack threads, Discord logs, meeting transcripts, journal entries, CSV data, browser bookmarks, email archives, or any raw text dump. Triggers on "ingest this data", "process these logs", "add this export to the wiki", "import my chat history from X". This is the catch-all for any text source not covered by the more specific ingest skills.
Set up or update the agent-first engineering harness for any repository. Implements the complete scaffolding that makes AI coding agents effective: knowledge maps (AGENTS.md as a concise TOC), structured documentation, architecture boundaries, enforcement rules (.harness/*.yml specs), quality scoring, and process patterns for agent-driven development. Use this skill whenever someone wants to make a repo agent-ready, set up AGENTS.md or docs/ structure, define domain boundaries or golden principles, generate .harness/ configuration, audit agent readiness, or update an existing harness. Also trigger when a user reports problems with agent effectiveness, context management, or architectural drift — these are symptoms of a missing or stale harness. Trigger on: "harness this repo", "set up harness", "agent-first setup", "make this agent-ready", "update the harness", "assess agent readiness", "set up AGENTS.md", "organize for agents", or any discussion about structuring a codebase for AI agent workflows.
Apply Lean and Six Sigma principles to eliminate waste and reduce process variation. Use this skill when the user needs to improve operational efficiency, identify the seven wastes (TIMWOOD), run DMAIC improvement projects, or streamline workflows — even if they say 'our process is too slow', 'where are we wasting resources', or 'how do we reduce defects'.
Apply pragmatist philosophy (Peirce, James, Dewey) to frame knowledge as instrumental for action, evaluate ideas by their practical consequences, and conduct inquiry as problem-solving. Use this skill when the user needs to bridge theory and practice, evaluate competing theories by their usefulness, employ abductive reasoning to generate hypotheses, or when they ask 'which theory is more useful here', 'how do I move from abstract ideas to actionable knowledge', or 'what practical difference does this distinction make'.
Guides EVM Solidity DeFi triage from public verified source or bytecode—access control, proxies, oracle usage, reentrancy and CEI patterns, DEX/router integrations, and common vulnerability classes. Use when the user asks for Ethereum or L2 smart contract security review, Solidity audit triage, OpenZeppelin proxy risks, or EVM-specific DeFi patterns—not for live exploits or private keys.
Read and parse RSS/Atom feeds. Use when: user wants to subscribe to feeds, get latest articles, or monitor news sources.
MCP (Model Context Protocol) - Build AI-native servers with tools, resources, and prompts. TypeScript/Python SDKs for Claude Desktop integration.