openclaw - 💡(How to fix) Fix [Feature]: Plugin idea: openclaw-cost-tracker (per-session token + cost reporting) [1 comments, 2 participants]

Summary

Body: Proposing a community plugin: openclaw-prompt-library.

What it does

• Save reusable prompt templates: prompt save deploy "Deploy <service> to <env>..."
• Run them with variables: prompt run deploy service=api env=staging
• Share templates as JSON files (team workflows)
• Storage: ~/.openclaw/prompt-library/*.json

Problem to solve

Power users repeat the same prompts daily (deploy commands, code reviews, scaffolding). Today they paste from scratch notes or scroll through history. There's no structured, shareable way to save and reuse
prompt templates with variables.

Proposed solution

Proposed solution

A community plugin openclaw-prompt-library that provides:

• prompt save <name> "<template with {{vars}}>" — save a reusable template
• prompt list — show all saved templates
• prompt run <name> var1=value1 var2=value2 — execute with variable substitution
• prompt export <name> > team-prompt.json — share with teammates
• prompt import team-prompt.json — load shared templates

Storage: ~/.openclaw/prompt-library/*.json (one file per template, easy to git-track for teams).

Distribution

npm + ClawHub. No core changes.

Would the team be open to this as a community plugin? Any naming/scope conflicts with planned features I should avoid?

Alternatives considered

• Manual prefixing in prompts is inconsistent and hard to enforce across a team.
  • Shell aliases / snippet managers (e.g., Espanso) work outside OpenClaw but lose context — they can't reference session state or chain into OpenClaw commands.
  • A core feature inside OpenClaw itself would be heavier; a plugin keeps the surface small and lets the team validate demand before adopting it upstream.

Impact

Affected users/systems

• Power users running OpenClaw daily (developers, DevOps, technical writers)
• Teams using OpenClaw collaboratively who want consistent prompts across members
• Plugin authors who currently have no shared library to reference standard prompt patterns

Severity Annoying friction, not a blocker. Workflow still completes, but quality and consistency suffer. For teams it escalates to "blocks consistent output" — different members get different results from the same task because their prompts drift.

Frequency Always. Anyone who uses OpenClaw more than a few times a week hits this — every repeated task (commit messages, code review, deploy, scaffolding) is a candidate for a saved template.

Consequence

• Extra manual work: copying prompts from scratch notes, Slack pins, or Notion pages every time
• Inconsistent outputs: small wording differences in prompts produce noticeably different AI responses, leading to rework
• Knowledge loss: when a team member leaves, their well-tuned prompts leave with them — there's no shared library
• Slower onboarding: new team members can't inherit "the prompts that work" the way they inherit code or runbooks
• Lost productivity: conservatively 2-5 minutes per repeated task × multiple times daily = real hours per week per user

Evidence/examples

I published @syeda_quratualin/openclaw-rewind on npm + ClawHub recently. While building it, the most common feedback in community channels was "can it also save my favorite prompts?" — confirming the demand pattern.

• Real workflows users repeat daily:

  • "Review this diff for security issues, focus on auth and SQL injection: {{diff}}"
  • "Generate a conventional commit message for: {{changes}}"
  • "Deploy {{service}} to {{env}} with rollback plan"

• Prior art in adjacent ecosystems shows clear demand:

  • PromptHub, LangChain Hub, Cursor's .cursorrules — all solve fragments of this for their respective tools.
  • VS Code snippets and GitHub Copilot's custom instructions are widely used for the same reason.

• For teams, a shareable JSON file format means prompts can live in a git repo alongside code, get code-reviewed, and stay versioned — something no current OpenClaw workflow supports.

Additional information

No response