Progressive-disclosure instructions an agent loads on demand. Cheap until invoked, which is why the per-session figure on each card is usually two digits.
Use when working on any Java or JVM project: plain Java, libraries, CLI tools, Maven/Gradle builds, Spring Boot, Jakarta EE, MyBatis/MyBatis-Plus, JPA/Hibernate, Lombok, Java tests, Java code review, API design, exception handling, security review, refactoring, dependencies, Java version upgrades, javax/jakarta…
Extract the most controversial or genuinely-novel insights from a YouTube video and output them both as a .txt file and printed in the terminal. Use when the user provides a YouTube URL and wants the key ideas, hot takes, or original thinking — NOT video clips. Optionally cross-checks ideas against the web to judge…
Produces whiteboard-explainer video layers from a voiceover MP3 for Your Channel YouTube channel (and similar faceless curiosity-essay channels). Orchestrates a multi-agent pipeline that transcribes the audio, plans rapid-cut scenes synchronized to narration, writes per-scene image prompts in fixed whiteboard style…
Research-backed business strategy advisor using MBA frameworks — no MBA required. Use when users discuss business viability, revenue models, market opportunity, pricing, competitive analysis, growth planning, or any business problem that needs structured thinking. Also trigger when users mention frameworks by name…
Run the 8-phase product definition workflow for software-augmented hardware: Explore → High-Level Design → Component Arrangement → System Description → Gate Checklist → Product Visual → PPTX Carousel → PDF Carousel. Use when the user has a hardware+software product idea to develop.
Trigger when users say "explain with a story," "tell me a fable," "give me an analogy," "ELI5," or "help me understand intuitively" about a concept. Uses fables to illuminate abstract concepts — the story never mentions the term, only revealing it at the end.
Use when the user wants to create or edit an ArchAstro agent's config files before deployment, including AgentTemplate files, Script configs, custom tools, routines, and environment setup. Trigger phrases include "build this agent", "write the template", "create the scripts", "set up the routines", "author this agent…
Preview images, video, PDFs, code files, diffs, and tweets from inside an agent CLI that cannot render them. Use when the user asks to see, view, preview, show, or look at a file — screenshots, generated images, charts, mockups, video clips, PDFs, or a code diff — or says "show me", "let me see it", "preview that"…
Create, read and edit Microsoft Word .docx documents — reports, letters, contracts, formatted multi-section documents with headings, tables, images, headers/footers and styles. Also covers reading an existing .docx to extract or modify its content, filling a .docx template, converting to PDF, and the raw OOXML route…
A formatting workflow that turns Chinese Markdown, Word, or plain-text articles into HTML ready to paste into the WeChat public-account editor, with a preview page that includes one-click copying.
Writes git commit messages in a pure human-authored voice and strips AI attribution, tool watermarks, model names, co-author footers, and AI self-references. Use whenever creating, amending, rewriting, or reviewing a git commit message, including when running git commit, writing PR titles, or drafting commit bodies.
Splits a large change into small, single-purpose units of review — PRs, diffs, or CLs — each making one argument (one diff, one thesis) and each buildable and testable on its own. Use when a change is too big to review, when a feature builds on existing code, when working in a large monorepo with stacked diffs, or…
A method for reviewing code, bugs, diffs, branches, and pull requests. A diff is the set of changes between two versions of code, and a pull request is a proposed change submitted for review.
Full-cycle software development agent: plans, builds, tests, lints, fixes bugs, and writes production-grade README docs. ALWAYS use this skill when the user wants to: build or scaffold a new project, add features to existing code, fix bugs, improve code quality (lint, format, refactor), write or improve a README, add…
Drive IDA Pro through the IDA Pro MCP like a senior reverse engineer: don't just narrate decompiler output, transform the database. Use this whenever the user is reverse engineering, analyzing malware, working a crackme or CTF, or doing binary/firmware analysis with IDA Pro over an MCP connection (mrexodia/ida-pro-mcp…
Extract a complete agent-native-setup profile from an existing repo's agent setup (contracts, .claude/.cursor/.gemini tooling, MCP, docs conventions, git gates) — inventory, classify, parameterize, verify by byte-diff, and ship. Use when someone wants to turn a well-structured repo into a shareable profile.
Generates a complete, verified documentation suite for a codebase and wires it into AI-agent context files. Runs a multi-phase explore → generate → verify loop: scans the repo, writes 15 docs in docs/ (architecture, API reference, database schema, services, glossary, error catalog, security, and more) with Mermaid…
Plan and verify bounded agent graphs for complex coding work. Use when a coding agent needs to coordinate independent implementation, research, verification, auditing, isolated writers, merge ownership, or targeted repair loops. Prefer a single loop for small or genuinely sequential tasks.
Use when reviewing or writing LLM, RAG, MCP, tool, or agent code for OWASP-aligned security issues; triggered by "owasp my code", "owasp this PR", AI security review, PR review, or changes to AI system code.
A bias-check technique: spawn 2+ independent subagents, each attacking the idea from a different angle, to catch the flaw BEFORE it's set in concrete.
★not rated 6
changed 18d agoA0 tokens
originalMIT
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: