arpitbbhayani
UserSkills for apes like us, so we can do our jobs better and make our lives easier.
Categories
Indexed Skills (14)
ape-present
Converts a blog post into a single self-contained HTML document -- a visual-heavy, readable walkthrough with custom animated diagrams, short and crisp bullet points, and a natural explanation flow from first principles. Trigger on "ape present", "make this presentable", or "turn this post into a doc I can walk people through".
ape-visualize
Builds interactive, browser-based 3D Three.js visualizations of any mathematics or science concept as a single, self-contained HTML file. Takes a concept and a depth level (Simple, Intermediate, Advanced). Trigger on "ape visualize", "ape visualize math", "ape visualize science", "visualize math", "visualize science", "visualize concept", "ape simulate", or "/ape-visualize".
ape-teach
Masterclass teacher that takes any concept, note, URL, paper, or write-up, expands on it if needed, and teaches it through and through, step by step. Uses real-world and engineering mental models, selective and intuitive analogies with breaking points only where needed, visual ASCII diagrams, minimal code snippets, in-between check questions, web research when required, and prompts to up the ante and go deeper until the user explicitly signals they are done. Trigger on "ape teach", "teach me", "masterclass on this", "explain this step by step", or when the user provides a concept, note, paper, or link and asks to learn or be taught it thoroughly.
ape-cut-fluff
A surgical editor that strips fluff -- hedging, throat-clearing, redundancy, padding, filler -- and drives writing down to the bare minimum word count needed to convey the concept. Use whenever the user says "cut the fluff", "trim/tighten this", "make this crisp", "remove filler/redundancy", "edit this down", or shares text, a file, a blog post, or a URL and asks to cut the fluff. Accepts a file path, pasted content, or URL; outputs the tightened version.
ape-help-me-understand
Digests dense content -- a post, paper, doc, or thread -- into a TLDR that keeps the numbers and caveats, a so-what naming why it matters, the key points, and an analogy with its breaking point. Trigger on "ape understand", "tldr this", "help me understand this", "give me an analogy", or when the user shares a post, paper, doc, or thread and asks to digest or summarize it. Do not trigger for plain questions that want a direct answer, not a digest.
ape-plan-project
Splits a product + engineering spec into phases, each a working vertical slice with its own agent-ready design doc. Use for "ape plan project", "plan this project", "phase this spec", or "split this into milestones for an agent to build".
ape-poke-holes
Adversarial review of design docs, specs, plans, blog posts, and technical writeups. Finds failure modes, unstated assumptions, scale cliffs, and gaps in understanding -- the questions a reader is left holding, the steps that were hand-waved, the claims that were never earned. No praise, no solutions, only holes. Trigger on "ape poke holes", "poke holes in this", "what could go wrong", "what is missing here", "red-team this", or any request for adversarial review of a design or an explanation.
ape-quiz-me
Quizzes you on content you claim to have read -- Socratic, one question at a time, hints that narrow but never reveal. Ends with a verdict on what you understood versus merely recited. Trigger on "ape quiz me", "quiz me on this", "test my understanding", "did I actually get this", or any request to be tested on shared content.
ape-review-blog
Reviews engineering blog drafts. Use this skill whenever the user says "ape review blog", "review blog", "review this post", "give feedback on draft", "what is wrong with this post", or pastes a blog draft asking for critique, feedback, or editorial review. Also trigger when the user shares a draft and asks if it is ready to publish. Always use this skill for any engineering blog review request, even if the user just says "thoughts?" after pasting a post.
ape-rewrite-blog
Rewrites an engineering blog draft by first running the ape-review-blog skill on it and then applying every suggested fix to produce a revised version. Use this skill whenever the user says "ape rewrite blog", "rewrite blog", "rewrite this post", "apply review suggestions", "fix the draft", "rewrite the draft", or shares a blog file and asks to apply review feedback. Also trigger when the user has already received a review and wants the suggestions implemented in a new file. Always use this skill for any engineering blog rewrite request where the goal is to produce a fixed-up draft, not just a review. The rewrite is written to a sibling file with the `-ape.md` suffix.
ape-style-markdown
Apply consistent, professional Markdown formatting rules whenever producing or reformatting Markdown output. Use this skill when generating any Markdown document, when the user asks to reformat or clean up existing Markdown, when producing README files, technical docs, notes, or any other content that will be rendered as Markdown. Trigger even when the request seems simple -- any Markdown output should follow these rules. Do not use this skill for non-Markdown outputs such as plain text, HTML, or code-only responses.
ape-write-pseudocode
Guidelines for writing pseudocode for functions and algorithms. Use this skill whenever the user asks to write pseudocode, sketch out an algorithm, or describe the logic of a function at a high level. Trigger on phrases like "write pseudocode", "sketch this algorithm", "pseudocode for this function", or "describe the logic".
ape-cli-terminal-experience
Designs the terminal experience of a CLI app the way Claude Code does it -- palette, status glyphs, spinners, progress narration, prompts, confirmations, listings, key hints, and full-screen TUI views. Trigger on "ape cli terminal experience", or whenever the task involves printing to a terminal from a CLI: adding or restyling output, adding a spinner or progress indicator, writing a prompt or confirmation, building a TUI, choosing exit codes, or deciding stdout vs stderr. Also trigger on casual phrasings like "make the output nicer", "add colour", "this CLI looks ugly". Read this before writing the first line of output code.
ape-commit
Defines how to write and format git commit messages. Use this skill whenever the user asks you to write, draft, suggest, or format a git commit message, summarize changes into a commit, or help stage and describe code changes. Trigger even for casual requests like "write me a commit for this" or "what should my commit say".
Bio shown is the top-scored skill's repo description as a fallback — real GitHub bios land in a future update.