brainstorming

Name: brainstorming
Author: sentient-agi

1.1kstars114forks

How to install brainstorming?

sentient-agi/evoskill/brainstorming

$npx -y skills add sentient-agi/EvoSkill --skill brainstorming

Installs into the current project.

Summary

IMMEDIATELY USE THIS SKILL before answering any task - internal design thinking that identifies the question type, selects applicable skills, and converges on the best approach before implementation

Files · 1

View on GitHub

SKILL.md

1	# Internal Design Thinking
2
3	## Overview
4
5	Structured self-dialogue before answering any question or task. Analyze what's being asked, identify which skills apply, reason through the approach, then execute.
6
7	Core principle: Think first, execute second. Map the question to the right skill chain before acting.
8
9	## The Process
10
11	### Phase 1: Question Classification
12
13	Analyze the question to determine:
14
15	- Domain: What subject area does this fall into?
16	- Data type: What kind of data or input is involved?
17	- Time scope: Single point, time series, comparison, or not applicable?
18	- Operation type: Raw lookup, calculation, transformation, generation, analysis?
19	- Output format: What form should the answer take (number, text, code, list, etc.)?
20	- Key terms: If the question uses a specific term or method, explicitly state its definition/formula BEFORE proceeding
21
22	### Phase 2: Skill Selection
23
24	Review available skills and determine which apply:
25
26	1. List all skills currently available in `.claude/skills/`
27	2. For each skill, check if it is relevant to the question's domain and operation type
28	3. If multiple skills apply, determine the order they should be chained
29
30	Skill chain reasoning:
31	- "This question requires [X], which maps to skill [Y]"
32	- "After [Y], I need to apply [Z] for the final transformation"
33	- "No existing skill covers [W] — proceed with general reasoning"
34
35	### Phase 3: Approach Design
36
37	For the selected skills, map out the execution path:
38
39	1. Data retrieval: Where does the relevant data live? What search patterns to use?
40	2. Transformations: What processing or conversions are needed?
41	3. Analysis: What computation, reasoning, or synthesis is required?
42	4. Formula verification (if applicable):
43	- Write out the exact formula to be used
44	- Verify it matches the standard definition of the term in the question
45	- Confirm units and dimensions are consistent throughout
46	5. Validation: How will you verify intermediate results are correct?
47	6. Output: What format does the question expect?
48
49	State assumptions explicitly:
50	- "Assuming [X] convention because..."
51	- "Interpreting [term] as [definition] because..."
52	- "Using [method] since the question specifies..."
53
54	### Phase 4: Design Summary
55
56	Before execution, articulate the plan:
57
58	```
59	## Analysis Plan
60
61	Question type: [classification]
62
63	Skills to apply:
64	1. [skill name] → [what it does for this question]
65	2. [skill name] → [what it does for this question]
66
67	Data sources: [where to find the relevant data]
68
69	Key steps:
70	1. [step]
71	2. [step]
72	...
73
74	Precision note (if applicable): [number of decimal places, rounding rules, etc.]
75
76	Assumptions: [list any]
77
78	Proceeding with execution.
79	```
80
81	### Phase 5: Execute
82
83	- Follow the plan from Phase 4
84	- Verify each intermediate result before proceeding to the next step
85	- Complete pre-output verification before stating final answer
86
87	### Phase 6: Pre-Output Verification (MANDATORY)
88
89	Before outputting, check:
90	1. Units/dimensions correct for the question type?
91	2. Value in reasonable range for the domain?
92	3. Computation fully completed (not partial)?
93	4. Answer addresses exactly what was asked?
94
95	If ANY check fails → re-verify inputs and reasoning.
96
97	## Remember
98
99	- This is internal reasoning — no questions, no waiting
100	- ALWAYS verify data extracted from files or tables before using it in calculations
101	- State assumptions so errors are traceable
102	- The goal is selecting the right approach, not documenting
103	- Once the plan is clear, execute immediately

People who liked this also viewed

6 picks

Type

