Bulletmind
When active, responses remain in hierarchical bullet format with no paragraphs, no prose blocks, no drift, and only structured bullet output.
When to Use This Skill
Transform input into a structured bullet hierarchy when the user asks for:
- Bullet-only summaries of dense text, notes, explanations, articles, or webpages
- Cleaned-up note-taking output with clear parent-child relationships
- Structured study material that is easier to scan and memorize
- Consistent formatting for messy or mixed bullet lists
Use this skill to enforce:
- No paragraphs or long prose
- Only bullets with clean indentation
This improves readability, memorization, and structured thinking for note-taking and review workflows.
Mode
Default mode: full. Switch with /bulletmind lite|full|ultra when the user asks for a different level of detail.
Intensity
| Level |
Behavior |
| lite |
clean hierarchical bullets, light restructuring, preserve sentence flow |
| full |
default strict hierarchy, balanced compression, clear grouping + splitting |
| ultra |
deep hierarchical decomposition, aggressive splitting, high granularity, maximal structural clarity |
Bullet Structure
Use consistent indentation:
- Top-level idea
- Next top-level idea
Rules
- NO paragraphs
- ONLY bullets
-
- ALWAYS hierarchical structure
- GROUP related ideas under parent bullets
- SPLIT long sentences into smaller bullets
- KEEP meaning intact, no over-summarize
- REMOVE filler words
Formatting
- Use
- for all bullets
- Indent: 2 spaces per level
- Keep bullets short
- One idea per line
- No mixed symbols and no prose bridging lines
Transformation Logic
- Paragraph -> main ideas -> top bullets
- Details -> nested bullets
- Messy notes -> cleaned hierarchy
- Existing bullets -> restructure + normalize depth
- Short input -> still convert into bullet tree
Compression Strategy
- Remove filler words
- Split complex sentences
- Preserve key facts + relationships
- Do NOT flatten structure
- Prefer clarity over max compression
When Not to Use This Skill
- User requests paragraphs
- Creative writing tasks such as stories or essays
- Formats where bullets reduce clarity or violate the requested output format
Output Rule
When the skill is active, output:
- Structured bullet hierarchy
- No commentary or explanation
Limitations
- Do not use for deliverables that require prose, narrative flow, or exact source quotation.
- Do not preserve bullet-only formatting if a higher-priority instruction requires tables, code blocks, JSON, or paragraphs.
- Do not invent structure beyond the source material when the user asks for faithful summarization.
Examples
- Refer to
EXAMPLES.md for output templates.
Important Notes
- Prefer clarity over strict compression
- Avoid flattening everything into one level
- Maintain a logical tree structure
1---2name: bulletmind3description: Convert input into clean, structured, hierarchical bullet points for summarization, note-taking, and structured thinking.4license: MIT5---6
7# Bulletmind
8
9When active, responses remain in hierarchical bullet format with no paragraphs, no prose blocks, no drift, and only structured bullet output.
10
11---
12
13## When to Use This Skill
14
15Transform input into a structured bullet hierarchy when the user asks for:
16
17- Bullet-only summaries of dense text, notes, explanations, articles, or webpages
18- Cleaned-up note-taking output with clear parent-child relationships
19- Structured study material that is easier to scan and memorize
20- Consistent formatting for messy or mixed bullet lists
21
22Use this skill to enforce:
23
24- No paragraphs or long prose
25- Only bullets with clean indentation
26
27This improves readability, memorization, and structured thinking for note-taking and review workflows.
28
29---
30
31## Mode
32
33Default mode: **full**. Switch with `/bulletmind lite|full|ultra` when the user asks for a different level of detail.
34
35---
36
37## Intensity
38
39| Level | Behavior |
40| ----- | --------------------------------------------------------------------------------------------------- |
41| lite | clean hierarchical bullets, light restructuring, preserve sentence flow |
42| full | default strict hierarchy, balanced compression, clear grouping + splitting |
43| ultra | deep hierarchical decomposition, aggressive splitting, high granularity, maximal structural clarity |
44
45---
46
47## Bullet Structure
48
49Use consistent indentation:
50- Top-level idea
51 - Sub-point
52 - Detail
53 - Sub-point
54- Next top-level idea
55 - Sub-point
56
57---
58
59## Rules
60
61- NO paragraphs
62- ONLY bullets `-`
63- ALWAYS hierarchical structure
64- GROUP related ideas under parent bullets
65- SPLIT long sentences into smaller bullets
66- KEEP meaning intact, no over-summarize
67- REMOVE filler words
68
69---
70
71## Formatting
72
73- Use `-` for all bullets
74- Indent: 2 spaces per level
75- Keep bullets short
76- One idea per line
77- No mixed symbols and no prose bridging lines
78
79---
80
81## Transformation Logic
82
83- Paragraph -> main ideas -> top bullets
84- Details -> nested bullets
85- Messy notes -> cleaned hierarchy
86- Existing bullets -> restructure + normalize depth
87- Short input -> still convert into bullet tree
88
89---
90
91## Compression Strategy
92
93- Remove filler words
94- Split complex sentences
95- Preserve key facts + relationships
96- Do NOT flatten structure
97- Prefer clarity over max compression
98
99---
100
101## When Not to Use This Skill
102
103- User requests paragraphs
104- Creative writing tasks such as stories or essays
105- Formats where bullets reduce clarity or violate the requested output format
106
107---
108
109## Output Rule
110
111When the skill is active, output:
112
113- Structured bullet hierarchy
114- No commentary or explanation
115
116## Limitations
117
118- Do not use for deliverables that require prose, narrative flow, or exact source quotation.
119- Do not preserve bullet-only formatting if a higher-priority instruction requires tables, code blocks, JSON, or paragraphs.
120- Do not invent structure beyond the source material when the user asks for faithful summarization.
121
122### Examples
123
124- Refer to `EXAMPLES.md` for output templates.
125
126---
127
128## Important Notes
129
130- Prefer clarity over strict compression
131- Avoid flattening everything into one level
132- Maintain a logical tree structure
nous-hermeshub