New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Activation

by NoobyGains in NoobyGains/godmode

A skill your agent uses when starting any conversation - establishes how to locate and invoke skills, mandating Skill tool usage before ANY response including clarifying questions

MITAuto-check passedAgent Workflows

Install Activation

skills CLI
$ npx skills add NoobyGains/godmode --skill activation -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install NoobyGains/godmode activation --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/NoobyGains/godmode.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/activation .claude/skills/activation && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
activation
GitHub stars
107
Token cost
~2.4k tokens
SKILL.md length
718 words
Files
1
Skills in repo
34
Repo updated
First seen
Licence
MIT

At a glance

A skill your agent uses when starting any conversation - establishes how to locate and invoke skills, mandating Skill tool usage before ANY response including clarifying questions

  • Works in 3 steps: Protocols live at: [plugin-root]/skills/ → Each protocol has a definition:… → Read the SKILL.md and execute its…
  • Starting any conversation - establishes how to locate and invoke skills
  • SKILL.md covers Accessing Skills, The Mandate, Guardrails and Skill Ordering, plus 4 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Activation is an agent skill from NoobyGains/godmode. Use when starting any conversation - establishes how to locate and invoke skills, mandating Skill tool usage before ANY response including clarifying questions

Its SKILL.md is about 2.4k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Agent Workflows, covering Requirements gathering. The repository describes itself as: The AI development framework that thinks before it builds. 36 composable skills for Claude Code, Cursor, Codex, and OpenCode. The licence is MIT.

When your agent uses it

  • Starting any conversation - establishes how to locate and invoke skills
  • Mandating Skill tool usage before ANY response including clarifying questions

Example prompts

  • “/activation”

Workflow steps

3 steps, taken from the first numbered list in SKILL.md.

  1. Protocols live at: [plugin-root]/skills/
  2. Each protocol has a definition: [plugin-root]/skills/[protocol-name]/SKILL.md
  3. Read the SKILL.md and execute its instructions

What it can do on your machine

Read from SKILL.md and the folder at commit 441103a. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are dot).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Activation loads about 2.4k tokens when it runs. Until then it costs about 43 tokens; SKILL.md has 718 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~43
When it runs · the whole SKILL.md, loaded when a task matches
~2.4k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from NoobyGains/godmode at commit 441103a, republished under its MIT licence (© NoobyGains). 718 words, ~2,397 tokens.

