YuriNachosYuriNachos/claude-scope/.claude/skills/scope/SKILL.md

scope

Skill9 starsChanged 10 months agoMITView on GitHub

Configure claude-scope status line widgets for Claude Code. Use when user wants to customize widgets, change theme, reorder elements, or modify display style.

We split this skill into the rules it gives an agent

12 rules. 0 are common, 6 are distinctive, and 6 are very specific to this project.

0
Common
Most of the 35 edited versions we read keep these.
6
Distinctive
This author's own choices. Worth a look.
6
Very specific
Tied to their project's names, files or tools. Probably skip.

Common
Distinctive
Very specific

Distinctive:
Read config, change the order of widget objects in the line's array.
line 90
Very specific:
Add a widget object to the target line array.
line 108
Distinctive:
Example: Add docker widget to line 2:
line 110
Distinctive:
Remove the widget object from the line array.
line 117
Distinctive:
Remove widget object from source line
line 121
Distinctive:
Add widget object to target line
line 122
Very specific:
Update the "theme" field value.
line 126
Very specific:
Update the "style" field for the target widget.
line 137
Very specific:
Update "style" field for every widget in config to the same value.
line 141
Very specific:
Preserve required fields: - keep version and $aiDocs fields
line 155
Very specific:
Empty lines must be []: - don't remove line keys, use empty arrays
line 156
Distinctive:
Use existing colors as template: - when adding widgets, copy colors from similar existing widgets
line 158

“Common” is measured: kept by at least 6 in 10 of the 35 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.

Files

SKILL.md

Claude Scope Configuration Skill

Help users configure their claude-scope status line widgets.

Configuration Path

Config file: ~/.claude-scope/config.json

Workflow

Read current config from ~/.claude-scope/config.json
Understand what the user wants to change
Edit the config using the Edit tool
Confirm changes to the user

Changes apply automatically on the next status line render cycle.

Quick Reference

Config Structure

{
  "version": "1.0.0",
  "theme": "monokai",
  "lines": {
    "0": [{ "id": "model", "style": "balanced", "colors": {...} }],
    "1": [{ "id": "git", "style": "balanced", "colors": {...} }]
  }
}

lines is an object where keys are line numbers ("0", "1", "2", etc.)
Each line contains an array of widget configurations
Widgets render left-to-right within each line
Empty lines should be empty arrays []

Available Widgets (16)

Widget ID	Description	Typical Line
`cwd`	Current working directory	0
`model`	Claude model name (e.g., "Claude Opus 4.5")	0
`context`	Context window usage with progress bar	0
`cost`	Session cost in USD	0
`duration`	Session elapsed time	0
`lines`	Lines added/removed during session	0
`git`	Current git branch and changes	1
`git-tag`	Latest git tag	1
`config-count`	CLAUDE.md, rules, MCPs, hooks counts	1
`cache-metrics`	Cache hit rate and cost savings	1
`active-tools`	Running and completed Claude tools	2
`dev-server`	Dev server status (Nuxt, Next, Vite)	2
`docker`	Docker container count and status	2
`sysmon`	System metrics (CPU, RAM, Disk, Network)	3
`poker`	Random poker hand (easter egg)	4
`empty-line`	Blank separator line	any

Available Themes (17)

monokai (default), nord, dracula, catppuccin-mocha, tokyo-night, vscode-dark-plus, github-dark-dimmed, dusty-sage, muted-gray, slate-blue, professional-blue, rose-pine, semantic-classic, solarized-dark, one-dark-pro, cyberpunk-neon, gray

Available Styles

Style	Description
`balanced`	Clean, balanced with labels (default)
`compact`	Minimal, condensed
`playful`	Fun with emojis
`verbose`	Full text labels
`technical`	Raw values, no formatting
`labeled`	Explicit prefix labels
`minimal`	Most compact, no labels

Common Operations

Swap widgets within a line

Read config, change the order of widget objects in the line's array.

Example: Swap model and context on line 0:

// Before
"0": [{ "id": "model", ... }, { "id": "context", ... }]
// After
"0": [{ "id": "context", ... }, { "id": "model", ... }]

