asadullah48/hackathon-superpowers

Overview

This skill, example-skill, provides compact command and code patterns to solve common shell and scripting tasks, plus guidance on what to avoid. Use trigger keywords like "example", "pattern", or "fix" when asking for quick, practical snippets and troubleshooting steps. It is designed for developers who want ready-to-run examples and clear explanations.

How this skill works

The skill inspects the intent expressed by the user and returns concise shell or small code patterns plus an explanation of why they work. It highlights correct usage, anti-patterns to avoid, and short fixes for common problems. Responses focus on actionable commands, minimal examples, and rationale so you can copy, test, and adapt quickly.

When to use it

• When a user mentions keywords like "example", "pattern", or "fix" and needs a concrete shell snippet
• When a user asks to run or construct a simple command or small script
• When the user needs a quick explanation of why a pattern works
• When troubleshooting common shell mistakes or unsafe commands
• When the user wants best-practice guidance for small scripting tasks

Best practices

• Show minimal, runnable examples that are safe to test locally
• Explain the rationale in one or two sentences so readers understand trade-offs
• Highlight anti-patterns explicitly and provide safe alternatives
• Prefer portable shell constructs and note when a tool is system-specific
• Include one-liner fixes for common issues when applicable

Example use cases

• Provide a short echo or file-manipulation example when asked "show me an example"
• Offer a safe alternative when a user suggests a dangerous command like recursive deletes
• Supply a small TypeScript or shell snippet to illustrate an API or CLI pattern
• Diagnose a reported error and give a concise command to reproduce or fix it
• Recommend a related skill when the problem scope goes beyond a short example