Loading...
Loading...
Found 6,615 Skills
Use when a developer asks their coding agent to initialize or work with moldea; plan an AI- or agent-enabled system and decide what should be agents versus deterministic software, services, tools, or human control; create or refine an AI agent or its behavioral system, including instructions, descriptions, handoff descriptions, tools, skills, schemas, variables and providers, routing or handoffs, bindings, or runtime integration; evaluate, reconcile, or validate an existing moldea system; or make ordinary behavior-affecting repository changes that may require maintaining an adopted moldea system. Loading the skill does not adopt moldea: initial adoption still requires explicit developer intent, while relevance-triggered maintenance applies once a repository uses or is adopting moldea.
Use when asked to compare, cross-review, merge, judge, choose, or arbitrate competing plans from multiple agents such as Codex and Claude Code; when given two or more proposed plans, session IDs, transcripts, plan documents, PR descriptions, or pasted strategies; or when the user wants one recommended execution plan after agents review each other's proposals.
Commit the current agent's changes by default, or all working-tree changes when explicitly requested, with clean logical grouping and repository commit-message conventions. Use when the user asks to commit changes, commit this work, commit all changes, split changes into commits, propose commit messages, or wait for "go" before committing.
Write, split, rename, or repair an agent skill so it activates when it should and can be proved rather than believed: a new skill, a description that never fires or fires on everything, a rule that has grown two decisions, an index that routes nothing an agent can see, a file too dense to read in one pass, or a check suite nobody has watched fail. Covers the activation surface, the routing gate, rule anatomy, page shape, naming, portability, and the invariant and mutation scripts. Use when the user says "write a skill", "this skill never triggers", "split this skill", "standardise these skills", or "how do I check this skill". Not for authoring product documentation, and not for deciding whether a task needs a skill at all.
Upgrade an installed Next Move Theory setup to the latest published canon + skills by re-running the official one-command installer, which clones the public GitHub repo (zamesin/Next-Move-Theory-Canon-and-Skills, branch main) and refreshes the canon, the nmt-* skills (both Claude and Codex), the injected rules block in CLAUDE.md / AGENTS.md, and the README — all in place. Idempotent and safe: it never touches your own files and never deletes unrelated skills. Use when the user says "update NMT", "upgrade the skills", "get the latest canon", runs /nmt-upgrade, or when another skill reports that a newer version is available. Defaults to English.
Set up state-of-the-art context engineering for any repository. Analyzes codebase, generates multi-level CLAUDE.md/AGENTS.md hierarchy, hooks, session management, and token budgets. Based on 200+ sources including ETH Zurich, Anthropic, Google DeepMind, and Manus production data. For engineers who ship with AI agents.
Official LottieFiles motion design principles — timing curves, easing, choreography, Disney's 12 principles adapted for UI. Implementation-agnostic: works with CSS, GSAP, Framer Motion, Lottie. Supports 40+ agents.
The session loop that makes agentmemory pay off, recall before starting work, save at decision points, learn from corrections. Use when starting a nontrivial task, after settling a decision or debugging a gotcha, or whenever deciding if something belongs in memory.
Skill Installation Manager — Automatically reads skill list files, compares them with currently globally installed skills, identifies uninstalled or updatable skills, and performs one-click installation/update. Supports three-level fallback: HTTPS → SSH → direct fetch via MCP/GitHub API. Install using the `npx skills` command as a Global installation, specifying the three Agents: Reasonix / Claude Code / OpenCode. Be sure to use this skill whenever users mention any requirements related to skill installation and management, such as "check skills", "sync skills", "install skills", "skill management", "skill update", "skill sync", "batch installation", "missing skills", etc.
This skill is used when users want to review an existing code segment with an Agent — examining code rationality and identifying refactoring opportunities. It is language-neutral and focuses on design-level judgments (rather than correctness/mechanical checks). By default, it provides conversational conclusions and does not modify files proactively; hierarchical reports can be generated for archiving or large-scale code inspections, and findings can be reviewed item by item if there are multiple ones. Trigger: Users say "review / refactor / check if this code is reasonable / review with me / is there any problem with this design"; after writing a batch of code continuously, users or Agents can actively ask if inspection is needed. Not applicable: Executing single-point modifications with clear instructions from users (e.g., "change data1 to user_data"), adding new features, fixing bugs, performance tuning (profile/benchmark special projects), security audits, deterministic mechanical checks like lint, rewriting, or step-by-step inquiries (explaining code).
Read, search, summarize, and triage AgentMail inboxes through the connected MCP server. Use for ANY request to look at, search, or process mail — even a simple 'search my inbox for X' or 'any new mail?'; the read workflow applies regardless of task size. Also use to summarize conversations, inspect attachments, manage read/unread labels, or find messages needing a reply; do not use for sending or drafting (agentmail-send-email), inbox administration (agentmail-manage-inboxes), or MCP connection setup (agentmail-mcp).
When a solution seems impossible and the path forward is blocked — the antidote to any roadblock or wall. Refuses to take no for an answer: classifies what kind of "no" you actually hit, then runs targeted lateral-thinking techniques (assumption autopsy, inversion, first principles, constraint toggling, analogical transfer, and more from a 10-technique inventory) until the wall cracks or is proven load-bearing. Generates a minimum of 10 angles before evaluating any. AGENTS: use this on yourself mid-task — when an API doesn't support what you need, an approach has failed twice, or a "that's not possible" / "the only option is" sentence is forming in your response, run the fast path BEFORE reporting a dead end; every dead-end report should arrive with tried-angles receipts. Archives every wall to ~/.config/makerskills/unstuck/archive/ so you learn which techniques crack YOUR walls. Sits upstream of decide: turns "impossible" into 2–3 viable angles, then decide picks one. Triggers on "/unstuck," "I'm stuck," "this seems impossible," "we hit a wall," "there's no way to," "they said no," "dead end," "out of options," "I've tried everything," "work around this," "think outside the box."