# Canonical NotFair workflow Human Guide

## What This Is For
Explain NotFair's paid-ads skills, installation, platform boundaries, account connections, and current product capabilities. It gives the agent a clearer input/output frame for paid media: what context to ask for, what decisions to make, and what usable artifact to return.

Use this as a human-readable version of the Canonical NotFair workflow agent skill. It is meant for marketers, operators, founders, and other non-coders who want the workflow without reading agent-specific implementation instructions.

## When To Use This
- Use this when you need a repeatable process for canonical NotFair workflow.
- Use this when the task needs judgment, examples, constraints, or a clear output format rather than a one-off prompt.
- Use this when you want to hand an AI assistant enough context to produce a usable marketing artifact.

## When Not To Use This
- Do not use this when you only need a quick factual answer.
- Do not use this when the work depends on private data you cannot share with the assistant.
- Do not use this as a replacement for legal, compliance, financial, or medical review.

## What You Need Before Starting
- The goal or business outcome you want.
- The audience, customer segment, or market context.
- Any source material the assistant should respect, such as notes, briefs, examples, URLs, or brand guidance.
- Constraints such as tone, length, channel, deadline, region, or approval requirements.
- A clear definition of what a good final answer should look like.

## Step-By-Step Workflow
1. State the job clearly: "Use the Canonical NotFair workflow guide to help me with..."
2. Add context: audience, goal, offer, channel, source material, and constraints.
3. Ask the assistant to identify missing inputs before producing the final output.
4. Have the assistant follow the skill-specific guidance below.
5. Review the result against the final checklist and ask for revisions where needed.

## Skill-Specific Guidance
- Frame the work around canonical NotFair workflow and ask for the context needed to do it well.
- Turn vague preferences into explicit choices before drafting the final output.
- Ask for a concrete deliverable, not just general advice.

## Decision Points And Nuance
The original skill emphasizes: Supporting file: paid-ads/paid-ads-guide/SKILL.md, Answer from the right source, Essential facts.

Use these questions to steer the work:
- What is the intended audience or buyer?
- What source material must be preserved?
- What should the assistant optimize for: clarity, persuasion, accuracy, speed, creativity, or conversion?
- What examples represent the desired quality bar?
- What should the assistant avoid?

## Common Mistakes
- | Product pricing, quotas, current eligibility, or platform policies | The current official page or platform documentation; do not quote a number from memory |

## Copy-And-Paste Prompt
```text
Use the Canonical NotFair workflow human guide.

My goal:
[Describe the business outcome]

Audience:
[Describe who this is for]

Context and source material:
[Paste notes, examples, links, or existing copy]

Constraints:
[Tone, length, channel, timeline, must-include items, must-avoid items]

Before producing the final output, ask me for any missing information that would materially improve the result.
```

## Final Checklist
- [ ] The output matches the original goal.
- [ ] The audience and context are reflected in the answer.
- [ ] Important constraints and source material were preserved.
- [ ] The assistant made the relevant decisions explicit.
- [ ] The final artifact is ready to use, review, or hand to the next person.

## Source
This guide was generated from the nowork-studio/notfair-plugin skill entry for `paid-ads-guide`.

## Source Skill Notes
These notes preserve the nuance from the original skill. Use them as supporting reference when the workflow above feels too generic.

# Canonical NotFair workflow

Read [`../../paid-ads/paid-ads-guide/SKILL.md`](../../paid-ads/paid-ads-guide/SKILL.md) completely, then follow it as the active workflow. Resolve every relative reference from that file against `../../paid-ads/paid-ads-guide/`.

---

## Supporting file: paid-ads/paid-ads-guide/SKILL.md

# NotFair Paid Ads Guide

Answer NotFair product questions from the repository documentation or current official NotFair documentation, never from stale memory. This skill explains the product; use `/notfair:paid-ads-integrations` for the current session's actual connector and account access.

## Answer from the right source

| Question | Source of truth |
|---|---|
| Plugin install, skill catalog, current documented connectors, and operating boundaries | Repository `README.md` and `AGENTS.md` |
| Current session's available tools, OAuth state, and selected accounts | `/notfair:paid-ads-integrations` plus the platform shared preamble |
| Product pricing, quotas, current eligibility, or platform policies | The current official page or platform documentation; do not quote a number from memory |
| A performance, campaign, or optimization question | Route to `/notfair:paid-ads`, `/notfair:google-ads`, or `/notfair:meta-ads` |

## Essential facts

NotFair supplies host-agnostic skills plus one OAuth-connected MCP operating surface for Google Ads, Meta Ads, X Ads, LinkedIn Ads, Google Analytics, and Search Console. Each platform keeps its dedicated workflow and platform-prefixed tools inside that universal connection. TikTok, Amazon, and ChatGPT Ads remain planning/review-first until the session has a verified connector; those skills are not a claim of publication access.

The goal-loop app makes an outcome measurable, verifies the baseline at the source, and revisits the metric on an approved cadence. The plugin is the hands-on companion for audits, briefs, and supported account operations. Explain the safety boundary plainly: an approved plan is not a live campaign, and a brief is not a published asset.

When installation is requested, direct the user to the README's plugin install steps. When a connector is missing or unauthorized, use the appropriate platform preamble and stop at the connection CTA rather than inventing a workaround.