Swap entire lines

Exchange the arrays between two line keys.

Example: Swap line 0 and line 1 contents.

Add a widget

Add a widget object to the target line array. Use existing widgets in config as template for the colors field.

Example: Add docker widget to line 2:

{ "id": "docker", "style": "balanced", "colors": { "label": "...", "count": "...", "running": "...", "stopped": "..." } }

Remove a widget

Remove the widget object from the line array. Don't leave empty objects.

Move widget to different line

Remove widget object from source line
Add widget object to target line

Change theme

Update the "theme" field value.

Important: Changing theme also requires updating all colors fields in every widget. Recommendation: For full theme changes, suggest user run:

npx claude-scope quick-config

This provides an interactive menu with live preview.

Change widget style

Update the "style" field for the target widget.

Change all styles at once

Update "style" field for every widget in config to the same value.

Full Documentation

For detailed information about widgets, styles, colors, and themes, read the full documentation:

Main reference: AI-CONFIG-GUIDE.md in claude-scope repository
All widgets with examples: docs/WIDGETS.md
Theme system: docs/THEME-SYSTEM.md
Architecture: docs/ARCHITECTURE.md

Important Rules

Never break JSON structure - validate before saving
Preserve required fields - keep version and $aiDocs fields
Empty lines must be [] - don't remove line keys, use empty arrays
ANSI color format - colors use \u001b[38;2;R;G;Bm escape codes
Use existing colors as template - when adding widgets, copy colors from similar existing widgets

Example User Requests

User says	Action
"Swap first and second line"	Exchange lines "0" and "1" arrays
"Add docker widget"	Add docker widget to appropriate line
"Remove cost widget"	Remove cost widget from its line
"Make everything compact"	Change all widget styles to "compact"
"Use Dracula theme"	Update theme field (suggest quick-config for colors)
"Move git to first line"	Remove git from current line, add to line 0
"Show current config"	Read and display the config file

Download now (ZIP)

Other versions38 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 38
jsmastery-pro/skills★ 1.4ksame name
suboss87/FDEOps★ 940same name
AlexZio00/sovereign-skills★ 149same name
crisandrews/ClawCode★ 64same name
raphaelsalaja/skills★ 46same name
Dan-Cleary/fdestack★ 40same name
jack4world/auditstack★ 9same name
klmiing1229-a11y/Vague_Goal_To_Clear_Plan★ 3same name
WhorideChicken/first-playable★ 3same name
envisioning/skills★ 2same name
28 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
Used alongsideProjects with it also use develop, visual and 10 more.
Other files people use alongside this one.
- hong9LeeSkill
  develop
  빌드, 아키텍처, git 관련 작업 시 OMS MSA 공통 인프라 규칙을 적용한다. 기술 스택, 빌드 명령, 헥사고날 아키텍처 구조, git 워크플로우, AI Context 동기화 규칙을 다룬다. 코드 작성 컨벤션은 /convention, 테스트 컨벤션은 /test-guide 스킬을 참조.
  Also in 6 projects that use this
- minhtran3124Skill
  visual
  Skill graph visualizer — scans all SKILL.md files in skills/, builds a directed relationship graph from explicit `relationships` frontmatter (falling back to content inference), and generates both a Mermaid markdown summary and an interactive HTML graph at .docs/skill-graph.html. Trigger: /visual
  Also in 3 projects that use this
- MicrosoftSkill
  sync
  Sync the current session branch with its upstream branch, or publish the current session branch to a remote. Use when the user asks to sync a branch, pull latest changes, rebase onto upstream, push current branch, publish branch, or set upstream.
  Also in 7 projects that use this
- nicolasestremSkill
  document
  Create focused documentation for specific components or features
  Also in 5 projects that use this
- kt057Skill
  check
  lint, typecheck, test を一括実行して結果をサマリーする
  Also in 5 projects that use this
- Harut8Skill
  architect
  Also in 8 projects that use this
In this repositoryOne other file it gives its agents.
- CLAUDE.mdCLAUDE.md

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

It worked
Partly
It didn't

What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free