find-skillsHelps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skSkillsJul 20262.6M27k
grill-meA relentless interview to sharpen a plan or design.SkillsJul 2026633k182k
vercel-react-best-practicesVercel's official collection of agent skillsSkillsJul 2026573k29k
improve-codebase-architectureScan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.SkillsJul 2026522k182k
setup-matt-pocock-skillsConfigure this repo for the engineering skills — set up its issue tracker, triage label vocabulary, and domain doc layout. Run once before first use of the other engineering skills.SkillsJul 2026454k182k
triageMove issues and external PRs through a state machine of triage roles — categorise, verify, grill if needed, and write agent-ready briefs.SkillsJul 2026424k182k

brainstorming

1.1kstars114forks

View on GitHub

How to install brainstorming?

sentient-agi/evoskill/brainstorming

$npx -y skills add sentient-agi/EvoSkill --skill brainstorming

Installs into the current project.

Summary

IMMEDIATELY USE THIS SKILL before answering any task - internal design thinking that identifies the question type, selects applicable skills, and converges on the best approach before implementation

Files · 1

View on GitHub

SKILL.md

1	# Internal Design Thinking
2
3	## Overview
4
5	Structured self-dialogue before answering any question or task. Analyze what's being asked, identify which skills apply, reason through the approach, then execute.
6
7	Core principle: Think first, execute second. Map the question to the right skill chain before acting.
8
9	## The Process
10
11	### Phase 1: Question Classification
12
13	Analyze the question to determine:
14
15	- Domain: What subject area does this fall into?
16	- Data type: What kind of data or input is involved?
17	- Time scope: Single point, time series, comparison, or not applicable?
18	- Operation type: Raw lookup, calculation, transformation, generation, analysis?
19	- Output format: What form should the answer take (number, text, code, list, etc.)?
20	- Key terms: If the question uses a specific term or method, explicitly state its definition/formula BEFORE proceeding
21
22	### Phase 2: Skill Selection
23
24	Review available skills and determine which apply:
25
26	1. List all skills currently available in `.claude/skills/`
27	2. For each skill, check if it is relevant to the question's domain and operation type
28	3. If multiple skills apply, determine the order they should be chained
29
30	Skill chain reasoning:
31	- "This question requires [X], which maps to skill [Y]"
32	- "After [Y], I need to apply [Z] for the final transformation"
33	- "No existing skill covers [W] — proceed with general reasoning"
34
35	### Phase 3: Approach Design
36
37	For the selected skills, map out the execution path:
38
39	1. Data retrieval: Where does the relevant data live? What search patterns to use?
40	2. Transformations: What processing or conversions are needed?
41	3. Analysis: What computation, reasoning, or synthesis is required?
42	4. Formula verification (if applicable):
43	- Write out the exact formula to be used
44	- Verify it matches the standard definition of the term in the question
45	- Confirm units and dimensions are consistent throughout
46	5. Validation: How will you verify intermediate results are correct?
47	6. Output: What format does the question expect?
48
49	State assumptions explicitly:
50	- "Assuming [X] convention because..."
51	- "Interpreting [term] as [definition] because..."
52	- "Using [method] since the question specifies..."
53
54	### Phase 4: Design Summary
55
56	Before execution, articulate the plan:
57
58	```
59	## Analysis Plan
60
61	Question type: [classification]
62
63	Skills to apply:
64	1. [skill name] → [what it does for this question]
65	2. [skill name] → [what it does for this question]
66
67	Data sources: [where to find the relevant data]
68
69	Key steps:
70	1. [step]
71	2. [step]
72	...
73
74	Precision note (if applicable): [number of decimal places, rounding rules, etc.]
75
76	Assumptions: [list any]
77
78	Proceeding with execution.
79	```
80
81	### Phase 5: Execute
82
83	- Follow the plan from Phase 4
84	- Verify each intermediate result before proceeding to the next step
85	- Complete pre-output verification before stating final answer
86
87	### Phase 6: Pre-Output Verification (MANDATORY)
88
89	Before outputting, check:
90	1. Units/dimensions correct for the question type?
91	2. Value in reasonable range for the domain?
92	3. Computation fully completed (not partial)?
93	4. Answer addresses exactly what was asked?
94
95	If ANY check fails → re-verify inputs and reasoning.
96
97	## Remember
98
99	- This is internal reasoning — no questions, no waiting
100	- ALWAYS verify data extracted from files or tables before using it in calculations
101	- State assumptions so errors are traceable
102	- The goal is selecting the right approach, not documenting
103	- Once the plan is clear, execute immediately

People who liked this also viewed

6 picks

Type