cci
- Repo stars 330
- License MIT
- Author repo claude-skill-registry
- Domain
- Data
- Author-declared agents
- No explicit declaration found; this is not inferred or tested compatibility
- Static check
- 94 / 100 · heuristic scan, not runtime safety proof
- Runtime evidence
- Not run; no isolated runtime test evidence is currently recorded
- Author / version / license
- @majiayu000 · MIT
- Token usage
- Lean
- Setup complexity
- Manual integration
- External API key
- Not required
- Operating systems
- Docker
- Runtime requirements
- Node.js · Docker
- Detected file/system behavior
-
- Read-only
- Write / modify
- Network behavior
- Local-only
- Install commands
- None (reference only)
Heads up: Tool permissions are not declared; actual access depends on the runtime.
# Claude Collective Intelligence (CCI) Skill
Search the shared knowledge base for existing solutions before solving problems from scratch.
## When to Use
- User asks about common programming problems
- User mentions "CCI", "knowledge base", or "collective intelligence"
- You're about to solve a problem that might have been solved before
- User wants to find what solutions exist for a topic
## How to Search
Use the CCI CLI to search the knowledge base:
```bash
# Set the CCI repo path
export CCI_REPO="$HOME/code/claude-collective-intelligence"
# Search for relevant entries
node "$CCI_REPO/src/search.js" "your search query"
# For verbose output (full solutions)
node "$CCI_REPO/src/search.js" -v "your search query"
# View stats
node "$CCI_REPO/src/search.js" --stats
# List recent entries
node "$CCI_REPO/src/search.js" --list 5
```
## Response Format
When you find relevant entries:
1. Summarize the most relevant solution found
2. Adapt it to the user's specific context
3. Credit the source (date and contributor if available)
4. Offer to show more results if available
When no entries match:
1. Let the user know you checked CCI but found no matches
2. Proceed to solve the problem normally
3. Suggest saving the solution to CCI when done
## Example Queries
- "search CCI for react hooks typescript"
- "check knowledge base for API authentication patterns"
- "find CCI entries about docker deployment"
## After Solving New Problems
Remind users they can save successful solutions:
"This solution worked! Would you like to save it to CCI for future reference? Just say 'save to CCI' and I'll help capture it."
To manually add an entry:
```bash
node "$CCI_REPO/bin/cci.js" add
```
Sections and files
Listed in source order.
sections -> When to Use → How to Search → Response Format → Example Queries → After Solving New Problems
terms -> Search the shared knowledge base for existing solutions before solving problems from scratch. · 1. Summarize the most relevant solution found 2. · 1. Let the user know you checked CCI but found no matches 2. · "This solution worked!
files/cmd -> HOME/code/claude-collective-intelligence · CCI_REPO/src/search.js · CCI_REPO/bin/cci.js
body sha256 -> d28a9fdead17
When to Use
User asks about common programming problems User mentions "CCI", "knowledge base", or "collective intelligence" You're about to solve a problem that might have been solved before User wants to find what solutions exist for a topic
How to Search
Use the CCI CLI to search the knowledge base:
Response Format
When you find relevant entries: Summarize the most relevant solution found Adapt it to the user's specific context Credit the source (date and contributor if available) Offer to show more results if available
Example Queries
"search CCI for react hooks typescript" "check knowledge base for API authentication patterns" "find CCI entries about docker deployment"
After Solving New Problems
Remind users they can save successful solutions: "This solution worked! Would you like to save it to CCI for future reference? Just say 'save to CCI' and I'll help capture it." To manually add an entry: