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.
Si lo creaste tú, pega este código en tu README. La insignia enlaza a esta página.
[](https://mcp.popnx.com/en/skills/cpt13-g-clarify-research-idea)Servidores MCP que conectan la IA a servicios para el mismo trabajo
Gives AI development tools Firebase-specific capabilities and expertise.
MCP server for interacting with the Supabase platform
Query databases from AI agents using connections configured in DBX.
Mismo tipo de trabajo, ordenadas como la lista de Skills
| Este clarify-research-idea | timesfm | Shadowbroker | google-maps-scraper | tradingview-mcp | |
|---|---|---|---|---|---|
| Autor | cpt13-g | google-research | BigBodyCobain | gosom | atilaahmettaner |
| Skills | 1 | 1 | 1 | 1 | 1 |
| Estrellas de GitHub | 298 | 35.629 | 11.602 | 8209 | 5307 |
| Último cambio de código | 26 jul 2026 | 13 nov 2026 | 17 nov 2026 | 15 nov 2026 | 15 nov 2026 |
| Licencia | – | Apache-2.0 | AGPL-3.0 | MIT | MIT |
1 skills (conjuntos de instrucciones) de cpt13-g que la IA lee y sigue · no es un MCP server
MCP = las manos
Conecta la IA a un servicio o dato externo, como leer Notion o crear una factura. Necesita un programa o servidor en marcha.
Skill = el manual
Un archivo de texto que enseña a la IA cómo hacer una tarea. No se conecta a nada.
A veces se parecen: algunas Skills ejecutan scripts que llaman herramientas y algunos MCP solo envían conocimiento. Empieza por la tarea que quieres hacer.
Codex
Según el README del autor y las carpetas del repo
GitHub account cpt13-g (person), 5 years old
★ 298 stars, few users so far · code last changed 26 jul 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
Primero: ¿qué IA usas?
Elige tu app y esta página mostrará solo cómo instalarlo en ella
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 12 nov 2026 · Source: support.claude.com, support.claude.com, code.claude.com
Copia esta frase y pégala en un chat de Claude Code
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
Vuelve a abrir Claude Code y escribe /clarify-research-idea, o pide una tarea relacionada y Claude lo usará
Checked against official docs 12 nov 2026 · Source: code.claude.com
Un Skill son instrucciones que la IA seguirá. Lee los archivos antes de instalar e instala solo de autores de confianza.
Mac: pulsa Command+Espacio y escribe Terminal · Windows: el comando no funciona en PowerShell; usa «Que la IA lo instale» arriba
Descarga el repo a una carpeta temporal y copia solo las carpetas con SKILL.md
Revisando los comandos · los botones de copiar aparecen cuando pasan la revisión
La app de escritorio de ChatGPT incluye Codex, y Codex lee las skills de la carpeta ~/.agents/skills
Abre Codex en la app de escritorio de ChatGPT y pega esta frase en el 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
Coloca la carpeta clarify-research-idea en ~/.agents/skills/clarify-research-idea
~ es tu carpeta de inicio ($HOME)
Un Skill son instrucciones que la IA seguirá. Lee los archivos antes de instalar e instala solo de autores de confianza.
Mac: pulsa Command+Espacio y escribe Terminal · Windows: el comando no funciona en PowerShell; usa «Que la IA lo instale» arriba
Descarga el repo a una carpeta temporal y copia solo las carpetas con SKILL.md
Revisando los comandos · los botones de copiar aparecen cuando pasan la revisión
Checked against official docs 15 nov 2026 · Source: learn.chatgpt.com
Las skills que instalas tú no funcionan aquí; solo las que vienen con un plugin del directorio
Para usar esta skill con ChatGPT, usa la app de escritorio de ChatGPT como se indica arriba
Checked against official docs 15 nov 2026 · Source: learn.chatgpt.com
Copia esta frase y pégala en un chat de Codex · Sirve en Codex dentro de la app de escritorio de ChatGPT, en Codex CLI y en la extensión del IDE
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 detecta solo las skills recién instaladas; si una no aparece, reinicia Codex · Para usarla: en ChatGPT escribe @ y elige la skill · en Codex CLI o la extensión del IDE ejecuta /skills o escribe $ y el nombre de la skill
Checked against official docs 15 nov 2026 · Source: learn.chatgpt.com
Un Skill son instrucciones que la IA seguirá. Lee los archivos antes de instalar e instala solo de autores de confianza.
Mac: pulsa Command+Espacio y escribe Terminal · Windows: el comando no funciona en PowerShell; usa «Que la IA lo instale» arriba
Descarga el repo a una carpeta temporal y copia solo las carpetas con SKILL.md
Revisando los comandos · los botones de copiar aparecen cuando pasan la revisión
Copia esta frase y pégala en un chat de Cursor
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
En el chat Agent de Cursor escribe / y elige clarify-research-idea
Checked against official docs 12 nov 2026 · Source: cursor.com
Un Skill son instrucciones que la IA seguirá. Lee los archivos antes de instalar e instala solo de autores de confianza.
Mac: pulsa Command+Espacio y escribe Terminal · Windows: el comando no funciona en PowerShell; usa «Que la IA lo instale» arriba
Descarga el repo a una carpeta temporal y copia solo las carpetas con SKILL.md
Revisando los comandos · los botones de copiar aparecen cuando pasan la revisión
Para otras apps que leen skills. La frase incluye las rutas de Claude Code, Codex y Cursor para que la IA elija la de tu 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 12 nov 2026 · Source: code.claude.com, learn.chatgpt.com, cursor.com
Otras apps con Agent Skills (como Gemini CLI o GitHub Copilot) usan otras carpetas. Mira la guía de esa app y copia allí la carpeta con el SKILL.md.
Carpetas de skills comprobadas con las guías oficiales de Claude Code, Codex y Cursor el 11 nov 2026
El texto siguiente viene del repo del autor, no de PopNx MCP
Se muestran los primeros 8000 caracteres · Abrir el archivo completo en 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 Pregunta, comparte un consejo o avisa de que no funciona. Ordenado por lo que la gente marcó como útil.
Aún no hay publicaciones. Sé la primera persona en preguntar o compartir.
Lo publicado aquí lo escriben usuarios, no el equipo de PopNx.