skills$openclaw/promptify
tolibear3.0k

by tolibear

promptify – OpenClaw Skill

promptify is an OpenClaw Skills integration for coding workflows. Optimize prompts for clarity and effectiveness. Use when user says "improve this prompt", "optimize my prompt", "make this clearer", or provides vague/unstructured prompts. Intelligently routes to sub-agents for codebase research, clarifying questions, or web search as needed.

3.0k stars6.5k forksSecurity L1
Updated Feb 7, 2026Created Feb 7, 2026coding

Skill Snapshot

namepromptify
descriptionOptimize prompts for clarity and effectiveness. Use when user says "improve this prompt", "optimize my prompt", "make this clearer", or provides vague/unstructured prompts. Intelligently routes to sub-agents for codebase research, clarifying questions, or web search as needed. OpenClaw Skills integration.
ownertolibear
repositorytolibear/promptify
languageMarkdown
licenseMIT
topics
securityL1
installopenclaw add @tolibear/promptify
last updatedFeb 7, 2026

Maintainer

tolibear

tolibear

Maintains promptify in the OpenClaw Skills directory.

View GitHub profile
File Explorer
9 files
.
agents
clarifier.md
2.4 KB
codebase-researcher.md
2.1 KB
web-researcher.md
2.7 KB
commands
promptify.md
2.0 KB
_meta.json
278 B
README.md
2.1 KB
SKILL.md
2.1 KB
SKILL.md

name: promptify description: Optimize prompts for clarity and effectiveness. Use when user says "improve this prompt", "optimize my prompt", "make this clearer", or provides vague/unstructured prompts. Intelligently routes to sub-agents for codebase research, clarifying questions, or web search as needed. metadata: {"moltbot":{"emoji":"✨"}}

Prompt Optimizer

Transform prompts into clear, effective ones. Model-agnostic.

Modifiers (parse from ARGUMENTS)

  • +ask → Force clarifying questions
  • +deep → Force codebase exploration
  • +web → Force web search

No modifiers? Auto-detect what's needed.

Auto-Detection Triggers

TriggerSignals
codebase-researcher"this project", "our API", specific files/functions, "integrate", "extend", "refactor"
clarifierAmbiguous ("make it better"), multiple interpretations, missing constraints, vague pronouns
web-researcher"best practices", "latest", external APIs/libraries, framework patterns, year references

Agent Dispatch

When agents needed:

  1. Announce which and why
  2. Run in parallel via Task tool (agents/ directory)
  3. Synthesize findings
  4. Optimize with gathered context

Core Contract (every prompt needs all four)

ElementIf Missing
RoleAdd persona with expertise
TaskMake action specific
ConstraintsInfer from context
OutputSpecify format/structure

Process

  1. If image: Analyze, incorporate context
  2. Detect type: coding/writing/analysis/creative/data
  3. Convert output→process: "Write X" → "Analyze → Plan → Implement → Validate"
  4. Strip fluff: "please", "I want you to", filler, apologies
  5. Apply contract: Verify all 4 elements
  6. Add structure: XML tags for complex prompts

Type Focus

  • Coding: Specs, edge cases, framework
  • Writing: Tone, audience, length
  • Analysis: Criteria, depth
  • Creative: Constraints, novelty
  • Data: I/O format, edge cases

Output

  1. Optimized prompt in code block
  2. echo 'PROMPT' | pbcopy
  3. 2-3 sentence explanation
README.md

Promptify

Optimize your prompts. One command, stackable modifiers.

Works in Claude Code and molt.bot.

Install

Claude Code:

claude plugin install promptify@tolibear

Molt.bot:

npx molthub install promptify

Usage

/promptify [+modifiers] your prompt here

Modifiers

ModifierEffect
+askAsk clarifying questions first
+deepExplore codebase for context
+webSearch web for best practices

Stack them:

/promptify +ask+deep+web Build a payment system

Smart Auto-Detection (v3)

Skip modifiers - promptify auto-detects what's needed:

Your PromptAuto-Triggers
"Add auth to our API"Codebase research
"Help me with this thing"Clarifying questions
"Best practices for React hooks"Web search
"Write a landing page"Direct optimization

Example

Before:

Build a payment system

After:

You are a senior backend engineer with Stripe integration experience.

<task>
1. Analyze payment requirements (one-time vs recurring, currencies, refunds)
2. Design the data model (customers, payments, subscriptions)
3. Implement Stripe integration with proper error handling
4. Add webhook handlers for payment events
5. Include idempotency keys for safe retries
</task>

<constraints>
- Use Stripe API v2024-01
- Handle card failures gracefully with user-friendly messages
- Log all payment events for debugging
- Never store raw card numbers
</constraints>

<output>
Working implementation with:
- Payment service class
- Webhook controller
- Database migrations
- Test coverage for happy path and failure cases
</output>

What It Does

  • Analyzes images you include
  • Uses conversation context
  • Detects prompt type (coding, writing, analysis, creative, data)
  • Converts output requests to process-oriented prompts
  • Removes anti-patterns (filler, excessive politeness)
  • Enforces Role, Task, Constraints, Output
  • Copies to clipboard

Changelog

v3.0.0 - Rewritten for Claude 4.x. 65% shorter (163→57 lines). Progressive disclosure. Contract-first design.

License

MIT

Permissions & Security

Security level L1: Low-risk skills with minimal permissions. Review inputs and outputs before running in production.

Requirements

  • OpenClaw CLI installed and configured.
  • Language: Markdown
  • License: MIT
  • Topics:

FAQ

How do I install promptify?

Run openclaw add @tolibear/promptify in your terminal. This installs promptify into your OpenClaw Skills catalog.

Does this skill run locally or in the cloud?

OpenClaw Skills execute locally by default. Review the SKILL.md and permissions before running any skill.

Where can I verify the source code?

The source repository is available at https://github.com/openclaw/skills/tree/main/skills/tolibear/promptify. Review commits and README documentation before installing.