Loading...
Loading...
Found 2,058 Skills
Translate "The Interactive Book of Prompting" chapters and UI strings to a new language
길드 운영 인사이트를 구조화된 문서로 축적하여 조직 지식을 복리로 성장시킨다
Use when asked to create a code walkthrough, explain how code works linearly, generate a walkthrough for a PR or codebase, or when user says /walkthrough. Triggers on "walkthrough", "explain the code", "how does this work", "walk me through".
Binance Fiat request using the Binance API. Authentication requires API key and secret key.
Create release notes that summarize features, fixes, and migration guidance for software releases.
Use when designing new system architecture, reviewing existing designs, or making architectural decisions. Invoke for system design, architecture review, design patterns, ADRs, scalability planning.
Guide for creating effective skills for Apollo GraphQL and GraphQL development. Use this skill when: (1) users want to create a new skill, (2) users want to update an existing skill, (3) users ask about skill structure or best practices, (4) users need help writing SKILL.md files.
Interactive feature development workflow from idea to implementation. Creates requirements (EARS format), design documents, and task lists. Triggers: "kiro", ".kiro/specs/", "feature spec", "需求文档", "设计文档", "实现计划".
This skill should be used when the user asks to "create a PRD for Replit", "write product requirements", "document app specifications", "prepare a product spec", or needs a comprehensive specification document that Replit Agent can use for complex, multi-feature applications. Creates structured PRDs optimized for AI-powered development.
Use when user asks to search the web, look something up online, find current/recent/latest information, or needs cited answers. Triggers on "search", "look up", "find out about", "what is the current/latest", image searches, news lookups. NOT for searching code/files—only for web/internet searches.
Assess and classify legal risks using a severity-by-likelihood framework with escalation criteria. Use when evaluating contract risk, assessing deal exposure, classifying issues by severity, or determining whether a matter needs senior counsel or outside legal review.
Test features before users find bugs. Use when feature is built, before deploying, or when bugs reported. Covers manual testing, edge cases, cross-browser testing, and testing checklists for non-technical founders.