Generate Improvement Ideas Agent Skill

Generate and evaluate grounded ideas. Use when the user wants ideas, improvements, or surprising directions before choosing one to…

Context cost
43.9k tokensestimated from the bundle, loaded when it triggers
Bundle
12 files · 175.6 kBtext throughout, nothing executable
Licence
MITthe author’s own terms
Last change
—no release on file
Servers it uses
Noneruns standalone

What it does

Generate and evaluate grounded ideas. Use when the user wants ideas, improvements, or surprising directions before choosing one to develop. Not for refining an idea they already have (ce-brainstorm) or judging one already on the table (ce-pov).

What this skill changes about the agent has not been set out here as a list. Its SKILL.md, shown below, says it in the author’s own words.

productivity

The skill itself

A skill is instructions the model reads, so you can see what you are getting: below is the start of its SKILL.md. The front matter loads with every session, the body loads when the skill triggers, and the whole file comes with the install.

SKILL.md7.1 kB · preview
--- name: ce-ideate argument-hint: "[feature, focus area, or constraint] [output:md]" ---
8# Generate Improvement Ideas
9
10**The current year is 2026** — use it when dating documents and checking recent artifacts.
11
12ce-ideate runs before ce-brainstorm. This skill answers "which ideas are worth exploring?" ce-brainstorm then answers what one chosen idea should mean. ce-plan answers how it gets built.
13
14**Done:** a ranked ideation artifact is written to <root>/ideation/ when that root is present, else to a CE temp path. Every idea generated has been critiqued, and the survivors are explained. The user is left holding the next-steps menu. No requirements, plans, or code.
15
16## Boundaries
17
181. **Ground before ideating.** No advice detached from the repo.
192. **Generate many, critique all, explain survivors only.** Generate the full candidate list before critiquing any of it. Rejection is explicit and carries a reason; this is not optimistic ranking.
203. **Send the user to brainstorming for action.** Never skip from ideation output to planning.
214. **Never dispatch on an unidentified subject.** Ask instead, through the host's blocking question tool already in the current tool list (match by capability, not by a host-specific name). Presence in the current tool list is proof the tool exists; never call a user-facing question tool to discover whether it exists. If a matching tool is listed but unloaded, use the host's tool-discovery primitive to load that capability — do not search for another host's tool name. Where no such tool is in the list, offer numbered options on the user-visible surface. Never skip a question silently. Keep "Surprise me" a real option, alongside a Cancel that exits cleanly. Do not ask about solution direction, constraints, audience, tone, or success criteria; ce-brainstorm asks those. If it takes more than 3 questions, ideation is the wrong workflow.
225. **Never print the internal taxonomy label.** The labels repo-grounded, elsewhere-software, and elsewhere-non-software only decide which agents to dispatch. Describe the mode to the user in the topic's own words.
236. **Warn and proceed when grounding fails.**
247. **Show the user the cost line before dispatching.**
25
26The **focus hint** is any optional context this run was invoked with, from the user or from a calling skill. The rest of this skill calls it {focus_hint}.
This is a preview of SKILL.md. Download or install the skill to get the whole thing.
In the file
SKILL.md1,061 words
Files12
LicenceMIT
Why you can read it

Nothing in a skill executes. The client loads the text and the model follows it, so a skill can be audited the way a runbook is — by reading it.

What it costs in context

Skills are not billed by the call. They are paid for in context: every token the instructions occupy is a token your code, your diff and your conversation cannot use. Here is what this one takes and when it takes it.

≈90
always loaded
The name and description, so the model knows the skill exists and when to reach for it.
43,810
on trigger
The instruction body and 11 supporting files, read only when the skill fires.
21.9%
of a 200k window
Ten skills this size would not fit in the window together.
050k100k150k200k context window

43.9k tokens, estimated from the bundle at four bytes to the token, held for the rest of the session once it triggers. Heavy. Teams tend to install this one per project rather than globally, and load it only when the job comes up.

Servers bill, skills cost

A server charges by the month. A skill charges once per session, in context, and then keeps charging it for as long as the session lives.

Before and after

The same question, put to the same model twice: once as it comes, and once with these instructions loaded.

No worked example has been published for this skill yet.

The procedure it runs

The procedure has not been set out here step by step. It is in the body of its SKILL.md: the start of it is shown above, and the whole file comes with the install.

Prose, not code

These steps are written for a model to follow, not executed by a runtime. It can still be told to skip one, and it will say so when it does.

Servers it uses

None. This skill calls no MCP servers at all.

Everything it needs is in the instructions, so it works in a project with nothing connected — the model reads the file and changes how it works with what it can already reach.

Its SKILL.md does not declare which tools it asks the agent for, so what it touches is whatever the instructions themselves ask for — read them before you install it.

What it asks for
Writes filesnot declared
Network accessnot declared

This SKILL.md carries no allowed-tools line, so neither is declared. A skill grants no permissions of its own — it can only ask for tools your client already has.

What it will not do

Every skill is narrow, and the useful ones say where they stop. These are the jobs this one is the wrong tool for.

