agentsclimarketplace

Skill prompt brief

Skill TSFanKing/skill-prompt-brief

中英双语：把粗略 skill 想法扩展成完整制作提示词 / Bilingual build briefs for Codex and agent skills.

Install
npx -y skills add TSFanKing/skill-prompt-brief

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
  • 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Turn a rough one-sentence skill idea into a complete professional build brief for a skill creator. Use when the user wants prompt wording, requirements, specs, or a handoff brief for someone else to create a Codex/agent skill, especially from vague requests like "make a skill for X", "write the prompt for a skill about X", "help me describe a skill idea", or "generate a complete skill-making prompt".

SKILL.md

2.8 KB, as published. Nobody here has run it

Skill Prompt Brief

Purpose

Create a polished handoff prompt that a professional skill creator can use to build a high-quality skill. Do not create the skill itself unless the user explicitly asks for implementation.

Workflow

  1. Identify the user's rough skill idea, target users, domain, expected outputs, and any named tools or platforms.
  2. Expand the idea into a professional skill-making brief with clear scope, trigger conditions, workflows, resources, validation, and safety boundaries.
  3. Include domain-specific knowledge the skill creator should research or encode. If current facts, regulations, APIs, prices, model names, or platform behavior matter, browse or instruct the skill creator to verify authoritative sources.
  4. Preserve the user's language preference. If the user asks for Chinese or English, write the handoff prompt in that language. If no language is specified, use the user's language.
  5. Ask at most one concise clarification only when the idea is too ambiguous to produce a useful brief. Otherwise make reasonable assumptions and state them.
  6. Use references/brief-patterns.md when the request needs a comprehensive template, domain checklist, or quality rubric.

Output Requirements

Return a directly reusable prompt addressed to a skill creator. The prompt must include:

  • User original idea
  • Skill purpose and non-goals
  • Suggested skill name and description
  • Trigger examples and anti-trigger boundaries
  • Expected inputs and outputs
  • Core workflow and decision branches
  • Recommended references/, scripts/, and assets/ contents
  • Domain knowledge to research or encode
  • Safety, verification, and uncertainty rules
  • Test cases and acceptance criteria
  • Final deliverables expected from the skill creator

Quality Rules

  • Be specific enough that another agent can build the skill without guessing the user's intent.
  • Separate stable procedural knowledge from facts that may require live verification.
  • Recommend scripts only for repeatable or error-prone operations; recommend references for long domain knowledge; recommend assets for reusable templates or media.
  • Make the description concrete and trigger-rich, because it controls skill invocation.
  • Avoid promising that the future skill can make high-stakes decisions alone. Require disclaimers, source checks, or human review where appropriate.
  • Keep the final answer focused on the handoff prompt, not on explaining how skills work.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.