القائمة
USE WHEN: user wants to publish, port, or share a skill to a marketplace repo. DO NOT USE WHEN: creating new skills, installing skills, or general questions.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | publish-skill |
| description | USE WHEN: user wants to publish, port, or share a skill to a marketplace repo. DO NOT USE WHEN: creating new skills, installing skills, or general questions. |
| license | MIT |
Port skills from any project to the claude-hacks marketplace.
publish-skill <skill-name> [--source PATH] [--dry-run] [--no-push]
skills/<name>/skills/<name>/.claude-plugin/marketplace.jsonpublish-skill my-skill
publish-skill my-skill --source /path/to/.claude/skills/my-skill
publish-skill my-skill --dry-run
Verify SKILL.md has:
name: in frontmatterdescription: with USE WHEN / DO NOT USE WHENPROACTIVE skill - Claude invokes automatically when user messages exhibit anti-patterns. Detects recursive nesting, scope creep, buried asks, assumed context, stream dumps, imprecise descriptions. Disable with "coach off" or "raw mode".
Explains code, algorithms, system design using ASCII diagrams. Trigger phrases - "explain visually", "I don't get it", "show me", "ascii diagram", "help me understand". Produces diagram-first explanations ending with TL;DR tables.
USE WHEN: user requests generative art, algorithmic art, procedural visuals, flow fields, particle systems, creative coding, or says "create art", "generative", "p5.js". DO NOT USE WHEN: static images, traditional graphics, or non-generative visual work is requested. Creates original algorithmic art—never copies existing artists' work.
USE WHEN: analyzing existing architectures, evaluating architectural decisions, identifying technical debt, planning refactoring, assessing whether patterns are justified, onboarding to complex codebases, reviewing PRs with architectural changes. DO NOT USE WHEN: simple code questions, bug fixes, feature implementation, or tasks not requiring architectural analysis. For complex architectural analysis, trigger deep thinking with "think harder" or "ultrathink" to enable thorough first-principles reasoning.
USE WHEN: visualizing algorithms, data structures, architecture, control flow with ASCII art, or when terminal-friendly diagrams are needed. DO NOT USE WHEN: Mermaid diagrams are better suited, rich graphics are available, or simple text explanation suffices.
USE WHEN: needing real code examples from GitHub, finding API usage patterns, looking up framework setup, verifying library implementations, eliminating hallucinations with working code. DO NOT USE WHEN: working on proprietary code, questions about the current codebase, or when local context is sufficient. Requires Exa API key configured in environment.