feat: Add skills-search skill for CCPM registry

- Add skills-search v1.0.0: Search, discover, install, and manage Claude Code skills from CCPM registry
- Track docs-cleaner skill that was already in marketplace.json
- Update marketplace version from 1.15.0 to 1.16.0
- Update skill count from 22 to 23 across all documentation
- Add skills-search section to README.md and README.zh-CN.md
- Add CCPM CLI to requirements section
- Add use case section for skill discovery & management

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
This commit is contained in:
daymade
2025-12-11 20:53:31 +08:00
parent d0042ffc7a
commit b1a21dc05b
10 changed files with 482 additions and 11 deletions

View File

@@ -0,0 +1,4 @@
Security scan passed
Scanned at: 2025-12-01T19:34:07.888071
Tool: gitleaks + pattern-based validation
Content hash: 05162f259948be068f6d59cf0c66cf9971eb7b2fce92c8485b8332c80e440b49

84
docs-cleaner/SKILL.md Normal file
View File

@@ -0,0 +1,84 @@
---
name: docs-cleaner
description: Consolidates redundant documentation while preserving all valuable content. This skill should be used when users want to clean up documentation bloat, merge redundant docs, reduce documentation sprawl, or consolidate multiple files covering the same topic. Triggers include "clean up docs", "consolidate documentation", "too many doc files", "merge these docs", or when documentation exceeds 500 lines across multiple files covering similar topics.
---
# Documentation Cleaner
Consolidate redundant documentation while preserving 100% of valuable content.
## Core Principle
**Critical evaluation before deletion.** Never blindly delete. Analyze each section's unique value before proposing removal. The goal is reduction without information loss.
## Workflow
### Phase 1: Discovery
1. Identify all documentation files covering the topic
2. Count total lines across files
3. Map content overlap between documents
### Phase 2: Value Analysis
For each document, create a section-by-section analysis table:
| Section | Lines | Value | Reason |
|---------|-------|-------|--------|
| API Reference | 25 | Keep | Unique endpoint documentation |
| Setup Steps | 40 | Condense | Verbose but essential |
| Test Results | 30 | Delete | One-time record, not reference |
Value categories:
- **Keep**: Unique, essential, frequently referenced
- **Condense**: Valuable but verbose
- **Delete**: Duplicate, one-time, self-evident, outdated
See `references/value_analysis_template.md` for detailed criteria.
### Phase 3: Consolidation Plan
Propose target structure:
```
Before: 726 lines (3 files, high redundancy)
After: ~100 lines (1 file + reference in CLAUDE.md)
Reduction: 86%
Value preserved: 100%
```
### Phase 4: Execution
1. Create consolidated document with all valuable content
2. Delete redundant source files
3. Update references (CLAUDE.md, README, imports)
4. Verify no broken links
## Value Preservation Checklist
Before finalizing, confirm preservation of:
- [ ] Essential procedures (setup, configuration)
- [ ] Key constraints and gotchas
- [ ] Troubleshooting guides
- [ ] Technical debt / roadmap items
- [ ] External links and references
- [ ] Debug tips and code snippets
## Anti-Patterns
| Pattern | Problem | Solution |
|---------|---------|----------|
| Blind deletion | Loses valuable information | Section-by-section analysis first |
| Keeping everything | No reduction achieved | Apply value criteria strictly |
| Multiple sources of truth | Future divergence | Single authoritative location |
| Orphaned references | Broken links | Update all references after consolidation |
## Output Artifacts
A successful cleanup produces:
1. **Consolidated document** - Single source of truth
2. **Value analysis** - Section-by-section justification
3. **Before/after metrics** - Lines reduced, value preserved
4. **Updated references** - CLAUDE.md or README with pointer to new location

View File

@@ -0,0 +1,50 @@
# Value Analysis Template
Use this template for section-by-section documentation analysis.
## Document Analysis Table
| Section | Lines | Value | Reason |
|---------|-------|-------|--------|
| Example Section | 25 | Keep | Contains unique troubleshooting steps not documented elsewhere |
| Another Section | 40 | Delete | Duplicates content in CLAUDE.md |
| Technical Details | 60 | Condense | Valuable but verbose; can be reduced to 15 lines |
| Setup Instructions | 30 | Keep | Essential for onboarding |
## Value Categories
### Keep (Green)
- Unique information not found elsewhere
- Essential procedures (setup, troubleshooting, constraints)
- Frequently referenced content
- Technical debt / roadmap items
### Condense (Yellow)
- Valuable but overly verbose
- Contains redundant examples
- Can be expressed more concisely
### Delete (Red)
- Duplicates existing documentation
- One-time records (test results, meeting notes)
- Self-evident information (code already documents this)
- Outdated or superseded content
## Consolidation Checklist
Before proposing deletions:
- [ ] Identified ALL files containing related content
- [ ] Mapped overlap between documents
- [ ] Listed unique value in each document
- [ ] Proposed single source of truth location
- [ ] Planned reference updates (CLAUDE.md, README, etc.)
## Output Format
After analysis, produce:
1. **Value Analysis Table** - Per-section breakdown with keep/condense/delete
2. **Consolidation Plan** - Target structure with line count estimates
3. **Before/After Comparison** - Total lines and percentage reduction
4. **Preserved Value Checklist** - Confirm all valuable content retained