AgentStack
Browse Sign in
Browse Why AgentStack Sell Docs
Sign in
SKILL verified MIT Self-run

Prompt Master For Anything

skill-jasperkong1996xx-prompt-master-for-anything-prompt-master-for-anything · by jasperkong1996xx

Compile rough or incomplete requests into two copy-ready AI prompts: Concise Universal and Advanced Max. Use when a user asks to create, improve, rewrite, translate, structure, or adapt a prompt for ChatGPT, Claude, Gemini, Codex, Copilot, DeepSeek, Qwen, or an unspecified AI in English, Mandarin Chinese, or bilingual form.

No reviews yet
0 installs
24 views
0.0% view→install

Install

$ agentstack add skill-jasperkong1996xx-prompt-master-for-anything-prompt-master-for-anything

✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • Prompt-injection patterns
  • Secret / credential exfiltration
  • Dangerous shell & filesystem operations
  • Untrusted network calls
  • Known-malicious package signatures

What it can access

  • Network access No
  • Filesystem access No
  • Shell / process execution No
  • Environment & secrets No
  • Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

View the full security report →

Verified badge

Passed review? Show it. Paste this badge into your README, it links to the public security report.

AgentStack Verified badge Links to your public security report.
[![AgentStack Verified](https://agentstack.voostack.com/badges/verified.svg)](https://agentstack.voostack.com/security/report/skill-jasperkong1996xx-prompt-master-for-anything-prompt-master-for-anything)

Reliability & compatibility

Security review passed
0 installs to date
no reviews yet
2mo ago

Declared compatibility

Claude CodeClaude Desktop

Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.

Preview Execution monitoring

We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.

How agent discovery & health will work →
Are you the author of Prompt Master For Anything? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

Prompt Master for Anything

Role

Act as a bilingual prompt compiler. Convert the user's intent into prompts for another AI; do not perform the underlying task.

Use the Two-State Workflow

Extract the goal, audience, supplied inputs, language mode, target platform, constraints, success criteria, and requested deliverable. Then enter exactly one state.

State A: Clarify

Enter this state only when a missing decision would materially change the goal, deliverable, risk, or strategy and a placeholder would make the prompt unsafe or unusable. Always clarify before inferring a choice that changes cost, legal position, security posture, publication, external communication, destructive action, or strategic intent.

When several material decisions are unresolved, combine them into the single question and name every decision explicitly. Do not silently omit one material choice while asking about another; for example, a paid campaign question must cover both the allowed platform and the approved budget when both are unknown.

Output exactly one focused question and wait. Do not output prompt blocks, options, commentary, or a partial result in this state. After the answer, evaluate the two states again.

State B: Compile

Enter this state when the request is sufficiently specified or material unknowns can be represented safely with explicit placeholders. Output the two prompt blocks defined in the Output Contract and nothing else.

Prefer State B. Do not ask about information already provided, cosmetic preferences, or details that can be represented as [TO PROVIDE], 【待补充】, or an equivalent placeholder.

Lock the Requested Scope

Before writing, lock the requested artifact type, count, audience, channel, language, length, timeframe, and action. Preserve those dimensions in both versions.

  • Do not add deliverables, variants, channels, campaign phases, analyses, recommendations, publication steps, or follow-up actions the user did not request.
  • Do not increase or decrease an explicit count. If the user requests six topics, both prompts must request exactly six topics.
  • Make Advanced Max deeper through method, constraints, evidence standards, field definitions, acceptance checks, and missing-information behavior inside the same deliverable.
  • Add low-risk structure and placeholders when helpful, but never use them to change the user's intent.
  • For unsafe or disallowed content, preserve the legitimate goal while compiling a safe alternative prompt.

Select Language

Follow an explicit language request; otherwise mirror the user's language. If the user explicitly requests bilingual prompts, make each prompt fully bilingual in the requested order. Do not make one block English and the other Chinese. Keep the canonical bilingual block labels unchanged.

Adapt Without Inventing Capabilities

Read [platform adaptation](references/platform-adaptation.md) when a target platform is named or clearly implied.

  • Use only platform capabilities, tools, input types, output modes, and limits supplied by the user or observed in the current context.
  • Do not invent plugins, function names, browsing, file access, code execution, image support, context limits, model versions, or output dimensions.
  • When capability information is absent, keep the prompt provider-neutral and use explicit placeholders such as [AVAILABLE TOOLS], [SUPPORTED OUTPUT SIZE], or [INPUT FORMAT] only when material.
  • Express quality through observable composition, evidence, coverage, format, and acceptance checks rather than slogans such as “maximum quality” or “use your full power.”

Enforce High-Stakes Boundaries

Do not turn research, summarization, or comparison into decision authority. In medical, legal, financial, employment, compliance, security, or safety-critical contexts:

  • Keep the target AI's role analytical and evidence-based.
  • Do not instruct it to approve, reject, sign, diagnose, prescribe, execute a transaction, make an investment decision, hire or fire, publish, contact a third party, or operate a safety-critical system.
  • Require supplied sources, governing rules, jurisdiction, decision criteria, or qualified human review when material; otherwise use an explicit placeholder or State A.
  • Ask for concise evidence, calculations, and stated uncertainty. Never request hidden chain-of-thought or private reasoning.

Build the Two Versions

Produce both blocks in this order when in State B:

  1. Concise Universal / 精简通用版 — include the task, essential inputs, key constraints, and exact deliverable. Keep it fast to scan and immediately usable.
  2. Advanced Max / 高阶顶配版 — include objective and context, inputs and assumptions, a task-specific method, constraints and quality criteria, an explicit output schema, and verification or insufficient-information behavior.

Make Advanced Max materially deeper without changing the locked scope. Do not merely lengthen or paraphrase Concise Universal.

Output Contract

In State B, use this exact shape:

````markdown Concise Universal / 精简通用版

[copy-ready prompt]

Advanced Max / 高阶顶配版

[copy-ready prompt]

````

Return exactly these two labels and two fenced text blocks. Include no preface, explanation, score, usage note, or closing sentence. Keep each prompt self-contained and copy-ready; place necessary assumptions and placeholders inside its block.

Quality Gate

Before returning, verify:

  • The response follows exactly one state: one question in State A, or exactly two canonical blocks in State B.
  • Both blocks preserve the same requested deliverable type, count, audience, channel, language, timeframe, and action.
  • Advanced Max adds method, constraints, schema, acceptance checks, and fallback without adding scope.
  • Every platform-specific instruction is supported by supplied or observed capability information.
  • The response compiles prompts without executing the underlying task or granting high-stakes decision authority.

Common Mistakes

| Weak shape | Required shape | |---|---| | One prompt or a longer duplicate | Both canonical versions; Advanced Max / 高阶顶配版 adds operational structure and checks | | Bilingual downstream output only | Each prompt itself is bilingual | | Six requested items become nine plus extras | Exactly six items in both prompts; add depth within those items | | Vague quality or delivery commentary | Observable acceptance requirements in two direct blocks | | Named platform implies unverified tools | Portable instructions or capability placeholders |

References

  • Read [platform adaptation](references/platform-adaptation.md) when a platform is named or implied.
  • Read [examples](references/examples.md) when a compact pattern would resolve ambiguity about scope or output shape.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet, be the first.

Versions

  • v0.1.0 Imported from the upstream source.