Persistent markdown planning files keep multi-step agent work organized and recoverable across context loss and /clear.
Publisher
Skills by othmanadi
12 published skills, 884 installs in total.
Gives AI coding agents temporal awareness via a hook-backed ledger and decision rules. Activates whenever an agent reasons about recency, retry windows, memory staleness, deploy cooldowns, idle detection, or any "when / how long ago" question. Required for autonomous or long-running agents.
Debug LangChain and LangGraph agents by fetching execution traces from LangSmith Studio. Use when debugging agent behavior, investigating errors, analyzing tool calls, checking memory operations, or examining agent performance. Automatically fetches recent traces and analyzes execution patterns. Requires langsmith-fetch CLI installed.
A live visual Kanban board and continuity layer for long-running agentic tasks. Nobody wants to read a markdown plan or stare at raw HTML while an agent grinds for an hour, so Plandeck turns the plan into a board that organizes itself. Use it when a task is multi-step, long-running, or needs visual planning. Break the work into cards, declare which card depends on which, and Plandeck computes the critical path, auto-promotes cards to Ready as their dependencies clear, rolls up story-point estimates into an honest percent complete, and names the one next action. Plans, observed transitions, and last-known-good snapshots stay as plain files on disk, so they survive /clear and context resets. After a reset, run plandeck next to recover the single next move and its recent history. If the plan stops parsing, run plandeck doctor before using git. Renders a live board in the browser over SSE. Triggers on plan a project, break down a task, kanban board, task board, visual plan, long-running ag
Build generative UI with OpenUI — any LLM provider, any backend language. Scaffold, integrate, validate.
The barber for your coding agents' config. Weighs everything every agent on this machine loads (instruction files, memory, MCP servers, hooks, skills, commands, subagents, plugins, leftovers), prices each item in tokens from your own transcripts, and parks the dead weight with a receipt and an undo. Use this skill whenever the user mentions config bloat, a heavy or slow session start, tokens burned before the first word, too many MCP servers, hooks that are slow or fire on every prompt, skills or commands or plugins nobody invokes, cleaning up or auditing CLAUDE.md or AGENTS.md, Codex config, or asks what does my agent actually load, why is my context full before I type, which of these servers can I turn off, or what is this plugin costing me. Use it even when they only say the session feels bloated or startup got slow, and even when they mention /context, /doctor or /skill-doctor.
Connect and operate the Loophole Bridge (Ableton Live MCP server). Use when the user wants to check Live/bridge prerequisites, wire an MCP client to Loophole, or run a Live editing recipe (humanize, build arrangement, batch rename, chord from prompt). Triggers: "is my Ableton bridge working", "set up loophole", "connect Claude to Ableton", "/doctor", "/setup".
Use when building, redesigning, or reviewing a website or web surface that must not look generated. Covers landing pages, e-commerce (PLP, PDP, cart, checkout), car and vehicle inventory sites, course and cohort school pages, portfolios, dashboards, and marketing sites. Handles visual direction, WebGL and canvas effects, shadcn registry components, scroll choreography, typography, color, motion, empty and error states, accessibility, performance budgets, and multi-viewport visual verification. Also use when a page came out bland, templated, or "AI-looking" and needs a real direction, or when an installed registry component renders wrong.
Automate setup, configuration, execution, monitoring, and troubleshooting of AutoResearchClaw — the 23-stage autonomous research pipeline that generates conference-grade papers. Use when the user mentions ResearchClaw, wants to write a research paper autonomously, needs to set up or debug the pipeline, or says research paper, autonomous research, or paper generation.
Study unfamiliar codebases and produce evidence-backed knowledge artifacts. Use for repository orientation, architecture mapping, subsystem tracing, onboarding, or codebase documentation.
HTML-first persistent planning skill. Generates a single self-contained plan.html with interactive phases, drag-and-drop tickets, sliders, mockups, and embedded JSON state. Survives /clear via session catchup, tamper-protected by SHA-256, mirrors across 17 IDEs, ships 10 templates across Thariq's 9 categories, exports back to Markdown on demand. Use when asked to "plan it", "make me an html plan", "show me the plan", "render the plan", or when starting any multi-step task that needs a navigable artifact instead of a markdown wall.
Turn a real win into a set of designed, on-brand image assets for social media, email and a profile, in every size those channels need, built around a verified screenshot as proof. Use whenever someone lands a ranking, a milestone, a launch, a star count, an award, an acceptance, a shipped release, a chart position or any other public result and wants to post it, show it off, put it in a newsletter, or use it as hiring or fundraising evidence. Triggers on "make a screenshot I can post", "turn this into a social card", "banner for LinkedIn", "we hit #1", "we just crossed N users", "announcement image", "show off", "brag post", "celebrate this", or a pasted screenshot of a leaderboard, dashboard or chart.
About Ottermind skills
Every published skill from othmanadi. 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.