Loading...
Loading...
Found 644 Skills
Capture architectural decisions and changes made during a GSDL project into a structured markdown document. Analyzes git history and diffs, extracts key decisions, and optionally pushes the doc to Slite or Notion as a child page. Called by the gsdl orchestrator after all implementation tasks are complete.
Use this skill when you need to parse requirement documents and requirement analysis results from Word/HTML/JSON/Markdown/Excel, then generate test cases and output them in Markdown/Word/JSON/Excel formats.
Standardize and validate SKILL.md files to match the project specification. Use when creating new skills, converting existing skills to standard format, or validating skill file structure. Handles section heading conversion, frontmatter standardization, and missing section detection.
Create a README.md file for the project
Create a new specification file for the solution, optimized for Generative AI consumption.
Detect and remove AI-generated markers from Finnish text, making it sound like a native Finnish speaker wrote it. Use when asked to "humanize", "naturalize", or "remove AI feel" from Finnish text, or when editing .md/.txt files containing Finnish content. Identifies 26 patterns (12 Finnish-specific + 14 universal) and 4 style markers.
Update an existing specification file for the solution, optimized for Generative AI consumption based on new requirements or updates to any existing code.
Generate a language translation for a mkdocs documentation stack.
Translates articles and documents between languages with three modes - quick (direct), normal (analyze then translate), and refined (analyze, translate, review, polish). Supports custom glossaries and terminology consistency via EXTEND.md. Use when user asks to "translate", "翻译", "精翻", "translate article", "translate to Chinese/English", or needs any document translation. Also triggers for "refined translation", "精细翻译", "proofread translation", or "快速翻译".
Day 1 Skill 체험용. "/day1-test-skill", "테스트 스킬" 요청에 사용.
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".
Deconstructs academic papers like an X-ray machine, extracting core contributions, critical assumptions, and napkin-worthy insights from research papers.