agentsclimarketplace
Sign in

Promptify

Skill ulpi-io/plugin-marketplace/plugins/intellectronica/skills/promptify

Transform user requests into detailed, precise prompts for AI models. Use when users say "promptify", "promptify this", or explicitly request prompt engineering or improvement of their request for better AI responses.From its SKILL.md

Install
npx -y skills add ulpi-io/plugin-marketplace --skill promptify

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.

SKILL.md

1.8 KB, 347 tokens by cl100k_base, as published. Nobody here has run it

Promptify

Transform user requests into detailed, precise prompts optimised for AI model consumption.

Core Task

Rewrite the user's request as a clear, specific, and complete prompt that guides an AI model to produce the desired output without ambiguity. Treat the output as specification language, not casual natural language.

Process

  1. Read and understand - Read the user's request carefully to understand the full context, intent, and all details
  2. Plan the rewrite - Consider what specific information, instructions, or context the AI model needs to fulfill the request effectively
  3. Rewrite as a detailed prompt - Transform the request into a precise prompt with clarity, specificity, and completeness

Writing Guidelines

Structure

  • Begin with a single short paragraph summarising the overall task
  • Use headings (##, ###, ####) for sections only where appropriate (no first-level title)
  • Use bold, italics, bullet points (-), and numbered lists (1., 2.) liberally for organisation
  • Never use emojis
  • Never use * for bullet points, always use -

Language

  • Use plain, straightforward, precise language
  • Avoid embellishments, niceties, or creative flourishes
  • Think of language as specification/code, not natural language
  • Be clear and specific in all instructions

Content

  • Keep the prompt concise: 0.75X to 1.5X the length of the original request
  • Do not add or invent information not present in the input
  • Do not include unnecessary complexity or verbosity

Output

Provide only the final prompt as markdown, without additional commentary or explanation.

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Gives 0 of the 12 instructions most prompt engineering skills give in 347 tokens

Counted across 542 of the 575 authors here whose files we hold, read 2026-09-06

  • Provide few-shot examples for complex tasksin 17 of 542, across 16 files
  • Ask clarifying questions if information is ambiguousin 16 of 542, across 14 files
  • Output a complete optimized prompt for the userin 15 of 542, across 9 files
  • Validate structured outputs against schemasin 15 of 542, across 13 files
  • Analyze the draft prompt for intent and gapsin 14 of 542, across 8 files
  • Detect project tech stack from local filesin 14 of 542, across 8 files
  • Recommend a model based on task scopein 13 of 542, across 7 files
  • Present results in the specified output formatin 13 of 542, across 7 files
  • Match intent and scope to ECC componentsin 13 of 542, across 7 files
  • Ask one question at a timein 13 of 542, across 12 files
  • Respond in the same language as the user inputin 12 of 542, across 6 files
  • Ask up to three clarification questions if context is missingin 11 of 542, across 5 files

Said here and by no other author read

  • Read the user request carefully
  • Rewrite the request as a detailed prompt
  • Summarize the task in one paragraph
  • Use headings for section organization
  • Use bold and italics for emphasis
  • Use bullet points and numbered lists

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 325,949. 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.