GitHub
add-meeting-agenda
회의록에 안건 추가. 자연어로 요청하여 GitHub Discussion 회의록에 안건을 추가합니다. Use when (1) "회의록에 안건 추가해줘", (2) "이번 주 회의에서 논의할 내용 추가", (3) "회의 안건으로 OOO 넣어줘", (4) 회의 안건...
Skills IA testing security knowledge base
Découvrez les skills testing security knowledge base, comparez leurs dépôts et consultez leurs instructions.
Catégories: testing security knowledge base
testing security knowledge base Effacer les filtres
Explorer
GitHub
semo-help
SEMO 도움말 및 Semicolon 팀 컨텍스트 응답 (공통 Skill). Use when (1) /SEMO:help 커맨드, (2) "도움말", "SEMO란", "어떻게 해" 키워드, (3) SEMO 사용법 질문.
GitHub
fetch-team-context
Fetch Semicolon team standards from docs wiki. Use when (1) providing workflow or process advice, (2) recommending DevOps strategies, (3) referencing team conventions for decision-making, (4) checking team stan...
GitHub
tid-note
Tidy and refactor Foam/Obsidian notes in this workspace, especially “整理当日笔记/整理笔记” requests. Use when extracting topics from `Daily Notes/` into subject chapter notes while preserving original content,...
GitHub
internal-linking
Plans internal link structure using content silos. Outputs link map with SEO priority. Does not create links.
GitHub
keyword-research
Keyword research for UK local service businesses. Generates silo-compatible keyword map. Binding input for heading-tree and internal-linking skills.
GitHub
llm-optimization
Optimize websites for AI assistant recommendations. ChatGPT, Gemini, Perplexity, Claude. Get cited in AI answers.
GitHub
skill-factory
Meta-skill for generating new standard skill modules. Context-aware: analyzes user requirements to select appropriate templates (Basic/Generator/Data) and automatically populates metadata (name, tags, descripti...
GitHub
strategic-thought-partner
Collaborative strategic thinking for founders, operators, and decision-makers. Use when someone needs help working through business strategy, product direction, positioning, prioritization, or major decisions....
GitHub
whitepaper-editor
Brutal technical white paper editor that performs merciless review with research-backed validation. Use when reviewing, editing, or improving white papers, technical documents, research papers, or any document...
GitHub
rag
検索増強生成（RAG）Skill。知識ベースへのドキュメント追加、意味検索、LLM 回答生成をサポート。 ドキュメント Q&A、社内知識検索、カスタム知識ベース構築に使用。
GitHub
clarificationagent
問題診断Agent - ユーザーの質問を深く診断し、論理的な穴、隠れた仮定、思考の誤りを指摘する
GitHub
querying-hms-documentation
Queries official HEC-HMS documentation to answer technical questions. Provides access to User's Manual, Technical Reference Manual, Release Notes, and community resources. Use when seeking official documentatio...
GitHub
reflect
Capture lessons from conversation after Claude made mistakes or needed correction. Trigger phrases include "reflect", "review our mistakes", "learn from this", "capture this lesson", "remember this for next tim...
GitHub
architecture
Design technical architecture from a PRD. Use when user wants to create an architecture document, define system design, plan technical implementation, or needs to translate product requirements into buildable t...
GitHub
memory-updater
Update and maintain Memory Bank files (activeContext, progress, decisionLog). Triggers: MB, memory, 記憶, 進度, 更新記憶, update memory, 記錄進度, 更新上下文.
GitHub
memory-checkpoint
Externalize detailed memory to Memory Bank before conversation summarization to prevent context loss. Triggers: CP, checkpoint, save, 存檔, 記一下, 保存, sync memory, dump, 先記著.
GitHub
tag-criteria
This skill should be used when analyzing Obsidian notes for tagging, determining which tags apply to content, or understanding tag definitions and criteria. Provides the complete tag taxonomy with judgment crit...
GitHub
zerodb-workflows
ZeroDB vector database best practices, semantic search patterns, RLHF workflows, and memory management. Use when working with ZeroDB APIs, vector search, or AI memory systems.
GitHub
bugs
Senior Logic & Correctness Reviewer for finding bugs and logical flaws.
GitHub
spine-framework
Evaluate and improve technical articles using the SPINE framework. Use when writing blog posts, technical documentation, tutorials, or reviewing draft articles for quality.
GitHub
research-first
Research-driven investigation. Validate solutions and explore documentation before presenting. Never ask questions you can answer yourself through research.
GitHub
structured-writing
Writing assistance with voice preservation. Structure content, ask clarifying questions, identify gaps. Small edits execute; large changes ask first.
GitHub
critical-peer
Professional skepticism with pattern enforcement. Verify before agreeing, challenge violations, propose instead of asking. Concise output, research before asking, answer questions literally.
Le classement utilise les étoiles du dépôt GitHub indexé. Plusieurs skills peuvent partager ce nombre : ce n’est ni un nombre d’installations ni une note de qualité.