Pitch Psychologist

• Use when a sales, investor, or product pitch needs stronger belief progression and audience alignment.
• Use when the pitch must move from attention to trust to commitment with less resistance.
• Use when the request clearly matches the imported source intent: One sentence - what this skill does and when to invoke it.
• Use when the operator should preserve upstream workflow detail instead of rewriting the process from scratch.
• Use when provenance needs to stay visible in the answer, PR, or review packet.
• Use when copied upstream references, examples, or scripts materially improve the answer.

Operating Table

Workflow

This workflow is intentionally editorial and operational at the same time. It keeps the imported source useful to the operator while still satisfying the public intake standards that feed the downstream enhancer flow.

1. Confirm the user goal, the scope of the imported workflow, and whether this skill is still the right router for the task.
2. Read the overview and provenance files before loading any copied upstream support files.
3. Load only the references, examples, prompts, or scripts that materially change the outcome for the current request.
4. Execute the upstream workflow while keeping provenance and source boundaries explicit in the working notes.
5. Validate the result against the upstream expectations and the evidence you can point to in the copied files.
6. Escalate or hand off to a related skill when the work moves out of this imported workflow's center of gravity.
7. Before merge or closure, record what was used, what changed, and what the reviewer still needs to verify.

Imported Workflow Notes

Imported: CONTEXT GATHERING

Before building a pitch, establish:

1. The Target Human - psychographic profile, trust stage, and awareness level.
2. The Objective - the decision or commitment the pitch must produce.
3. The Output - deck, talk track, one-pager, or demo script.
4. Constraints - audience type, time limit, and ethical boundaries.

If the decision context is unclear, ask before proceeding.

Examples

Example 1: Ask for the upstream workflow directly

Use @pitch-psychologist to handle <task>. Start from the copied upstream workflow, load only the files that change the outcome, and keep provenance visible in the answer.

Explanation: This is the safest starting point when the operator needs the imported workflow, but not the entire repository.

Example 2: Ask for a provenance-grounded review

Review @pitch-psychologist against EXTERNAL_SOURCE.json and ORIGIN.md, then explain which copied upstream files you would load first and why.

Explanation: Use this before review or troubleshooting when you need a precise, auditable explanation of origin and file selection.

Example 3: Narrow the copied support files before execution

Use @pitch-psychologist for <task>. Load only the copied references, examples, or scripts that change the outcome, and name the files explicitly before proceeding.

Explanation: This keeps the skill aligned with progressive disclosure instead of loading the whole copied package by default.

Example 4: Build a reviewer packet

Review @pitch-psychologist using the copied upstream files plus provenance, then summarize any gaps before merge.

Explanation: This is useful when the PR is waiting for human review and you want a repeatable audit packet.

Best Practices

Treat the generated public skill as a reviewable packaging layer around the upstream repository. The goal is to keep provenance explicit and load only the copied source material that materially improves execution.

• Be truthful about capabilities and tradeoffs.
• Avoid theatrical pressure or fake inevitability.
• Respect the audience's right to decline.
• Keep the imported skill grounded in the upstream repository; do not invent steps that the source material cannot support.
• Prefer the smallest useful set of support files so the workflow stays auditable and fast to review.
• Keep provenance, source commit, and imported file paths visible in notes and PR descriptions.
• Point directly at the copied upstream files that justify the workflow instead of relying on generic review boilerplate.

Imported Operating Notes

Imported: ETHICAL GUARDRAILS

This skill must:

• Be truthful about capabilities and tradeoffs.
• Avoid theatrical pressure or fake inevitability.
• Respect the audience's right to decline.

The line between persuasion and manipulation is sequencing ideas to help a person evaluate a real offer versus engineering a narrative that hides material facts. Never cross it.

Troubleshooting

Problem: The operator skipped the imported context and answered too generically

Symptoms: The result ignores the upstream workflow in plugins/antigravity-awesome-skills-claude/skills/pitch-psychologist, fails to mention provenance, or does not use any copied source files at all. Solution: Re-open EXTERNAL_SOURCE.json, ORIGIN.md, and the most relevant copied upstream files. Load only the files that materially change the answer, then restate the provenance before continuing.

Problem: The imported workflow feels incomplete during review

Symptoms: Reviewers can see the generated SKILL.md, but they cannot quickly tell which references, examples, or scripts matter for the current task. Solution: Point at the exact copied references, examples, scripts, or assets that justify the path you took. If the gap is still real, record it in the PR instead of hiding it.

