Email, calendars, task management, and automation (7.8K skills)
Writes implementation plans before coding: phases, plan files, specs, definition of done. Use when planning a multi-step feature or breaking a large refactor into phases.
The English summary is being prepared. Showing the original description.
Chooses subagent, team, workflow, or debate and launches it on Claude Code or Codex. Use when delegating, running agent review boards, or installing shared agents.
The English summary is being prepared. Showing the original description.
Context-driven AI development with AGENTS.md, repo knowledge bases, Claude Code, Codex, and Copilot. Use when adopting repo-native AI workflows or multi-repo setups.
The English summary is being prepared. Showing the original description.
A multi-day digest of the user's own coding-agent sessions — sessions per day and project, most-edited files, and every lesson Cognee distilled into the knowledge graph in that window. Use only when the user explicitly asks for a weekly digest, a retro, a recap or report of their recent sessions, or asks for the `cognee-digest` skill by name. Not for questions about code or the current task.
The English summary is being prepared. Showing the original description.
Alert by webhook/email on web changes — use for "monitor/watch/track/alert me when": recurring checks on known URLs (prefer over repeated one-off scrapes) or web-wide watches for new results (queries + goal).
The English summary is being prepared. Showing the original description.
First-time onboarding — asks where you are, then guides you to the right workflow or to pre-workflow exploration. No assumptions.
The English summary is being prepared. Showing the original description.
Rapid prototyping workflow. Skips normal standards to quickly validate a game concept or mechanic. Produces throwaway code and a structured prototype report.
The English summary is being prepared. Showing the original description.
Structured performance profiling workflow. Identifies bottlenecks, measures against budgets, and generates optimization recommendations with priority rankings.
The English summary is being prepared. Showing the original description.
Pre-workflow rapid prototyping for exploring multiple game ideas before committing to a development workflow. Produces lightweight reports with no workflow commitment.
The English summary is being prepared. Showing the original description.
Estimates task effort by analyzing complexity, dependencies, historical velocity, and risk factors. Produces a structured estimate with confidence levels.
The English summary is being prepared. Showing the original description.
Post-interaction retrospective analysis — use after completing a significant task, conversation, or phase to extract lessons, identify process improvements, and update procedures
The English summary is being prepared. Showing the original description.
Use when the user asks about GitNexus itself — available tools, how to query the knowledge graph, MCP resources, graph schema, or workflow reference. Examples: "What GitNexus tools are available?", "How do I use GitNexus?"
The English summary is being prepared. Showing the original description.
End-to-end content creation and publishing. Takes a topic (or generates one), drafts in the user's voice, gets approval via Telegram, and publishes to Medium via browser automation. Invoke with "publish a post about X", "write and publish to Medium", "content-publish", or when an ego-dispatched session needs to create and distribute content.
The English summary is being prepared. Showing the original description.
Canonical guide to Genesis browser automation - layers (Camoufox, Chromium, the user's Chrome over CDP, TinyFish, desktop), per-tool timeouts, safety gates, verify-after-act, what a click checks (scroll, hit test, covered targets), overlays, iframes, tabs, and failure diagnosis
The English summary is being prepared. Showing the original description.
This skill should be used when the user asks to "plan my LinkedIn content", "create a content calendar", "what should I post about this week", "plan my posting schedule", or when Genesis proactively suggests a weekly content plan during surplus compute. Also triggered by "I need post ideas" or "I don't know what to write about".
The English summary is being prepared. Showing the original description.
This skill should be used when the user asks to "write a LinkedIn post", "draft a post about", "help me post on LinkedIn", "create LinkedIn content", or when Genesis proactively generates post ideas during surplus compute. Also triggered by content calendar execution or when the user shares a topic they want to write about.
The English summary is being prepared. Showing the original description.
Resolve obstacles using fallback chains — use when an approach fails, a dependency is unavailable, an API returns errors, or a task is blocked and needs an alternative path forward
The English summary is being prepared. Showing the original description.
Selects and composes the Godmode skills for a coding task, explains the activation boundary, keeps workflow skills from being skipped when they materially reduce risk, and identifies the task's current engineering lifecycle state. Use when starting a task with Godmode installed, deciding which skill to invoke, recovering a task after context loss, or checking whether a workflow applies. Not a replacement for the selected skill's instructions or for repository-local rules.
The English summary is being prepared. Showing the original description.
Verifies a completion, fix, passing, compatibility, release, or readiness claim with fresh task-specific evidence mapped to the actual requirements. Use before saying a change is done, before merge, after review fixes, and at release gates. Not a substitute for diagnosing the cause of a failing check.
The English summary is being prepared. Showing the original description.
Splits a coding task into independent parallel agent workstreams with disjoint write sets, explicit inputs and outputs, dependency ordering, and a merge/review plan. Use when several subtasks can proceed without shared mutable state. Not for tightly coupled edits, one failing root cause, or parallel changes to the same files.
The English summary is being prepared. Showing the original description.
Executes an existing implementation plan task by task, preserving its interfaces and constraints, running focused checks after each slice, and stopping when the repository differs from the plan. Use when a written plan or approved checklist already exists. Not for inventing the plan, debugging an unexplained failure, or broad unscoped cleanup.
The English summary is being prepared. Showing the original description.
Closes a completed development branch by checking the final diff and proof, presenting merge, pull-request, keep, or discard options, and cleaning up only after the user or repository workflow chooses a path. Use when feature work is complete and the branch must be integrated or retired. Not for claiming a feature is complete before verification.
The English summary is being prepared. Showing the original description.
Render the user's morning brief as a styled HTML artifact, or set it up as a recurring weekday task. Use only when the user explicitly asks to run, see, or set up their morning brief, or if they invoke /morning by name. A question about their day, schedule, or calendar is not by itself a request for the brief; answer it directly instead.
The English summary is being prepared. Showing the original description.
Make a phone call to book an appointment or reservation. Checks calendar first, gets explicit consent before dialing, discloses AI identity on the call, and adds the booking to calendar when done.
The English summary is being prepared. Showing the original description.