GitHub
architecture-documenter
Maintain and update architecture documentation in docs/architecture/. Uses tool-based inspection first, falling back to CLI only when needed.
☆ 0View skill
timbuchinger AI Skills
GitHub ↗Browse published AI skills maintained by timbuchinger. Compare skill descriptions and follow each source repository for setup instructions.
Author statistics
Indexed skills
24Repository stars across indexed skills
0Repository forks
0Average repository stars per indexed skill
0Repository stars may repeat across skills from the same repository.
Popular categories
Recent indexing activity
Browse skills
GitHub
user-story
Creates well-structured user stories for software development and project management. Use when the user asks to write, create, or format a user story, or needs to document requirements, features, or tasks in us...
☆ 0View skill
GitHub
executing-plans
Use when given a complete implementation plan to execute in controlled batches with review checkpoints - loads plan, reviews critically, executes tasks in batches, reports for review between batches
☆ 0View skill
GitHub
webapp-testing
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
☆ 0View skill
GitHub
tempo-troubleshoot
Help craft efficient Tempo trace queries, troubleshoot distributed traces, link logs and metrics (Loki/Mimir), and perform request-level root cause analysis.
☆ 0View skill
GitHub
playwright-testing
Complete browser automation with Playwright. Auto-detects dev servers, writes clean test scripts to /tmp. Test pages, fill forms, take screenshots, check responsive design, validate UX, test login flows, check...
☆ 0View skill
GitHub
loki-troubleshoot
Help craft efficient Grafana Loki / LogQL queries for debugging logs — with label‑based filtering, narrow time windows, and best‑practice guidance to avoid expensive or overly broad scans.
☆ 0View skill
GitHub
code-review
Use when the user asks to review code or a pull request - performs focused review checking for obvious defects only, provides minimal feedback with clear approval/rejection format
☆ 0View skill
GitHub
search-notes
Always use this skill at the start of a task to check whether relevant information already exists. Use when users ask to recall, search memories, or subscribe to updates. Triggers on "recall", "search memories"...
☆ 0View skill
GitHub
writing-skills
Use when creating new skills, editing existing skills, or verifying skills work before deployment - applies TDD to process documentation by testing with subagents before writing, iterating until bulletproof aga...
☆ 0View skill
GitHub
add-note
Use this skill whenever important information is learned during a task or when the user explicitly asks to store something. Use when users ask to remember. Triggers on "remember this", "update memory", "share"...
☆ 0View skill
GitHub
brainstorming
Use when creating or developing, before writing code or implementation plans - refines rough ideas into fully-formed designs through collaborative questioning, alternative exploration, and incremental validatio...
☆ 0View skill
GitHub
azure-troubleshoot
Troubleshoot Azure using tool-first access, falling back to Azure CLI when necessary. Focus on Virtual Machines, AKS, Azure Container Registry, Storage Accounts, and Log Analytics.
☆ 0View skill
GitHub
repo-documenter
Provide repository-wide documentation guidelines under `docs/`. Use tool-based inspection first, and keep `README.md` and `docs/` in sync with the current state of the app.
☆ 0View skill
GitHub
bash-defensive-patterns
Use when writing or reviewing Bash scripts to apply defensive programming patterns including strict mode, proper error handling, safe variable handling, argument parsing, and idempotent design. Ensures scripts...
☆ 0View skill
GitHub
gcp-troubleshoot
Troubleshoot GCP services using tool-first access (via MCP when available), falling back to the CLI only when necessary. Focus on Firestore, Cloud Run, networking, load balancers, IAM, Pub/Sub, Cloud SQL, and S...
☆ 0View skill
GitHub
kubernetes-troubleshoot
Troubleshoot and manage Kubernetes clusters, including resource inspection, debugging, pod logs, events, and cluster operations. Use when the user needs to diagnose issues, inspect workloads, analyze pod failur...
☆ 0View skill
GitHub
writing-plans
Use when design is complete and you need detailed implementation tasks - creates comprehensive implementation plans with exact file paths, complete code examples, and verification steps assuming minimal codebas...
☆ 0View skill
GitHub
aws-troubleshoot
Troubleshoot AWS services using tool-first access (via MCP when available), falling back to AWS CLI when necessary. Focus on EKS, S3, ECR, EC2, SSM, networking, site-to-site VPNs, IAM Identity Center, and IAM.
☆ 0View skill
GitHub
mimir-prometheus-troubleshoot
Help craft efficient Mimir/Prometheus queries, troubleshoot metric issues, avoid high-cardinality problems, and recommend best practices for aggregation, recording rules, and performance.
☆ 0View skill
GitHub
create-pull-request
Use when the user asks to create a pull request or PR for their work - creates PR using available tools with clear, concise title and description following standard template
☆ 0View skill
GitHub
bats-testing-patterns
Comprehensive guide for writing shell script tests using Bats (Bash Automated Testing System). Use when writing or improving tests for Bash/shell scripts, creating test fixtures, mocking commands, or setting up...
☆ 0View skill
GitHub
test-driven-development
Use when implementing any feature or bugfix, before writing implementation code - write the test first, watch it fail, write minimal code to pass; ensures tests actually verify behavior by requiring failure fir...
☆ 0View skill
GitHub
gemini-cli
Use Gemini CLI for analyzing large codebases or multiple files that exceed context limits. Leverage Google Gemini's massive context window with `gemini -p` and `@` syntax for file/directory inclusion to verify...
☆ 0View skill
The default order uses GitHub repository stars from our indexed data. Stars belong to the source repository and may be shared by multiple skills. They indicate repository interest, not skill installs or an independent quality score.