Problem: The task drifted into a different specialization

Symptoms: The imported skill starts in the right place, but the work turns into debugging, architecture, design, security, or release orchestration that a native skill handles better. Solution: Use the related skills section to hand off deliberately. Keep the imported provenance visible so the next skill inherits the right context instead of starting blind.

Imported Troubleshooting Notes

Imported: FAILURE MODES - DO NOT DO THESE

Failure Mode 1

• Agents typically: open with features.
• Why it fails psychologically: the audience has no emotional reason to care yet.
• Instead: open with the world and tension.

Failure Mode 2

• Agents typically: pack the pitch with details before desire is built.
• Why it fails psychologically: cognitive load increases and persuasion drops.
• Instead: sequence desire before explanation.

Failure Mode 3

• Agents typically: end weakly.
• Why it fails psychologically: people remember the ending and the peak more than the middle.
• Instead: end on the key idea and next step.

Related Skills

• @00-andruia-consultant-v2 - Use when the work is better handled by that native specialization after this imported skill establishes context.
• @10-andruia-skill-smith-v2 - Use when the work is better handled by that native specialization after this imported skill establishes context.
• @20-andruia-niche-intelligence-v2 - Use when the work is better handled by that native specialization after this imported skill establishes context.
• @2d-games - Use when the work is better handled by that native specialization after this imported skill establishes context.

Additional Resources

Use this support matrix and the linked files below as the operator packet for this imported skill. They should reflect real copied source material, not generic scaffolding.

Imported Reference Notes

Imported: DECISION MATRIX

Variable: audience type

• If technical -> lead with evidence, then implications, then demo.
• If executive -> lead with risk, opportunity, then business outcome.
• If consumer -> lead with desire, identity, then ease of action.
• If skeptical -> lead with proof, then only enough story to connect it.

Variable: awareness stage

• If unaware -> start with the problem and the cost of delay.
• If problem aware -> sharpen the problem and show a believable alternative.
• If solution aware -> show why your approach fits best.
• If product aware -> reduce hesitation with proof and clarity.

Variable: pitch length

• If short -> compress into problem, tension, bridge, ask.
• If medium -> add proof and comparison.
• If long -> add case logic, objections, and decision support.

Imported: PSYCHOLOGICAL FRAMEWORK: DESIRE-THEN-SOLUTION ARC

Mechanism

People are more persuadable when they first feel the problem, the aspiration, and the cost of staying put, then receive the solution as the natural resolution. Narrative transportation, contrast, anchoring, and memory sequencing all matter more than raw feature density (Green & Brock, 2000; Chen & Bell, 2022; Bagozzi et al., 2021; peak-end research; motivated sequence theory).

Execution Steps

Step 1 - Open with the audience's world Start from the customer's current reality and stakes. Research basis: self-relevance and narrative transportation increase receptivity (Green & Brock, 2000; Dragojevic et al., 2024).

Step 2 - Build desire before solution Show the better future and the cost of not getting there. Research basis: desire-first sequencing reduces defensive processing and improves belief change (Monroe's motivated sequence; narrative persuasion studies).

Step 3 - Frame the contrast Make the current state and proposed state visibly different. Research basis: contrast and anchoring shape evaluation by shifting the reference point (Ariely et al., 2003; Houdek, 2016).

Step 4 - Introduce the solution as the bridge Position the offer as the path through the tension you already established. Research basis: people accept solutions more readily when the problem has been emotionally and cognitively prepared (Bagozzi et al., 2021).

Step 5 - End with remembered clarity Close on the key idea, proof, and next step. Research basis: the peak-end rule shapes what audiences recall after the pitch (memory and decision research; Chen & Bell, 2022).

Imported: SKILL CHAINING

Before invoking this skill, the agent should have completed:

• @customer-psychographic-profiler
• @jobs-to-be-done-analyst
• @awareness-stage-mapper
• @trust-calibrator

This skill's output feeds into:

• @deck-writing
• @sales-page
• @presentation-script

Imported: OUTPUT QUALITY CHECK

Before finalizing output, the agent asks:

• Did I build desire before explaining the solution?
• Did I use contrast effectively?
• Did I choose the right pitch sequence for the audience?
• Did I end with remembered clarity?
• Would the pitch still feel honest if challenged?

Imported: Limitations

• Use this skill only when the task clearly matches the scope described above.
• Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
• Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.