What this skill is not for has not been published here. Nothing is implied by that: it is a section the author has not filled in.

What is in the bundle

12 files, 175.6 kB on disk. A bundle is text throughout: the instructions the model reads, plus the templates it fills in.

  • SKILL.md7.1 kB
  • references/divergent-ideation.md18.8 kB
  • references/html-rendering.md34.6 kB
  • references/ideation-sections.md8.7 kB
  • references/markdown-rendering.md10.9 kB
  • references/post-ideation-workflow.md20.2 kB
  • references/universal-ideation.md19.2 kB
  • references/web-research-cache.md4.2 kB
  • references/agents/issue-intelligence-analyst.md15.8 kB
  • references/agents/learnings-researcher.md16.6 kB
  • references/agents/slack-researcher.md10.4 kB
  • references/agents/web-researcher.md9.1 kB
What is not in it

No dependencies and nothing executable: a skill is text the agent reads, so the bundle is 12 files you can review in full before installing. The MIT licence covers the templates and examples as well as the instructions.

Install

Installing copies the bundle into your project. Nothing runs at install time — the files sit on disk until the model reads them.

# Generate Improvement Ideas · 43.9k tokens when loaded · macOS, Linux mkdir -p .claude/skills && t=$(mktemp -d) && curl -fsSL -o "$t/bundle.tar.gz" https://mcprush.com/api/skills/generate-improvement-ideas/bundle.tar.gz && tar -xzf "$t/bundle.tar.gz" -C "$t" && [ -d "$t/generate-improvement-ideas" ] && { [ ! -e .claude/skills/generate-improvement-ideas ] || { mv .claude/skills/generate-improvement-ideas "$t/.previous" && echo "Previous copy moved to $t/.previous"; }; } && mv "$t/generate-improvement-ideas" .claude/skills/ && echo "Installed .claude/skills/generate-improvement-ideas"
On Windows, or any OS with Node 20+
npx mcprush@latest skill add everyinc/generate-improvement-ideas

Windows PowerShell says 'running scripts is disabled on this system'? Run Set-ExecutionPolicy -Scope CurrentUser RemoteSigned once, or type npx.cmd instead of npx (codex.cmd, gemini.cmd, grok.cmd likewise). PowerShell 7 needs neither. Writes to .claude/skills/generate-improvement-ideas/ in the current project. For every project instead, run mkdir -p ~/.claude/skills && t=$(mktemp -d) && curl -fsSL -o "$t/bundle.tar.gz" https://mcprush.com/api/skills/generate-improvement-ideas/bundle.tar.gz && tar -xzf "$t/bundle.tar.gz" -C "$t" && [ -d "$t/generate-improvement-ideas" ] && { [ ! -e ~/.claude/skills/generate-improvement-ideas ] || { mv ~/.claude/skills/generate-improvement-ideas "$t/.previous" && echo "Previous copy moved to $t/.previous"; }; } && mv "$t/generate-improvement-ideas" ~/.claude/skills/ && echo "Installed ~/.claude/skills/generate-improvement-ideas" (macOS, Linux) — or add --global to the npx line. The curl line replaces .claude/skills/generate-improvement-ideas/ only after the download succeeds, so files left there by another skill of the same name, or by an older release, do not mix in. A copy already there is moved aside, not deleted, and the line prints where. It appears as ce-ideate in Gemini CLI, Codex, Copilot and Grok (its own name); Claude Code lists it by the folder name, generate-improvement-ideas.

Which clients pick it up on their own

A skill is a folder of text. Most of these read a skills folder and pick it up without being told; the rest take the same folder another way — an upload in the app, a parameter on an API call — and then choose it by its description just the same.

Claude Code.claude/skills/
Claude DesktopCustomize › Skills
ChatGPTSkills › Create › Upload
Cursor.cursor/skills/
VS Code.github/skills/
Codex CLI.agents/skills/
Gemini CLI.gemini/skills/
Grok Build.grok/skills/
Microsoft CopilotSkills › Upload a skill
PerplexityComputer › Skills › Upload a skill
DeepSeek Harness.dsh/skills/
Zed.agents/skills/
Devin Desktop.devin/skills/
Windsurf (legacy).windsurf/skills/
OpenAI Agents SDKInstructions or sandbox Skills
HTTP / APIa request parameter
This release
Versionnot versioned
Publishedno release date on file
PriceFree
Referenceeveryinc/generate-improvement-ideas

Versions

Its author publishes no version number, so there is nothing here to pin to: what you install is the folder as it stands today. Instructions change more often than APIs do — a skill can be rewritten entirely without anything it depends on moving.

Pinning

Nothing to pin to: this skill carries no version number of its own. What you install is what the folder holds on the day you install it.

Reviews

—no reviews yet

Nobody has reviewed this skill yet. The rating is the mean of the reviews written here, so there is none until somebody writes the first.

Sign in to review it

A review is tied to an account so it can be answered, edited and taken down by the person who wrote it.

Sign in
Who can post

Anybody with an account, one review each. It carries the version that was current when you wrote it, and the publisher may reply once.

Publisher
Servers0
Claim this skill