# Canonical NotFair workflow Human Guide

## What This Is For
Discover, connect, and verify NotFair paid-ad integrations and their actual 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
- Confirm OAuth/account access with a harmless account-list or read operation when the connector exposes one.
- Record the exact platform, selected account, accessible date range, and whether the surface is read-only or mutation-capable.
- If authorization fails, state the error and give the documented connection path. Do not retry a destructive operation or fall back to another account.

## Decision Points And Nuance
The original skill emphasizes: Supporting file: paid-ads/paid-ads-integrations/SKILL.md, Verify before promising, Capability map.

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
- If authorization fails, state the error and give the documented connection path. Do not retry a destructive operation or fall back to another account.

## 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-integrations`.

## 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-integrations/SKILL.md`](../../paid-ads/paid-ads-integrations/SKILL.md) completely, then follow it as the active workflow. Resolve every relative reference from that file against `../../paid-ads/paid-ads-integrations/`.

---

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

# Paid Ads Integrations

Read `../shared/operating-contract.md`. Treat tool discovery as the source of truth; product documentation describes intent, not the current session's authorization.

## Verify before promising

1. Inspect the available tool list. On the universal NotFair MCP, call `listConnectedPlatforms` first. Use the Google or Meta shared preamble when that surface is requested; for X Ads and LinkedIn Ads, resolve the platform-prefixed tools and require a harmless account/setup read before claiming access.
2. Confirm OAuth/account access with a harmless account-list or read operation when the connector exposes one.
3. Record the exact platform, selected account, accessible date range, and whether the surface is read-only or mutation-capable.
4. If authorization fails, state the error and give the documented connection path. Do not retry a destructive operation or fall back to another account.

## Capability map

| Platform | NotFair path | Safe response when unavailable |
|---|---|---|
| Google Ads | Universal NotFair MCP `google_ads_` tools; use the Google shared preamble | Connect/re-authenticate, then use the Google skills |
| Meta Ads | Universal NotFair MCP `meta_ads_` tools; use the Meta shared preamble | Connect/re-authenticate, then use the Meta skills |
| X Ads | Universal NotFair MCP `x_ads_` tools; resolve `~~x-ads` | Connect/re-authenticate, then use `/notfair:paid-ads-x` |
| LinkedIn Ads | Universal NotFair MCP `linkedin_ads_` tools; resolve `~~linkedin-ads` | Connect/re-authenticate, then use `/notfair:paid-ads-linkedin` |
| TikTok, Amazon, ChatGPT Ads | No first-party NotFair surface declared by this plugin | Request a verified connector or export; stay plan/review-only |

Never invent a router, endpoint, tool name, account ID, or platform capability. Quote prices, quotas, and platform eligibility only from current official documentation when a user asks; do not infer them from a plan or another connector.