fluxly Search skills… ⌘K 中文 Publish

idea-generation

Engineering Verified
Fluxly profile Facts only: domain, agents, trust score, runtime, permissions and network
Domain
Engineering
Compatible agents
  • Claude Code
  • Cursor
  • Cline
  • Codex
  • Windsurf
  • Gemini CLI
  • +20
Trust score
94 / 100 · audit passed
Author / version / license
@voidful · MIT
Token usage
Lean
Setup complexity
Plug-and-play
External API key
Not required
Operating systems
Unspecified (assume cross-platform)
Runtime requirements
No special requirements
Permissions
  • Read-only
  • Write / modify
Network behavior
Local-only
Install commands
26 variants

Profile is derived at build time from SKILL.md and install vectors. Subject to drift from author intent.

Heads up: 未限定 allowed-tools，默认拥有全部工具权限。

Output preview idea-generation.preview 
---
name: idea-generation
description: 本技能提供一套系統化的研究構想產生流程，幫助研究者從零開始產出具備新穎性、可行性與影響力的研究 idea。流程分為三個階段：發散、文獻搜索驗證、收斂，最終產出一份精煉的 1-page 研究提案…
category: engineering
runtime: no special runtime
---

# idea-generation output preview

## PART A: Task fit
- Use case: 本技能提供一套系統化的研究構想產生流程，幫助研究者從零開始產出具備新穎性、可行性與影響力的研究 idea。流程分為三個階段：發散、文獻搜索驗證、收斂，最終產出一份精煉的 1-page 研究提案。 階段一：發散 階段二：文獻搜索驗證 階段三：收斂 ───────────── ───────────────── ────────── runs entirely locally. Works with Claude Code, Cursor, Cline and 23 more..
- Inputs: target material, constraints, expected output, and acceptance criteria.
- Evidence boundary: follow “概述 / 三階段流程 / 總覽” and do not present inference as author intent.

## PART B: Execution result
- **01** The card summarizes the use case; runtime output centers on “本技能提供一套系統化的研究構想產生流程，幫助研究者從零開始產出具備新穎性、可行性與影響力的研究 idea。流程分為三個階段：發散、文獻搜索驗證、收斂，最終產出一份精煉的 1-page 研究提案。 階段一：發散 階段二：文獻搜索驗證 階段三：收斂 ───────────── ───────────────── ────────── runs entirely locally. Works with Claude Code, Cursor, Cline and 23 more.”.
- **02** When the source has headings, the agent prioritizes “概述 / 三階段流程 / 總覽” so the result follows the author’s structure.
- **03** Typical output includes task judgment, concrete steps, required commands or file edits, validation, and follow-up options.
- **04** Risk context follows the fingerprint: read files, write/modify files; mostly runs locally; usually needs no extra API key.

## Running Rules
- read files, write/modify files; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding scope.
- Return the result, validation criteria, and next iteration options.
Interpretation is structured for decision-making; original keeps the upstream SKILL.md unchanged.

Decide Fit First

  • Core job: 本技能提供一套系統化的研究構想產生流程，幫助研究者從零開始產出具備新穎性、可行性與影響力的研究 idea。流程分為三個階段：發散、文獻搜索驗證、收斂，最終產出一份精煉的 1-page 研究提案。 階段一：發散 階段二：文獻搜索驗證 階段三：收斂 ─────…
  • Best fit: Use it when the task has reusable inputs, steps, and validation criteria rather than a one-off answer.
  • Avoid forcing it: If the source lacks commands, platform support, or external-service evidence, keep those fields unknown instead of guessing.

Design Intent

  • Structure: The skill is organized around “概述”, “三階段流程”, “總覽”, “階段一：發散 — 產生 10-20 個候選 Idea”, showing how the author expects the agent to judge fit, collect context, and produce verifiable output.
  • Trigger evidence: Prioritize the author’s wording around when to use it, what context to collect, and what output shape to produce.
  • Evidence boundary: Author text states facts, repository files prove commands and paths, and Fluxly only adds fit, limits, and usage judgment.

How To Use It

  • Inputs: Provide target material, scope, expected result, forbidden changes, and validation method.
  • Invocation: Name idea-generation directly; if the source includes slash commands, start with the command and then add task context.
  • Validation: Start small and check whether the result follows “概述 / 三階段流程 / 總覽” before expanding.

Boundaries And Review

  • Dependencies: It usually needs no extra API key, so start with a small validation task.
  • Permissions: Declared permissions include read / write; ask the agent to state file, command, and rollback boundaries before acting.
  • Quality bar: A useful result names the deliverable, evidence, and next action. Generic prose means the task needs tighter context.

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.