$ loading_
Turn rough ideas into actionable designs through structured questioning and validation.
This appears to be a prompt-only brainstorming skill with no required secrets, no declared remote endpoints, and no executable installation steps, so overall risk is low. The main caveat is provenance ambiguity: the skill name does not clearly match the provided GitHub repository, so its origin and maintenance should be verified before production use.
The material explicitly states that no keys or environment variables are required, and the README does not request login, API tokens, or other sensitive credentials; based on the provided facts, there is no direct credential collection, storage, or abuse surface.
No remote endpoints are declared, and the documentation does not describe sending user data to external services, syncing to the cloud, or calling third-party APIs; based on the material itself, it does not involve network egress.
This skill is marked as prompt-only, and the README mainly describes a conversational and design workflow, with no install scripts, shell commands, or executable code. Although it mentions switching to other skills later for worktree/plan steps, that is process guidance rather than code execution capability of this skill itself.
The document mentions checking the current project state in the working directory, but it provides no actual file read/write implementation, permission request, or automated access mechanism; as prompt-only material, its data access remains advisory and does not show factual overbroad authorization.
A positive factor is that it is labeled open source and hosted on GitHub, which is more auditable than closed-source material. However, the provided repository is microsoft/FluidFramework, which does not clearly match the 'brainstorming' skill name or content, and the metadata shows 0 stars with unknown maintenance status; this creates provenance ambiguity and insufficient maintenance visibility, so the true upstream should be verified.
Copy the install command and let the AI configure it · recommended for beginners
Please install the "brainstorming" skill from askskill: 1. Download https://raw.githubusercontent.com/microsoft/FluidFramework/main/.agency/plugins/nori/skills/brainstorming/SKILL.md 2. Save it as ~/.claude/skills/brainstorming/SKILL.md 3. Reload skills and tell me it's ready
Use the brainstorming skill now. I want to build a task board feature for small and midsize teams. Do not give the solution immediately. First, clarify target users, core scenarios, key constraints, and success metrics through step-by-step questions. After each round, summarize and propose 2-3 alternative directions, then produce an actionable feature design draft.
An actionable feature design draft with goals, constraints, alternatives, and a recommended direction.
Use the brainstorming skill now. Before I start coding, validate the requirements and technical approach for this log analysis tool through Socratic questioning, including inputs and outputs, performance requirements, edge cases, deployment environment, and testing strategy. If assumptions are incomplete, keep probing, then provide implementation priority recommendations.
A more complete implementation plan with clarified scope, risks, testing focus, and development priorities.
Use the brainstorming skill now. I want to conduct a study on remote work productivity. First, narrow the research question through iterative questions, identify variables, compare feasible methods, and validate whether the hypothesis is measurable, then compile a concise research design.
A focused research design including problem definition, variables, method choices, and testable hypotheses.
Transform rough ideas into fully-formed designs through structured questioning and alternative exploration.
Core principle: Ask questions to understand, explore alternatives, present design incrementally for validation.
Announce at start: "I'm using the Nori Brainstorming skill to refine your idea into a design."
When design is approved and implementation will follow:
Ask: "Ready to create the implementation plan?"
When your human partner confirms (any affirmative response):
You can and should go backward when:
Don't force forward linearly when going backward would give better results.
Explains how to use abilities effectively before starting any conversation.
Break large, long-running tasks into manageable chunks and preserve context.
Draft and review Fluid Framework PR titles and descriptions consistently.
Review code or branches for correctness, compatibility, architecture, tests, performance, and security.
Build, debug, and validate features in web app frontends.
Generate Fluid-style PR content, push branches, and open GitHub pull requests.
Clarify intent, requirements, and solution direction before any creative implementation work.
Brainstorm product ideas, explore problems, and challenge assumptions with an AI partner.
Plan with pseudocode first, refine approaches, then translate into working code.
Compare 2-3 approaches before execution to choose a stronger solution.
Clarify ambiguous plans and requirements through rigorous questioning and assumption testing.
Get high-signal second opinions on plans, designs, and implementations early.