When to use this skill
- Building a backlog of CLI tools to package into reusable skills
- Running recurring surveys that must include CLI open-source candidates
- Comparing candidate repos by maintenance and licensing risk
- Preparing PR-ready evidence for new proposal vs improvement proposal decisions
Instructions
Step 1: Build candidate pool from search evidence
- Run keyword searches and save direct links to result pages.
- Collect at least 3 CLI repositories per run.
- Keep a provenance note for each candidate:
- direct page retrieval
- browser-rendered search result
- API metadata lookup
Step 2: Enrich each candidate with repository facts
For each candidate, collect:
- Repository URL
- SPDX license (or
NOASSERTION) - Last pushed timestamp
- Archived status
- Star/fork signal (for rough adoption only)
Minimum quality baseline:
- Must be non-archived
- Must have a clear license (avoid unknown for immediate packaging)
- Should show recent maintenance activity
Step 3: Classify as new proposal or improvement proposal
- If the concept is already covered by an existing skill path, classify as improvement proposal.
- If no equivalent skill exists, classify as new proposal.
- Always include rationale and the existing path checked for overlap.
Step 4: Score risk explicitly
Use this risk taxonomy:
- Low: active + licensed + clear docs
- Medium: active but limited adoption or narrower scope
- High: archived, unclear license, stale maintenance, or unstable API
Step 5: Produce PR-ready output
For each shortlisted candidate include:
- Why this candidate matters now
- Evidence links
- Suggested target path (new skill or existing skill to patch)
- Risk notes and blockers
Output format
## CLI OSS 후보
| Name | Link | License | Updated | Risk | 분류 |
|------|------|---------|---------|------|------|
| ... | ... | ... | ... | ... | 신규안/개선안 |
## 적용 제안
1. ...
2. ...
3. ...
Best practices
- Prefer maintainability over novelty.
- Treat unclear license as a blocker for immediate merge.
- Keep proposals link-backed; no unsupported claims.
- Separate discovery notes from implementation changes.
References
- https://github.com/search
- https://docs.github.com/en/rest/repos/repos#get-a-repository
- references/quality-gate.md