Loading...
Loading...
Found 3 Skills
Generate or improve a company-specific data analysis skill by extracting tribal knowledge from analysts. BOOTSTRAP MODE - Triggers: "Create a data context skill", "Set up data analysis for our warehouse", "Help me create a skill for our database", "Generate a data skill for [company]" → Discovers schemas, asks key questions, generates initial skill with reference files ITERATION MODE - Triggers: "Add context about [domain]", "The skill needs more info about [topic]", "Update the data skill with [metrics/tables/terminology]", "Improve the [domain] reference" → Loads existing skill, asks targeted questions, appends/updates reference files Use when data analysts want Claude to understand their company's specific data warehouse, terminology, metrics definitions, and common query patterns.
Coordinate PR mining to extract tribal knowledge and coding standards from GitHub PR history. Use when mining review comments, extracting coding rules, tracking mining jobs, or analyzing reviewer patterns across repositories. Use for "mine PRs", "extract standards", "coding rules from reviews", or "reviewer patterns". Do NOT use for code review, linting, static analysis, or writing new coding standards from scratch without PR data.
Search and maintain ~/tk, a personal knowledge base of hard-won understanding reused across sessions, such as tool behavior and pitfalls, how repos and services in a workspace connect, and environment facts. Use before working with a tool, repo, or service, when hitting an unexpected error, or when cross-service context is needed. Also use right after figuring out something non-obvious, after a wrong assumption gets corrected, when the user explains how an internal system works, and before the final answer to vote and record.