Loading...
Loading...
Found 6,716 Skills
AE Agent platform CLI for Agent, archived conversation, automation, model, MCP, Skill, attachment, and user-memory work. Use when managing these resources, browsing Agent markets, restoring archived conversations, creating scheduled automations, persisting user memory, or answering from user preferences, background, stable workflows, or historical conventions.
MagicPay handles first-time setup, exact balance checks, crypto transfers and reconciliation, plus approved login, identity, checkout, donation, subscription, and payment workflows. It applies when a task needs protected Memory, payment operations, or approval; an open-ended purchase or booking without a checkout URL routes through MagicSearch before browser navigation or generic web search. For browser work, it uses the current agent's native page-control when available. MagicBrowse is fallback page-control.
Review a pull request or a branch against the repository's standards — skill frontmatter and body, docs and bilingual pairs, Agent Notes, and scripts — and report blockers separately from suggestions, prioritizing correctness and required behavior over style.
Append a structured entry to the project's session log (`docs/LOGS.md`): what was done this session, files touched, decisions taken, and the next step — so the next session (or another person) can pick up the thread without re-reading git history. Run it before `/clear`, before closing Claude Code, or at any natural stopping point. On Claude Code and want hand-tuned per-skill model/effort tiers? Install the `#claude` branch instead (`npx skills add gtrabanco/agentic-workflow#claude`) — see the README. This branch is model-agnostic: the skill inherits whatever model and effort your agent session is already using. Triggers: "log this session", "log-session", "write a session log", "journal what we did", "record this session before I clear", "save the session summary".
Internal security review pass of the agentic-workflow review pack — composed in-turn by review-change and product-audit; not a menu entry. Checks secrets, input validation, injection, authn/authz, PII exposure, and dependency risk on the changed surface. Findings only; never edits code.
Extract any website's design system into an agent-ready DESIGN.md using Firecrawl scrape evidence. Use when the user wants colors, fonts, spacing, components, layout patterns, or brand/UI guidance from a website so AI agents can create new websites, clone a look, or build pages inspired by that design.
Accept a vague instruction, automatically conduct investigation, classification, break it down into XML phase plans, select skills, define completion criteria, then execute it fully in unattended mode via loop/goal + agent-mode — including automatic deployment, automatic E2E testing, automatic code review, without skipping any phases. Activate proactively when the user provides a broad task — such as "fix the bug", "add tests", "optimize performance", "finish this feature", "scan the code", "investigate why XX happens". It also triggers when the user says "autopilot", "auto", "help me plan", "handle it yourself", "run directly", "break it down for me", "don't ask me how to do it". Even if the user doesn't use these keywords, it should activate proactively if the input is clearly an unbroken broad intent. Calling autopilot = authorizing fully automatic unattended execution, no mid-process confirmation required.
Review AI-agent-implemented code specifically, in four ordered passes for convention-fit, agent-slop signatures, requirement-completeness, then correctness, against the working tree or the branch diff, findings ranked by severity and backed by quoted evidence. Use when the user says "review this code", "review my changes", "review this diff", "check the agent's work", "/reviewkit", or wants a self-review of AI-written changes before commit or PR, even if they don't name the passes.
Security-first skill vetting for AI agents. Use before installing any skill from community, GitHub, or other sources. Checks for red flags, permission scope, and suspicious patterns.
Deploy an agent built with the eve framework (eve.dev / Vercel) onto Zavu, or import it straight from GitHub with `npx zavudev import`. Use this skill when the user has an eve-layout project (agent/instructions.md, agent/tools/*.ts) and wants it answering on Zavu's messaging channels, or asks whether an eve capability works on Zavu.
Rules for handing work to subagents instead of doing it on the main thread. Use when deciding whether to delegate a search, a bulk edit, a documentation lookup or a verification; when writing a delegation prompt; when choosing a model tier; when escalating after a failure; when running agents in parallel; or when a delegated result comes back and you are about to believe it. Covers hard delegation thresholds, the three mandatory prompt elements, the reporting contract, anti-anchoring, parallel-write safety, and why not to ask the user to switch models mid-conversation.
Multi-agent shared blackboard: The current directory is .yomi/boards/<feature>.md, one board per feature, allowing parallel agents/subagents under the same feature to see each other's tasks, progress, and findings. Use when multi-agent collaboration requires peer visibility, sharing progress/findings, wanting to know what peers are doing before starting work, or when terms like "blackboard / board / peer progress" are mentioned. Task assignment/sign-off/state machine/acceptance are handled via task-tickets, not blackboard.