yes

Overview of yes skill

What yes skill is

The yes skill is a praise-forward variant of the repository’s PUA-style leader persona. Instead of hard-pressure delivery, it keeps the underlying discipline and accountability but changes the narration into warm, encouraging, ENFP-like coaching with light teasing. In practice, yes is for users who want motivational, emotionally supportive prompt writing without losing structure, standards, or follow-through.

Who should install yes skill

yes fits users who want an AI to:

• encourage them while they work through a task
• give feedback in a more human, upbeat tone
• keep momentum during debugging, drafting, or shipping work
• praise good process, not just final results

It is especially relevant as yes for Prompt Writing when you want a coaching voice that helps you continue, revise, and close loops instead of just generating neutral instructions.

Real job-to-be-done

Most users considering yes are not looking for a new capability engine. They are looking for a better delivery style: a skill that makes the assistant sound supportive, engaged, and occasionally playful while still asking for evidence, validation, and clearer thinking. That matters if generic prompts feel flat, demotivating, or too blunt.

What makes yes different from a normal style prompt

The main differentiator is not “be nicer.” The skill defines a specific persona and response rhythm:

• high empathy when the user is stuck
• genuine excitement when work is strong
• practical suggestions mixed into encouragement
• a small amount of teasing that should stay friendly, not sharp
• continued respect for the repo’s existing “red lines” and method discipline

That makes yes usage more consistent than a one-line prompt like “be supportive.”

What to know before adopting

This skill is lightweight: the repository evidence shows only a SKILL.md file and no extra rules, scripts, or examples. That is good for fast adoption, but it also means quality depends heavily on how clearly you invoke the mode and what context you provide. If you need deterministic task logic, install yes for tone and coaching style, not for workflow automation.

How to Use yes skill

yes install context

The upstream skill file does not include an explicit install command, so install flow depends on your skill runner or agent environment. If you use a skills CLI that supports GitHub skills, the pattern is typically adding the repository skill by repo and slug, then invoking the skill trigger in chat. Verify your tool’s exact command syntax before relying on it in production.

How yes is triggered in practice

The skill description explicitly signals these trigger phrases:

• /pua:yes
• 夸夸模式
• 唠嗑模式
• 情绪价值
• yes
• 夸我
• 鼓励模式

If your agent supports trigger matching from skill metadata, using one of those phrases should activate the yes skill tone. If not, manually reference the skill name and desired mode in your prompt.

The input yes skill needs

yes works better when you give it:

• the task you are doing
• your current state: stuck, unsure, halfway done, or finished
• what you already tried
• whether you want praise, critique, or both
• whether light teasing is welcome

Without that, the model may default to generic encouragement instead of the stronger “supportive but standards-aware” behavior this skill is meant to produce.

Turn a rough goal into a good yes prompt

Weak prompt:

• “Use yes and help me with this feature.”

Stronger prompt:

• “Use the yes skill. I’m implementing form validation in React, I already handled required fields, and I’m stuck on async uniqueness checks. Encourage me, point out what I’ve done well, then give the next 3 practical steps. If my thinking is weak, say so gently.”

The stronger version gives the skill a state, a task, and the exact balance of praise and direction.

yes usage for prompt writing

For yes for Prompt Writing, ask the skill to improve both morale and prompt quality. A strong setup looks like:

• your intended outcome
• the target model or agent
• constraints
• examples of bad output you want to avoid
• whether you want the result rewritten, critiqued, or scaffolded

Example:

• “Use yes for Prompt Writing. I need a prompt that makes an assistant summarize support tickets into action items. Be encouraging, tell me what is already good in my draft, then rewrite it with clearer scope, output format, and failure handling.”

Suggested workflow for first use

1. Activate yes explicitly.
2. State the task and where you are blocked.
3. Ask for two layers: encouragement first, then concrete next actions.
4. Request evidence checks if the task is technical: tests, logs, output, or validation.
5. After the first reply, ask for a tighter version focused on execution.

This workflow uses the skill for motivation without letting it become empty flattery.

Repository reading path before deeper adoption

Because the skill has only one visible source file, read SKILL.md first and treat it as the full contract. Pay attention to:

• personality traits
• tone examples
• the ratio of encouragement, advice, and teasing
• reminder that the base discipline remains unchanged
• “flavor” switching support mentioned in the file

