✨ Add openclaw-skills-visualizer to Ecosystem Tools#477
✨ Add openclaw-skills-visualizer to Ecosystem Tools#477jingchang0623-crypto wants to merge 1 commit into
Conversation
Add the OpenClaw Skills Dependency Visualizer to the Development & Analysis Tools section. Features: - Smart dependency scanning for OpenClaw Skills - Multi-format output (text, JSON, DOT/Graphviz, ASCII art) - Zero-config startup, lightweight bash tool - Generate visual dependency graphs for documentation Links: - GitHub: https://github.com/jingchang0623-crypto/openclaw-skills-visualizer - Website: https://miaoquai.com (295+ AI terms, 484+ tutorials) 🦞 Helps developers understand and manage complex Skills ecosystems
📝 WalkthroughWalkthroughThis PR adds documentation for the OpenClaw Skills Dependency Visualizer tool. A new "Development & Analysis Tools" subsection is introduced in the README under ecosystem tools, featuring the visualizer project with links to its GitHub repository and website, a badge, concise feature descriptions, and a ready-to-use command example. ChangesDocumentation & Ecosystem Tools
Possibly related PRs
Suggested labels
Poem
🎯 1 (Trivial) | ⏱️ ~5 minutes 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment Warning |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@README.md`:
- Around line 87-109: The README entry links to a personal repo that violates
the CONTRIBUTING.md rule requiring skills to be in github.com/openclaw/skills;
remove or replace the "OpenClaw Skills Dependency Visualizer" entry (and its
links to https://github.com/jingchang0623-crypto/openclaw-skills-visualizer and
https://miaoquai.com) with either (a) a note linking only to an approved
repository under github.com/openclaw/skills, or (b) an explicit,
policy-compliant: "third-party tool" section that clearly states this is an
external tool (not a published skill) and documents that maintainers should
review its scripts (skills-visualizer.sh, test.sh) for safety before use; also
add a brief action item to validate the tool’s behavior (smart dependency
scanning/output modes) and the author identity against existing index entries.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
| ### 🛠️ Development & Analysis Tools | ||
|
|
||
| **OpenClaw Skills Dependency Visualizer** 🦞 | ||
| [🔗 GitHub](https://github.com/jingchang0623-crypto/openclaw-skills-visualizer) | [🌐 miaoquai.com](https://miaoquai.com) | ||
|
|
||
|  | ||
|
|
||
| Lightweight bash tool to visualize dependencies between OpenClaw Skills. Supports multiple output formats (text, JSON, DOT/Graphviz, ASCII art). | ||
|
|
||
| **Features:** | ||
| - 🔍 Smart dependency scanning | ||
| - 📊 Multi-format output (text/json/dot/ascii) | ||
| - 🎨 Generate Graphviz graphs for documentation | ||
| - 🚀 Zero-config startup | ||
|
|
||
| ```bash | ||
| # Quick start | ||
| git clone https://github.com/jingchang0623-crypto/openclaw-skills-visualizer.git | ||
| cd openclaw-skills-visualizer | ||
| ./skills-visualizer.sh /path/to/skills json report.json | ||
| ``` | ||
|
|
||
| --- |
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
# Verify the GitHub repository exists and contains the claimed tool
echo "=== Checking GitHub repository ==="
gh repo view jingchang0623-crypto/openclaw-skills-visualizer --json name,description,createdAt,pushedAt,isArchived,isFork 2>&1 || echo "Repository not found or inaccessible"
echo -e "\n=== Checking for bash script file ==="
gh api repos/jingchang0623-crypto/openclaw-skills-visualizer/contents 2>&1 | jq -r '.[].name' | grep -E '\.(sh|bash)$' || echo "No bash scripts found"
echo -e "\n=== Checking repository README ==="
gh repo view jingchang0623-crypto/openclaw-skills-visualizer --json readme -q .readme 2>&1 | head -50
echo -e "\n=== Checking website accessibility ==="
curl -s -o /dev/null -w "HTTP Status: %{http_code}\n" https://miaoquai.com 2>&1 || echo "Website not accessible"
echo -e "\n=== Searching for similar username patterns in this repo ==="
gh pr list --repo VoltAgent/awesome-openclaw-skills --state all --json author --jq '.[].author.login' | grep -E '^[a-z]+[0-9]+-crypto$' | sort | uniq -c || echo "No similar patterns found"Repository: VoltAgent/awesome-openclaw-skills
Length of output: 1446
🌐 Web query:
awesome-openclaw-skills repository contribution guidelines personal repositories
💡 Result:
awesome-openclaw-skills repository contribution guidelines (personal repositories) If you want to contribute to the awesome-openclaw-skills “awesome list” repos, the guidelines say you should NOT submit skills that live in personal repositories. Instead, you must add only skills that are already published in the official OpenClaw skills repository. 1) Where the skill must be published (no personal repos) - The repo’s CONTRIBUTING.md states that every skill listed “must already be published” in the official OpenClaw skills repo, and explicitly says the maintainers do not accept skills hosted elsewhere—“no personal repos, no gists, no external links.” [1][2][3] 2) What you need to do before submitting a PR - Publish your skill to the official OpenClaw skills repo first, then submit a PR to add the link to the awesome-openclaw-skills list. [1][2] 3) How to add it once it exists in the official skills repo - Add your entry to the relevant category at the end of that section in README.md (or suggest a new category if nothing fits). [1][2] 4) Additional quality constraints mentioned in CONTRIBUTING.md - The skill must have documentation (a SKILL.md). [1][2] - The description should be concise (10 words or fewer), and skills should have “real community usage” (brand new skills aren’t accepted). [1][2] Note: these rules apply to what gets included in the awesome-openclaw-skills index; OpenClaw itself supports local/managed/workspace skills directories for your own usage, but those are different from what the index repo will list. [4][5]
Citations:
- 1: https://github.com/natan89/awesome-openclaw-skills/blob/main/CONTRIBUTING.md
- 2: https://github.com/VoltAgent/awesome-openclaw-skills/blob/main/CONTRIBUTING.md
- 3: https://github.com/VoltAgent/awesome-openclaw-skills
- 4: https://docs.openclaw.ai/tools/skills
- 5: https://github.com/openclaw/openclaw/blob/9098e948/docs/tools/skills.md
Major: README entry links to a personal repo that conflicts with CONTRIBUTING policy
- CONTRIBUTING.md for
awesome-openclaw-skillsrequires skills be already published ingithub.com/openclaw/skillsand explicitly rejects personal repos/external sources; this entry links tohttps://github.com/jingchang0623-crypto/openclaw-skills-visualizer. - Link reachability looks OK: the GitHub repo exists and includes
skills-visualizer.sh(andtest.sh), andhttps://miaoquai.comreturns HTTP 200. - Still needs follow-up: validate the script’s actual “smart dependency scanning” + output modes, and review the bash script for safe behavior (no execution of arbitrary/untrusted code). Also review the author pattern (
jingchang0623-crypto)—there are multiple matching entries in the index repo.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@README.md` around lines 87 - 109, The README entry links to a personal repo
that violates the CONTRIBUTING.md rule requiring skills to be in
github.com/openclaw/skills; remove or replace the "OpenClaw Skills Dependency
Visualizer" entry (and its links to
https://github.com/jingchang0623-crypto/openclaw-skills-visualizer and
https://miaoquai.com) with either (a) a note linking only to an approved
repository under github.com/openclaw/skills, or (b) an explicit,
policy-compliant: "third-party tool" section that clearly states this is an
external tool (not a published skill) and documents that maintainers should
review its scripts (skills-visualizer.sh, test.sh) for safety before use; also
add a brief action item to validate the tool’s behavior (smart dependency
scanning/output modes) and the author identity against existing index entries.
1 participant
🛠️ Description
Add the OpenClaw Skills Dependency Visualizer to the Development & Analysis Tools section of Ecosystem Tools.
🎯 Features
🔗 Links
📸 Example Output
✅ Checklist
🦞 Why This Matters
As the OpenClaw Skills ecosystem grows (5,400+ skills!), developers need tools to understand dependencies and avoid conflicts. This visualizer helps:
Made with ❤️ by 妙趣AI 🦞
Summary by CodeRabbit