Download SKILL.mdSave it as .claude/skills/activation/SKILL.md (or your agent's skills folder).
name
activation
description
Use when starting any conversation - establishes how to locate and invoke skills, mandating Skill tool usage before ANY response including clarifying questions
<CRITICAL-OVERRIDE>
When there is even a remote possibility that a skill is relevant to the current task, you MUST invoke it immediately.

YOU DO NOT HAVE THE OPTION TO SKIP A RELEVANT SKILL. IT IS MANDATORY.

This requirement is absolute. It cannot be reasoned away or deferred. </CRITICAL-OVERRIDE>

Accessing Skills

Plugin installation (standard setup): Invoke skills directly through the Skill tool. All protocols are auto-registered. Example: Skill("godmode:intent-discovery")

When the Skill tool cannot locate a protocol: Fall back to reading the file directly with the Read tool:

  1. Protocols live at: [plugin-root]/skills/
  2. Each protocol has a definition: [plugin-root]/skills/[protocol-name]/SKILL.md
  3. Read the SKILL.md and execute its instructions

Locating the plugin root:

  • Running from the repository: the working directory is the plugin root
  • Installed as a plugin: the CLAUDE_PLUGIN_ROOT environment variable contains the path

Other platforms: Consult platform-specific documentation for skill loading mechanisms.

Working With Skills

The Mandate

Invoke applicable skills BEFORE generating any response or taking any action. Even a marginal chance of relevance is sufficient reason to invoke. If an invoked skill turns out to be inapplicable, you can simply move on.

dot
digraph protocol_flow {
    "Message arrives" [shape=doublecircle];
    "About to enter planning?" [shape=doublecircle];
    "Intent discovery done?" [shape=diamond];
    "Run intent-discovery" [shape=box];
    "Could any skill apply?" [shape=diamond];
    "Invoke Skill tool" [shape=box];
    "Skill tool errored?" [shape=diamond];
    "Read SKILL.md fallback" [shape=box];
    "Announce: 'Applying [skill] for [goal]'" [shape=box];
    "Contains checklist?" [shape=diamond];
    "Track each checklist item" [shape=box];
    "Execute skill instructions" [shape=box];
    "Generate response" [shape=doublecircle];

    "About to enter planning?" -> "Intent discovery done?";
    "Intent discovery done?" -> "Run intent-discovery" [label="no"];
    "Intent discovery done?" -> "Could any skill apply?" [label="yes"];
    "Run intent-discovery" -> "Could any skill apply?";

    "Message arrives" -> "Could any skill apply?";
    "Could any skill apply?" -> "Invoke Skill tool" [label="yes, any chance"];
    "Could any skill apply?" -> "Generate response" [label="clearly not"];
    "Invoke Skill tool" -> "Skill tool errored?";
    "Skill tool errored?" -> "Read SKILL.md fallback" [label="yes"];
    "Skill tool errored?" -> "Announce: 'Applying [skill] for [goal]'" [label="no"];
    "Read SKILL.md fallback" -> "Announce: 'Applying [skill] for [goal]'";
    "Announce: 'Applying [skill] for [goal]'" -> "Contains checklist?";
    "Contains checklist?" -> "Track each checklist item" [label="yes"];
    "Contains checklist?" -> "Execute skill instructions" [label="no"];
    "Track each checklist item" -> "Execute skill instructions";
}

Guardrails

These internal thoughts are warning signs that you are rationalizing:

ThoughtTruth
"This is a straightforward question"Questions are tasks. Look for applicable skills.
"I should gather more context first"Skill invocation precedes clarification.
"Let me scan the codebase first"Skills define HOW to scan. Invoke first.
"I can check files and history quickly"Files lack conversational context. Invoke skills.
"Let me collect some data first"Skills prescribe data collection methods.
"This doesn't warrant a formal skill"If a matching skill exists, it must be used.
"I recall what this skill says"Skills get updated. Read the current version.
"This isn't really a task"Any action is a task. Look for skills.
"The skill is too heavy for this"Seemingly simple tasks often have hidden complexity. Use it.
"I'll do this one thing first"Invoke BEFORE doing anything.
"I'm making good progress"Undirected effort creates waste. Skills prevent this.
"I understand that concept already"Understanding a concept is not the same as following a skill. Invoke it.

Skill Ordering

When several skills might be relevant, follow this sequence:

  1. Challenge skills first (rationale) - question whether the work is worth doing before committing
  2. Process skills second (intent-discovery, fault-diagnosis) - establish the approach
  3. Reference skills third (reference-engine routes to: ux-patterns, design-research, github-search, codebase-research, system-design, deployment-advisor) - locate proven solutions before designing
  4. Design skills fourth (ui-engineering, design-integration, specification-first) - apply references to guide decisions
  5. Implementation skills fifth (test-first, project-bootstrap, pattern-matching, environment-awareness) - drive execution
  6. Quality skills sixth (quality-enforcement, security-protocol, completion-gate, comprehension-check, error-recovery) - enforce standards
  7. Orchestration skills (team-orchestration, delegated-execution) - leverage parallelism

"Let's build X" -> rationale -> intent-discovery -> reference-engine (routes to appropriate references) -> design skills -> implementation skills. "Build a website" -> rationale -> intent-discovery -> reference-engine -> design-research + ux-patterns -> ui-engineering -> implementation. "Fix this bug" -> fault-diagnosis first, then domain-appropriate skills. (rationale skipped for bugs) "Big project" -> rationale -> intent-discovery -> reference-engine -> task-planning -> team-orchestration (when warranted). "Agent is stuck" -> error-recovery activates proactively based on failure count detection. "What database/hosting should I use?" -> environment-awareness -> deployment-advisor -> system-design.

Show full SKILL.md (212 more words)Show less

Execution Mode Guidance

When a user says "use godmode" for a task, evaluate the task and suggest the optimal execution strategy:

dot
digraph execution_guidance {
    "Evaluate task" [shape=box];
    "Single atomic step?" [shape=diamond];
    "Handle directly" [shape=box];
    "Multiple independent parts?" [shape=diamond];
    "Requires peer coordination?" [shape=diamond];
    "Suggest Agent Teams" [shape=box style=filled fillcolor=lightgreen];
    "Suggest Parallel Delegation" [shape=box];
    "Multi-step sequence?" [shape=diamond];
    "Suggest Delegated Execution" [shape=box];
    "Suggest single-agent workflow" [shape=box];

    "Evaluate task" -> "Single atomic step?";
    "Single atomic step?" -> "Handle directly" [label="yes"];
    "Single atomic step?" -> "Multiple independent parts?" [label="no"];
    "Multiple independent parts?" -> "Requires peer coordination?" [label="yes"];
    "Multiple independent parts?" -> "Multi-step sequence?" [label="no"];
    "Requires peer coordination?" -> "Suggest Agent Teams" [label="yes"];
    "Requires peer coordination?" -> "Suggest Parallel Delegation" [label="no"];
    "Multi-step sequence?" -> "Suggest Delegated Execution" [label="yes"];
    "Multi-step sequence?" -> "Suggest single-agent workflow" [label="no"];
}

Present the suggestion before acting:

Based on my analysis, I suggest:

[Suggested strategy] because [reasoning]

- Agent Teams: [X] agents collaborating on [modules] concurrently
- OR Delegated Execution: [N] sequential tasks with review gates
- OR Parallel Delegation: [N] independent tasks running simultaneously
- OR Single agent: manageable enough to handle in one flow

Shall I proceed this way, or do you prefer a different approach?

Skill Categories

Rigid (test-first, fault-diagnosis): Follow precisely. Do not deviate from the discipline.

Flexible (design patterns): Adapt the principles to fit the situation.

The skill definition itself indicates which category applies.

YoloMode

When the user signals they want autonomous execution, skip all confirmation prompts and compress workflows — but never auto-pick labeled options.

Trigger phrases (case-insensitive):

  • "yolo", "yolomode", "yolo mode"
  • "just go", "just do it", "go for it"
  • "skip the questions", "don't ask"
  • "auto-pick", "you decide"

Behavior when active:

  • Skills that present A/B/C/D options ALWAYS pause for user selection — no exceptions
  • Intent-discovery compresses: survey + research + present recommended approach, skip per-section confirmation
  • Rationale analysis still runs (safety check) but is compressed — present analysis and options concisely
  • Completion-gate and test verification are NEVER skipped (quality is non-negotiable)

How skills reference YoloMode:

If YoloMode is active:
  -> State: "YoloMode active — proceeding with recommendation [X] because [reason]"
  -> Execute immediately
  -> Log which option was auto-selected

If YoloMode is NOT active:
  -> Present options with labels and recommendation
  -> Wait for user selection

YoloMode does NOT bypass:

  • Test execution (completion-gate)
  • Security checks (security-protocol)
  • Destructive operations (merge-protocol abandon confirmation)
  • Quality enforcement (quality-enforcement)

YoloMode is about speed, not recklessness. It trusts the agent's recommendation for design choices, not for safety checks.

User Directives

User directives specify WHAT needs to happen, not HOW. "Add X" or "Fix Y" does not mean bypass established workflows.

© NoobyGains, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/activation of NoobyGains/godmode.

Open the folder on GitHubat commit 441103a

Compare with similar skills

Activation next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Activation compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Activation this skillNoobyGains/godmode107—~2.4kAutomated safety check: PassMIT
Using Superpowersfarm-fe/farm5.6k35 repos~1.4kAutomated safety check: PassMIT
Interview Meaddyosmani/agent-skills103k6 repos~3.8kAutomated safety check: PassMIT
Grillingpietheinstrengholt/rssmonster56431 repos~510Automated safety check: PassMIT
Agentic Workflow Designerdotnet/Open-XML-SDK4.6k2 repos~3.5kAutomated safety check: PassMIT
Ask User QuestionMemTensor/MemOS12k—~1kAutomated safety check: PassApache-2.0

Similar skills

  • Using Superpowers

    farm-fe/farm

    A skill your agent uses when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions

    5.6k GitHub starsUsed in 35 repos~1.4k tokens
    Agent WorkflowsAuto-check passed

  • Interview Me

    addyosmani/agent-skills

    Asks one question at a time, each with a best guess attached, until the agent is about 95 percent sure what you really want, before any plan, spec or code.

    103k GitHub starsUsed in 6 repos~3.8k tokens
    Agent WorkflowsAuto-check passed

  • Grilling

    pietheinstrengholt/rssmonster

    Grill the user relentlessly about a plan, decision, or idea.

    564 GitHub starsUsed in 31 repos~510 tokens
    Agent WorkflowsAuto-check passed

  • Agentic Workflow Designer

    dotnet/Open-XML-SDK

    Official

    Interviews you one question at a time about goal, trigger, permissions and data needs, then drafts a single agentic workflow markdown file.

    4.6k GitHub starsUsed in 2 repos~3.5k tokens
    Agent WorkflowsAuto-check passed

  • Ask User Question

    MemTensor/MemOS

    Shows a question as a modal in the interface to clarify a task, collect a preference or get approval, since the user cannot see terminal output.

    12k GitHub stars~1k tokensUpdated yesterday
    Agent WorkflowsAuto-check passed

  • Brainstorming Before Building

    jnMetaCode/superpowers-zh

    Turns a rough idea into an approved design before any code is written, sorting the request into spike, bounded or architectural and enforcing an approval gate.

    8.3k GitHub stars~1.8k tokensUpdated yesterday
    Agent WorkflowsAuto-check passed

More from NoobyGains/godmode

All 34 skills in this repo

  • Agent Messaging

    NoobyGains/godmode

    A skill your agent uses when dispatching subagents, composing prompts for teammates, structuring handoff reports, or managing context boundaries between agents.

    107 GitHub stars~3k tokensUpdated 7 mo ago
    Auto-check passed

  • Codebase Research

    NoobyGains/godmode

    A skill your agent uses when building ANY feature within an existing project - search the current codebase for existing patterns, conventions, similar implementations, and established approaches…

    107 GitHub stars~3.2k tokensUpdated 7 mo ago
    Auto-check: notes

  • Completion Gate

    NoobyGains/godmode

    A skill your agent uses when about to declare work done, fixed, or passing, before committing or opening PRs - demands executing verification commands and reading their output before making any…

    107 GitHub stars~1.6k tokensUpdated 7 mo ago
    Auto-check passed

  • Comprehension Check

    NoobyGains/godmode

    A skill your agent uses when implementing any substantial feature, multi-file modification, or architectural change - produces a plain-language walkthrough of every alteration so the developer can…

    107 GitHub stars~1.5k tokensUpdated 7 mo ago
    Auto-check passed

  • Delegated Execution

    NoobyGains/godmode

    A skill your agent uses when executing implementation plans with independent tasks in the current session

    107 GitHub stars~2.4k tokensUpdated 7 mo ago
    Auto-check passed

  • Deployment Advisor

    NoobyGains/godmode

    A skill your agent uses when making technology, hosting, or infrastructure decisions — recommends services, databases, and deployment strategies based on project requirements and what the user…

    107 GitHub stars~4k tokensUpdated 7 mo ago
    Auto-check: notes

Categories

Questions about Activation

What does Activation do?

A skill your agent uses when starting any conversation - establishes how to locate and invoke skills, mandating Skill tool usage before ANY response including clarifying questions. Activation is an agent skill from NoobyGains/godmode.

When should I use Activation?

Activation fits situations like: starting any conversation - establishes how to locate and invoke skills; mandating Skill tool usage before ANY response including clarifying questions.

How do I install Activation in Claude Code?

Run `npx skills add NoobyGains/godmode --skill activation -a claude-code`. Or copy the skill folder (skills/activation in NoobyGains/godmode) into .claude/skills/activation in your project. Claude Code loads it when a task matches its description.

How do I install Activation in Codex?

Run `npx skills add NoobyGains/godmode --skill activation -a codex`. Or copy the skill folder (skills/activation in NoobyGains/godmode) into .agents/skills/activation in your project. Codex loads it when a task matches its description.

Can I use Activation in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add NoobyGains/godmode --skill activation -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/activation, .gemini/skills/activation, .github/skills/activation and .opencode/skills/activation in your project.

What does Activation need to run?

SKILL.md names no scripts, command-line tools or credentials: Activation is instructions for the agent only.

Does Activation access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Activation safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Activation use?

Activation is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Activation use?

About 2.4k tokens (SKILL.md is roughly 9.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Activation?

Skills that share tags, products or a category with Activation: Using Superpowers (farm-fe/farm, 5.6k stars), Interview Me (addyosmani/agent-skills, 103k stars), Grilling (pietheinstrengholt/rssmonster, 564 stars) and Agentic Workflow Designer (dotnet/Open-XML-SDK, 4.6k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Activation?

NoobyGains (a GitHub user) maintains it in NoobyGains/godmode, which has 107 GitHub stars. The repository holds 34 skills in this directory. The repository was last updated on March 9, 2026.

Source: NoobyGains/godmode on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.