Skill by ara.so — Daily 2026 Skills collection.
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionclui-cc-claude-overlayExecute the skills CLI command in your project's root directory to begin installation:
Fetches clui-cc-claude-overlay from aradotso/trending-skills and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate clui-cc-claude-overlay. Access via /clui-cc-claude-overlay in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Automate repetitive workflows and reduce manual effort
Example
Generate reports, summarize documents, draft communications
Save 3-5 hours per week on routine tasks
Learn new skills, understand complex topics, get expert guidance
Example
Explain concepts, provide examples, suggest learning resources
Accelerate learning and skill development by 2x
Enhance output quality through reviews, suggestions, and refinements
Example
Review drafts, suggest improvements, catch errors
Improve work quality by 30-40% with less effort
0
total installs
0
this week
22
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
22
stars
Skill by ara.so — Daily 2026 Skills collection.
Clui CC wraps the Claude Code CLI in a transparent, floating macOS overlay with multi-tab sessions, a permission approval UI (PreToolUse HTTP hooks), voice input via Whisper, conversation history, and a skills marketplace. It requires an authenticated claude CLI and runs entirely local — no telemetry or cloud dependency.
| Requirement | Minimum | Notes |
|---|---|---|
| macOS | 13+ | Overlay is macOS-only |
| Node.js | 18+ | LTS 20 or 22 recommended |
| Python | 3.10+ | Needs setuptools on 3.12+ |
| Claude Code CLI | any | Must be authenticated |
| Whisper CLI | any | For voice input |
# 1. Xcode CLI tools (native module compilation)
xcode-select --install
# 2. Node.js via Homebrew
brew install node
node --version # confirm ≥18
# 3. Python setuptools (required on Python 3.12+)
python3 -m pip install --upgrade pip setuptools
# 4. Claude Code CLI
npm install -g @anthropic-ai/claude-code
# 5. Authenticate Claude Code
claude
# 6. Whisper for voice input
brew install whisper-cli
git clone https://github.com/lcoutodemos/clui-cc.git
# Then open the clui-cc folder in Finder and double-click install-app.command
On first launch macOS may block the unsigned app — go to System Settings → Privacy & Security → Open Anyway.
git clone https://github.com/lcoutodemos/clui-cc.git
cd clui-cc
npm install
npm run dev # Hot-reloads renderer; restart for main-process changes
./commands/setup.command # Environment check + install deps
./commands/start.command # Build and launch from source
./commands/stop.command # Stop all Clui CC processes
npm run build # Production build (no packaging)
npm run dist # Package as macOS .app → release/
npm run doctor # Environment diagnostic
| Shortcut | Action |
|---|---|
⌥ + Space |
Show / hide the overlay |
Cmd + Shift + K |
Fallback toggle (if ⌥+Space is claimed) |
UI prompt → Main process spawns claude -p → NDJSON stream → live render
→ tool call? → permission UI → approve/deny
claude -p --output-format stream-json as a subprocess.RunManager parses NDJSON; EventNormalizer normalizes events.ControlPlane manages tab lifecycle: connecting → idle → running → completed/failed/dead.PermissionServer (localhost only).--resume <session-id>.src/
├── main/
│ ├── claude/ # ControlPlane, RunManager, EventNormalizer
│ ├── hooks/ # PermissionServer (PreToolUse HTTP hooks)
│ ├── marketplace/ # Plugin catalog fetch + install
│ ├── skills/ # Skill auto-installer
│ └── index.ts # Window creation, IPC handlers, tray
├── renderer/
│ ├── components/ # TabStrip, ConversationView, InputBar, …
│ ├── stores/ # Zustand session store
│ ├── hooks/ # Event listeners, health reconciliation
│ └── theme.ts # Dual palette + CSS custom properties
├── preload/ # Secure IPC bridge (window.clui API)
└── shared/ # Canonical types, IPC channel definitions
window.clui)The preload bridge exposes window.clui in the renderer. Key methods:
// Send a prompt to the active tab's claude process
window.clui.sendPrompt(tabId: string, text: string): Promise<void>
// Approve or deny a pending tool-use permission
window.clui.resolvePermission(requestId: string, approved: boolean): Promise<void>
// Create a new tab (spawns a new claude -p process)
window.clui.createTab(): Promise<{ tabId: string }>
// Resume a past session by id
window.clui.resumeSession(tabId: string, sessionId: string): Promise<void>
// Subscribe to normalized events from a tab
window.clui.onTabEvent(tabId: string, callback: (event: NormalizedEvent) => void): () => void
// Get conversation history list
window.clui.getHistory(): Promise<SessionMeta[]>
import { useEffect, useState } from 'react'
export function useClaudeTab() {
const [tabId, setTabId] = useState<string | null>(null)
const [messages, setMessages] = useState<NormalizedEvent[]>([])
useEffect(() => {
window.clui.createTab().then(({ tabId }) => {
setTabId(tabId)
const unsubscribe = window.clui.onTabEvent(tabId, (event) => {
setMessages((prev) => [...prev, event])
})
return unsubscribe
})
}, [])
const send = (text: string) => {
if (!tabId) return
window.clui.sendPrompt(tabId, text)
}
return { messages, send }
}
async function resumeLastSession() {
const history = await window.clui.getHistory()
if (history.length === 0) return
const { tabId } = await window.clui.createTab()
const lastSession = history[0] // most recent first
await window.clui.resumeSession(tabId, lastSession.sessionId)
}
Tool calls are intercepted by PermissionServer via PreToolUse HTTP hooks before execution. The renderer receives a permission_request event and must resolve it.
// Renderer: listen for permission requests
window.clui.onTabEvent(tabId, async (event) => {
if (event.type !== 'permission_request') return
const { requestId, toolName, toolInput } = event
// Show your approval UI, then:
const approved = await showApprovalDialog({ toolName, toolInput })
await window.clui.resolvePermission(requestId, approved)
})
// Main process: PermissionServer registers a hook with claude -p
Prerequisites
Time Estimate
15-45 minutes depending on use case complexity
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.
✗ Avoid when
Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.
JuliusBrussee/caveman
JuliusBrussee/caveman
whyashthakker/agent-skills-marketing
anthropics/claude-code
mblode/agent-skills
github/awesome-copilot
Registry listing for clui-cc-claude-overlay matched our evaluation — installs cleanly and behaves as described in the markdown.
clui-cc-claude-overlay is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
I recommend clui-cc-claude-overlay for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
clui-cc-claude-overlay reduced setup friction for our internal harness; good balance of opinion and flexibility.
Solid pick for teams standardizing on skills: clui-cc-claude-overlay is focused, and the summary matches what you get after install.
Keeps context tight: clui-cc-claude-overlay is the kind of skill you can hand to a new teammate without a long onboarding doc.
Keeps context tight: clui-cc-claude-overlay is the kind of skill you can hand to a new teammate without a long onboarding doc.
Registry listing for clui-cc-claude-overlay matched our evaluation — installs cleanly and behaves as described in the markdown.
clui-cc-claude-overlay has been reliable in day-to-day use. Documentation quality is above average for community skills.
clui-cc-claude-overlay reduced setup friction for our internal harness; good balance of opinion and flexibility.
showing 1-10 of 63