That reading path is enough to decide whether the voice fits your workflow.

Practical boundaries that affect output quality

The repository does not provide formal constraints or decision rules beyond the text description. So you should set boundaries yourself when prompting:

• say whether you want emotional support or hard critique
• disable teasing for sensitive topics
• require concrete checks for claims of completion
• ask for concise output if you do not want long motivational framing

This matters because style-heavy skills can drift into performance if the task frame is vague.

Best use cases for yes skill

yes skill is most useful for:

• coding sessions where morale matters
• revision-heavy writing work
• brainstorming when confidence is low
• coaching-style progress reviews
• prompt writing where you want both uplift and sharper structure

It is less compelling for purely transactional requests like one-line conversions or deterministic extraction tasks.

yes skill FAQ

Is yes skill just a nicer system prompt

Not exactly. A normal prompt can say “be encouraging,” but yes adds a specific persona, pacing, and feedback style. The useful part is consistency: encouragement, process recognition, gentle correction, and occasional playful commentary in one mode.

Is yes suitable for beginners

Yes, often more than a harsher coaching style. Beginners usually benefit from a mode that acknowledges effort, reduces fear of failure, and still points them toward the next concrete step. Just make your request explicit so the answer stays practical.

When should I not use yes

Skip yes when you need:

• neutral, formal business tone
• strict compliance-style output
• emotionally flat summaries
• direct high-pressure management voice
• sensitive contexts where teasing could misfire

In those cases, a plain instruction set is safer.

Does yes replace normal task prompts

No. yes is a style-and-guidance layer, not a substitute for task specification. You still need to provide the goal, constraints, materials, and expected output. The better your task framing, the better the skill performs.

How does yes compare with ordinary prompts for motivation

The advantage of yes usage is tone continuity. Ordinary prompts often produce one encouraging paragraph and then revert to generic assistant language. This skill is designed to keep the supportive leader voice throughout the interaction.

Is yes good for team or shared workflows

Sometimes, but use care. In solo workflows, the playful style can improve momentum. In team settings, not everyone will want teasing or emotionally expressive feedback. If sharing outputs, ask the model to keep the yes tone supportive but professional.

How to Improve yes skill

Give yes skill a clear emotional target

The fastest quality gain is telling the model what kind of support you want:

• hype me up
• reassure me because I’m stuck
• praise what’s working but be strict on gaps
• keep it light, no teasing
• be warm but concise

That prevents the common failure mode where the answer sounds cheerful but not useful.

Provide evidence of progress, not just the task

yes performs better when it can praise real process. Give it code, drafts, decisions, logs, or the steps you already tried. Then it can respond with specific encouragement such as what you did well and where to go next, instead of generic “you’ve got this.”

Ask for praise plus next actions

A strong prompt pattern is:

• “Acknowledge what is good in my approach, then give the next 2-4 actions.”

This keeps the yes skill emotionally effective while making sure it still drives execution.

Prevent empty positivity

One risk with yes is over-indexing on encouragement. Counter that by adding:

• “Don’t flatter me if the work is weak.”
• “Point out the missing validation.”
• “If my plan is flawed, say so gently but clearly.”

That preserves the skill’s intended mix of support and standards.

Tune teasing carefully

The source text suggests teasing is a small part of the style, not the main event. If the model overdoes it, correct it directly:

• “Use yes mode, but keep teasing under 5%.”
• “No sarcasm.”
• “Friendly encouragement only.”

This is especially important for beginner users, tense debugging sessions, or professional contexts.

Iterate after the first answer

If the first output is too fluffy, ask for:

• fewer compliments
• more concrete steps
• stronger prioritization
• a rewritten answer with examples
• a version tied to your exact draft or code

The best yes guide workflow is iterative: first establish tone, then tighten for utility.

Use stronger inputs for prompt writing tasks

For yes for Prompt Writing, include:

• the exact prompt draft
• the target audience
• output schema
• failure cases
• what tone you want preserved

That allows the skill to praise what already works while materially improving structure, constraints, and clarity.

Keep the skill in its lane

If your main problem is missing domain knowledge, yes will not solve that by itself. Use it to improve coaching tone, confidence, and revision flow. Pair it with a stronger task brief or specialist skill when the job requires deeper technical reasoning.