using-superpowers
Use when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions
Security Assessment
About using-superpowers
The 'using-superpowers' skill is a procedural skill that ensures the invocation of relevant skills at the start of any conversation. It is designed to streamline the process of determining whether any skill applies to a task before providing a response, including clarifications. This skill effectively eliminates the chance of bypassing essential steps or misusing tools by prompting users to check for skills, ensuring that tasks are approached with the right framework from the outset. It helps maintain focus, discipline, and consistency in the way tasks are handled, even in simple or seemingly insignificant situations.
The core feature of the skill is its emphasis on checking for applicable skills before any action is taken. This includes not only the task-related response but also any clarifying questions. The skill follows a flowchart that guides the process, from checking for relevant skills to invoking the skill tool, announcing the use of the skill, and executing the steps. It also integrates with BD (Business Development) tools to create task checklists, ensuring that all aspects of the task are covered. Users are prompted to follow the skill exactly when a checklist is involved, maintaining structured progress tracking.
This skill is intended for developers, project managers, or anyone who frequently interacts with various tools and frameworks. It is especially useful in environments where tasks require methodical and disciplined approaches, such as software development, debugging, and implementation planning. The skill helps users avoid rushing into tasks without proper context, ensuring they are equipped with the right tools and methodologies before proceeding.
FAQ
How do I know if I need to use this skill?
If there is even a 1% chance that a skill could apply to your task, you must invoke the skill. This includes not only task-related responses but also clarifying questions.
What happens if multiple skills apply?
Skills should be prioritized. Process skills (e.g., brainstorming, debugging) should be invoked first, followed by implementation skills (e.g., frontend design, mcp-builder).
Can I skip the skill invocation for simple tasks?
No, even simple tasks should go through the skill invocation process. This ensures that the correct approach is followed, regardless of the task complexity.
What if there are checklist items in the skill?
When a checklist is present, you need to create BD issues to track the progress of each task. Follow the checklist exactly to ensure that all steps are covered.
Are there any tasks that don't require skill invocation?
No, the skill invocation process is mandatory for all tasks, no matter how simple they might seem.
Install using-superpowers
Quick Setup:
- Copy the skill folder to
.claude/skills/ - Claude will automatically detect and use the skill
Repository
Trevoke/org-gtd.el