Evaluate hook security, performance, and SDK compliance. Use for audits
Publisher
Skills by athola
188 published skills, 3634 installs in total.
Applies KISS, YAGNI, and SOLID principles for clean code with reduced complexity
Configures pre-commit hooks for linting, type checking, formatting, and testing
Executes implementation plans with progress tracking, checkpoint validation, and quality gates. Use after planning is complete and tasks are ready to implement
Guide creating Claude Code hooks with security-first design. Use for validation and enforcement
Analyze and improve the improvement process. Use for detecting regressions and meta-optimization
Selects and routes to the right architecture paradigm
Guides project ideation via Socratic questioning to produce a validated brief. Use before specification when requirements are unclear
Assesses architecture decisions, ADR compliance, and coupling
Guide creating Claude Code skills with TDD and persuasion principles. Use for new skill development
Applies microservices for independent deployment and per-service scaling
Compresses verbose responses by removing filler and framing to save 200-400 tokens
Browse hookify rule catalog
Hunts bugs with evidence trails
Converts a Claude Code session into a blog post, case study, or Reddit post
Assesses decision reversibility and risk at critical checkpoints
Scores backlog items with RICE/WSJF/Kano and files GitHub issues for top candidates
Merges ephemeral report and analysis artifacts into permanent documentation
Manages Claude Code sessions with naming, checkpointing, and resume strategies
Generates or updates tutorials from VHS tapes and Playwright specs with dual-tone markdown and GIF recording
Generates or remediates documentation with human-quality writing
Orchestrates full project lifecycle by auto-detecting state and routing to the correct phase
Manages context overflow by handing off to a fresh subagent at 80% usage
Routes multi-tool workflows through MCP servers for large datasets and pipelines
Autonomous orchestrator for manifest work items through the development lifecycle
Enforces validation and evidence before claiming work complete. Use before declaring implementation done, creating a PR, or submitting deliverables for review
Reviews pull requests with scope validation, requirements compliance, and line comments
Detects AI-generated writing patterns in prose
Extracts writing style patterns from exemplar text into a reusable profile
Plans, drafts, and refines technical tutorials for developers
Applies layered n-tier architecture with enforced boundaries
Assess whether to escalate models
Build composable skill modules with hub-and-spoke loading
Delegates tasks to Gemini or Qwen with quota tracking and error handling
Applies anti-sycophancy checklist to override agreement bias
Processes external resources into stored knowledge with quality scoring and routing
Captures and retrieves PR-review findings in memory palaces. Use after PR review to store architectural decisions, patterns, and standards for future reference
Evaluates test suites for coverage gaps, TDD/BDD compliance, and anti-patterns
Updates, generates, and validates tests using git-workspace context and TDD/BDD methodology
Convenes a multi-LLM expert panel to pressure-test hard-to-reverse decisions
Coordinates Claude agent teams via filesystem protocol
Implements hub-and-spoke lazy loading to minimize token usage in large skills
Improves code quality across duplication, efficiency, and architectural fit
Prepares pull requests by running quality gates, drafting descriptions, and validating tests
Records browser sessions via Playwright and converts video to GIF
Converts webm/mp4 video files to optimized GIFs via ffmpeg with configurable quality settings
Combines GIFs and videos into composite tutorials with vertical or grid layouts via ffmpeg
Scores feature worthiness and enforces branch-size limits against overengineering
About Ottermind skills
Every published skill from athola. Following a publisher whose work already fits how you operate is often faster than evaluating individual skills one at a time.
Skills cover the full range of what an Ottermind agent does: building editable PowerPoint decks, generating product and brand images, writing and running code on a machine you connect, producing video from a script or a still, and cleaning and analysing spreadsheet data. A skill is what turns a general model into something that handles your specific version of one of those jobs the same way every time.
A skill is a plain Markdown file with a short frontmatter header, which means you can read exactly what it will do before running it, edit it to match your own conventions, and share it with colleagues. Once a skill produces the result you wanted, it can be attached to an agent or scheduled as an automation so the same work happens again without anyone rewriting the prompt.
- What is an Ottermind skill?
- A reusable instruction package written in Markdown. It gives an agent the context, steps, and constraints for one kind of task, so results stay consistent instead of depending on how well you phrased the prompt that day.
- How do I install and use a skill?
- Open any skill's detail page, read the full document, and install it into your workspace. From then on the agent can use it automatically when the task matches, or you can invoke it by name.
- Can I create my own skill?
- Yes. A skill is a Markdown file with frontmatter naming it and describing when it should be used. If you have a workflow you keep re-explaining to an agent, writing it down once as a skill is usually the shortest path to making it repeatable.
- Do skills cost extra?
- Browsing and installing skills from this library does not cost anything on its own. Running one consumes the same credits as any other agent task, depending on the model you choose and how much work the task involves.