AI & Machine Learninglearnprompt/luban-skill
luban
Luban - Skill Polishing Workshop. Transform a "usable Skill" into a public Skill asset that is "understandable, installable, shareable, verifiable, and continuously evolvable". The methodology consists of five craftsman-like steps:
1. Material Inspection: First challenge whether the premise of this Skill is valid; directly state if the "material" is not worth polishing.
2. Peer Research: Search for similar Skills online to clarify its position in the ecosystem.
3. Dimension Measurement: Evaluate using three metrics - structure, actual testing, and live verification (live verification means reconciling with real running outputs; a green CI can be deceptive).
4. Iterative Refinement: Freeze the original version as a baseline; only retain changes that pass the verification gate, otherwise revert. Try to institutionalize verification methods as tools and rules in the repository.
5. Post-Release Iteration: Release is not the end; maintain a benchmark observation list, and start the next iteration based on real feedback.
This tool is used when users want to upgrade, optimize, polish, productize, or release their self-developed Skills. The final deliverables include a structured Skill Polishing Report, directly replaceable rewritten segments, and a shareable "Graduation Certificate" result card that can be screenshot.
Trigger phrases include but are not limited to: "Let Luban take a look at this skill", "Polish at Luban's Workshop", "Polish my skill", "Upgrade my skill", "Optimize this skill", "Skill check-up", "Skill audit", "Productize my skill", "How to release this skill", "Benchmark against similar skills", "Why no one installs my skill", "Help me publish my skill to GitHub/ClawHub", "Improve SKILL.md".
Even if users only provide a Skill directory, GitHub repository link, or a segment of SKILL.md saying "Help me figure out how to modify it", it should be triggered as long as the context is about making the Skill more usable and shareable.
Do NOT use this for creating a new Skill from scratch (use skill-creator), regular code review (use code-review), or rewriting ordinary prompts unrelated to Skill assets.