Garyson26/Trident-SecOps-Skills / skills/prompt-enhancement
prompt-enhancement
VerifiedPrompt engineering and task-specification skill for improving prompts, agent instructions, system messages, evaluation prompts, coding-agent tasks, multi-step workflows, and LLM output reliability. Use when rewriting vague prompts, adding constraints, reducing ambiguity, improving safety, creating reusable prompt templates, or converting goals into actionable agent instructions.
Prompt Enhancement
Operating Rules
- Preserve the user's intent; do not over-constrain creative or exploratory tasks.
- Separate objective, context, inputs, constraints, output format, and verification criteria.
- Make implicit assumptions explicit when they affect outcome quality.
- Prefer testable instructions over personality-heavy wording.
Workflow
- Diagnose the prompt for missing context, ambiguous goals, conflicting constraints, and weak success criteria.
- Rewrite into a direct task with ordered steps and clear boundaries.
- Add output format only when structure improves usability.
- Add examples sparingly; use examples that demonstrate edge cases, not just happy paths.
- Include a short rationale when the user needs to understand tradeoffs.
Prompt Template
Objective: <what outcome is required>
Context: <facts, files, audience, constraints>
Inputs: <data the model should use>
Process: <important reasoning or execution steps>
Output: <format, length, tone, artifacts>
Validation: <how to check correctness>
Boundaries: <what to avoid or ask before doing>
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |