Firebase MCP
Gives AI development tools Firebase-specific capabilities and expertise.
Turn vague research directions into falsifiable, evidence-grounded Research Idea Briefs with a six-stage Codex workflow.
If you made this, paste this code into your README. The badge links back to this page.
[](https://mcp.popnx.com/en/skills/cpt13-g-clarify-research-idea)MCP servers that connect the AI to services for the same work
Gives AI development tools Firebase-specific capabilities and expertise.
Supabase’s official server lets AI create tables, query data and review project settings in your Supabase database.
Same kind of work, ordered like the Skills list
| This one clarify-research-idea | timesfm | Shadowbroker | google-maps-scraper | tradingview-mcp | |
|---|---|---|---|---|---|
| Maker | cpt13-g | google-research | BigBodyCobain | gosom | atilaahmettaner |
| Skills | 1 | 1 | 1 | 1 | 1 |
| GitHub stars | 298 | 35,629 | 11,602 | 8,209 | 5,307 |
| Last code change | Jul 26, 2026 | Nov 13, 2026 | Nov 17, 2026 | Nov 15, 2026 | Nov 15, 2026 |
| License | – | Apache-2.0 | AGPL-3.0 | MIT | MIT |
1 skills (instruction sets) by cpt13-g that an AI reads and follows · not an MCP server
MCP = the hands
Connects the AI to an outside service or data, such as reading Notion or creating an invoice. A program or server has to be running.
Skill = the manual
A text file that teaches the AI how to do a task. It connects to nothing.
Some overlap: a few Skills run scripts that call tools, and a few MCP servers only send knowledge. Start from the task you want done.
Codex
From the maker’s README and the folders in the repo
GitHub account cpt13-g (person), 5 years old
★ 298 stars, few users so far · code last changed Jul 26, 2026
No, plain text files the AI reads and follows
No scripts, so it does not go online by itself
No hooks or writes to machine settings found
Checked automatically from the repo files at commit 1f8334d (read only, nothing was run). Not a safety guarantee: read it and decide for yourself
First: which AI do you use?
Pick your app and this page shows only how to install it there
This skill has no license, so we do not hand out a ZIP from our site. Download it from GitHub and arrange the folder yourself, or use "Let the AI install it" above, which is easier
Download from GitHub (whole repo) ↗
Unzip it, then zip only the .agents/skills/clarify-research-idea folder again. The ZIP must have a clarify-research-idea folder with SKILL.md at the top level, no loose files
+Create skillUpload a skillpick clarify-research-idea.zip
SettingsCapabilitiesCode execution and file creation
Turn on Code execution and file creation first (newer menus: Create and edit files) · personal plans: Settings → Capabilities · Team/Enterprise: an admin turns it on under Organization settings → Plugins & skills · every plan, including Free
Upload once; it works in claude.ai and Claude Desktop, and in recent Claude Code signed in with a Claude account (not with an API key)
Cowork and cloud sessions use the skills turned on in your claude.ai account, not ~/.claude/skills on your computer (Claude Desktop scheduled tasks run locally and still load it)
Checked against official docs Nov 12, 2026 · Source: support.claude.com, support.claude.com, code.claude.com
Copy this sentence and paste it into a Claude Code chat
For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
Restart Claude Code, then type /clarify-research-idea or ask for a matching task and Claude picks it up
Checked against official docs Nov 12, 2026 · Source: code.claude.com
A Skill is instructions the AI will follow. Read the files before installing, and install only from makers you trust.
Mac: press Command+Space and type Terminal · Windows: the command below does not work in PowerShell; use “Let AI install it” above instead
This downloads the repo to a temporary folder and copies only the folders that contain a SKILL.md
Checking the commands · copy buttons appear once they pass
The ChatGPT desktop app has Codex built in, and Codex reads skills from ~/.agents/skills
Open Codex in the ChatGPT desktop app and paste this sentence into the chat
The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
Put the clarify-research-idea folder at ~/.agents/skills/clarify-research-idea
~ is your home folder ($HOME)
A Skill is instructions the AI will follow. Read the files before installing, and install only from makers you trust.
Mac: press Command+Space and type Terminal · Windows: the command below does not work in PowerShell; use “Let AI install it” above instead
This downloads the repo to a temporary folder and copies only the folders that contain a SKILL.md
Checking the commands · copy buttons appear once they pass
Checked against official docs Nov 15, 2026 · Source: learn.chatgpt.com
Skills you install yourself do not work here; only skills that come with a plugin from the directory
To use this skill with ChatGPT, use the ChatGPT desktop app as above
Checked against official docs Nov 15, 2026 · Source: learn.chatgpt.com
Copy this sentence and paste it into a Codex chat · Works in Codex inside the ChatGPT desktop app, Codex CLI and the IDE extension
For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
Codex picks up newly installed skills by itself; if one does not show up, restart Codex · To use it: in ChatGPT type @ and pick the skill · in Codex CLI or the IDE extension run /skills or type $ and the skill name
Checked against official docs Nov 15, 2026 · Source: learn.chatgpt.com
A Skill is instructions the AI will follow. Read the files before installing, and install only from makers you trust.
Mac: press Command+Space and type Terminal · Windows: the command below does not work in PowerShell; use “Let AI install it” above instead
This downloads the repo to a temporary folder and copies only the folders that contain a SKILL.md
Checking the commands · copy buttons appear once they pass
Copy this sentence and paste it into a Cursor chat
For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
In Cursor’s Agent chat, type / and pick clarify-research-idea
Checked against official docs Nov 12, 2026 · Source: cursor.com
A Skill is instructions the AI will follow. Read the files before installing, and install only from makers you trust.
Mac: press Command+Space and type Terminal · Windows: the command below does not work in PowerShell; use “Let AI install it” above instead
This downloads the repo to a temporary folder and copies only the folders that contain a SKILL.md
Checking the commands · copy buttons appear once they pass
For other apps that read skills. The sentence gives the paths for Claude Code, Codex and Cursor so the AI picks the one for your app · Copy this sentence into the app’s chat
For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
Checked against official docs Nov 12, 2026 · Source: code.claude.com, learn.chatgpt.com, cursor.com
Other apps that support Agent Skills (such as Gemini CLI or GitHub Copilot) use different folders. Check that app’s guide, then copy the folder with the SKILL.md there.
Skill folders checked against the official Claude Code, Codex and Cursor guides on Nov 11, 2026
The text below comes from the maker’s repo, not from PopNx MCP
Showing the first 8,000 characters · Open the full file on GitHub
---
name: clarify-research-idea
description: Turn vague or partially formed AI, computer-science, data-driven, and engineering-method research directions into evidence-grounded, falsifiable, paper-ready Research Idea Briefs through heuristic questioning, staged confirmation, literature positioning, novelty attack, and method-figure planning. Use when the user needs to clarify a research idea, formalize inputs/outputs/objectives/constraints, frame background and motivation, select 3-5 anchor papers, identify a defensible gap, derive 2-3 contributions, stress-test novelty, or design an input-to-output method framework and core-paper figure. Also trigger on requests such as 明确科研 idea、启发式梳理 idea、互动追问科研问题、梳理论文创新点、定义研究任务、找对标论文、把研究方向变成论文方案、画方法框架图. Do not use as the primary workflow for running experiments, exhaustive systematic reviews, drafting full manuscript sections, or polishing finished prose.
---
# Clarify Research Idea
Convert an early research direction into an auditable idea architecture before detailed experiment design or manuscript writing. Preserve the researcher's judgment: make assumptions and framing visible, challenge weak novelty, and never manufacture supporting evidence.
## Choose the operating mode
Use `guided` by default when the question, gap, or method is uncertain. Ask one high-information question at a time, maintain a visible working draft, and pause at the three checkpoints.
Use `synthesize` when the user supplies enough material or explicitly requests a one-pass result. Complete the brief with labeled assumptions; mark checkpoint-dependent claims `UNCONFIRMED` and request confirmation at the end.
State the selected mode, research domain, maturity level, and intended deliverable in one short line. Let the user correct them cheaply.
## Run the heuristic interaction loop
Read [interactive-heuristics.md](references/interactive-heuristics.md) in `guided` mode, whenever the user's idea is vague, or whenever the user asks for interactive clarification. Treat interaction as part of the method, not as casual clarification.
Use this turn pattern:
1. State the current bottleneck in one sentence.
2. Ask one high-information question that will change the idea architecture.
3. Offer 2-3 plausible answer directions when the user is unsure.
4. Update the visible `Working Idea Canvas` with provenance labels before asking the next question.
Do not overwhelm the user with a survey. If multiple questions are useful, choose the one that best constrains the task, gap, hypothesis, or evidence path. If the user asks for a fast one-pass result, switch to `synthesize` and mark unconfirmed decisions explicitly.
## Maintain provenance
Label substantive content throughout the workflow:
- `PROVIDED`: stated or supplied by the user.
- `VERIFIED`: supported by a checked primary source or supplied artifact.
- `INFERRED`: reasoned from available material but not directly established.
- `PROVISIONAL`: useful working hypothesis awaiting evidence or user confirmation.
- `UNKNOWN`: missing and consequential.
Do not silently upgrade one status to another. When browsing or academic-search tools are available, verify time-sensitive literature claims and bibliographic metadata. Treat failure to find a paper as search incompleteness, not proof of novelty.
## Run the workflow
### 0. Scope the session
Determine the application, research object, current idea, intended venue or audience, available data or system, resource limits, and desired output language. Stay centered on AI, computer science, data-driven science, and engineering-method papers. If the request is primarily qualitative or non-methodological, explain that the mathematical contract must be adapted before continuing.
Identify whether the user has: a broad interest, a question without a task definition, a method without positioning, anchor papers without a gap, or a nearly complete idea needing audit. Use the maturity triage in [interactive-heuristics.md](references/interactive-heuristics.md) to choose the first question. Reuse supplied documents and prior decisions instead of re-asking settled questions.
### 1. Establish the Task Contract
Read [task-formalization.md](references/task-formalization.md). Define the inference-time inputs, required outputs, data or interaction process, model or decision function, objective, constraints, evaluation measures, baselines, assumptions, and explicit exclusions. Use mathematical notation only when it removes ambiguity; do not invent a loss function for appearance.
Require alignment among the claimed problem, information available at use time, optimization target, and evaluation metric.
**Checkpoint 1 — Task Contract:** Present the one-sentence task, compact formulation, success criterion, assumptions, and scope boundaries. In `guided` mode, obtain user confirmation before treating the contract as fixed.
### 2. Make the argument and framing explicit
Read [framing-and-motivation.md](references/framing-and-motivation.md). Build the chain:
`background -> consequential friction -> unresolved cause -> required capability -> proposed research move`
Record the intended reader update, the current default view, and the strongest counter-position in a `Framing Intent` block. Allow framing to guide emphasis and argument order, but never let it bias evidence retrieval, omit material counterevidence, or turn a hypothesis into a fact.
Express each challenge as a causal requirement, not an adjective: property of the setting -> technical difficulty -> why generic methods fail -> capability the solution must provide.
### 3. Position against 3-5 anchor papers
Read [anchor-paper-positioning.md](references/anchor-paper-positioning.md). Select papers by role rather than fame: problem anchor, method anchor, closest competitor, experiment anchor, and optional writing/architecture anchor. A paper may fill more than one role.
Verify title, authors, year, venue or repository, and DOI or stable URL. Extract `WHY / HOW / WHAT / LIMIT / TRANSFER` for each paper. Compare task assumptions and evidence, not only module names. Derive high-level writing characteristics without copying distinctive wording.
### 4. Derive and attack the idea
Read [novelty-and-falsification.md](references/novelty-and-falsification.md). Consider three routes: a genuinely new problem, an old problem with an ignored condition or failure mode, or new evidence/understanding that changes a boundary. Force each candidate through:
`observed gap -> underlying cause -> design principle -> method component -> expected evidence`
Generate alternatives only when they help the user choose. Reduce the selected idea to one core hypothesis and 2-3 contribution cards. Attack it with the closest existing method, the simplest plausible baseline, alternative explanations, confounds, negative cases, and feasibility limits. In `guided` mode, run the reviewer-simulation questions from [interactive-heuristics.md](references/interactive-heuristics.md) before treating a contribution as stable.
**Checkpoint 2 — Positioning and Hypothesis:** Present the verified anchors, defensible gap, rejected alternatives, core hypothesis, and falsifier. In `guided` mode, obtain user confirmation before freezing the method architecture.
### 5. Design the method architecture and core figure
Read [framework-figure.md](references/framework-figure.md). Map every challenge to a design principle, every principle to a component or procedure, and every component to a claim and validation hook. Build an editable textual specification and a Mermaid draft using:
`context/input -> problem structure -> method components -> objective/constraints -> output -> evidence`
Keep the figure causal and selective. Do not add decorative modules merely to make the method look complex. If the user requests an actual `.pptx`, hand the approved figure specification to a presentation-generation workflow rather than making PowerPoint a hidden dependency of Ask, share a tip or report that it does not work. Sorted by what people marked helpful.
No posts yet. Be the first to ask or share.
Posts here are written by users, not the PopNx team.