agentsclimarketplace
Sign in

Social campaign proof tracker

Skill jqaisystems/jqai-ai-skills/skills/social-campaign-proof-tracker

Plan, document, and follow up on public proof campaigns across LinkedIn, X, GitHub, websites, and videos. Use when the user wants carousel or thread copy, alt text, post/video captions, public link tracking, reply banks, engagement review, or a campaign proof trail after publishing project work.From its SKILL.md

Install
npx -y skills add jqaisystems/jqai-ai-skills --skill social-campaign-proof-tracker

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 2 stars2 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

3.4 KB, 703 tokens by cl100k_base, as published. Nobody here has run it

Social Campaign Proof Tracker

Overview

Use this skill to turn a project update into a public proof campaign with platform-specific copy, visual order, alt text, links, reply prompts, and follow-up tracking.

This skill organizes and drafts. It must not post, upload, comment, message, or submit externally unless the user explicitly asks and confirms the final action.

Workflow

  1. Identify the proof object:
    • GitHub update
    • demo
    • video
    • website page
    • case study
    • skill release
    • automation milestone
  2. Gather only public-safe inputs:
    • public links
    • approved images or videos
    • short outcome summary
    • safe implementation categories
    • approved calls to action
  3. Choose platform shape:
    • LinkedIn: reflective post, carousel, document-style sequence, or video post
    • X: short post, thread, image-led thread, or video-led post
    • GitHub: README note, release note, proof trail, or demo link
  4. Draft platform copy.
    • LinkedIn: clearer context, stronger hook, more reflective tone.
    • X: short lines, one idea per post, direct links.
  5. Add accessibility and context:
    • alt text for each image
    • caption for video if needed
    • link labels
    • comment/reply prompts
  6. Create or update a local tracker:
    • campaign name
    • date
    • asset list
    • published links
    • follow-up windows
    • engagement notes
    • useful replies
  7. After publishing, record only public results unless the user explicitly provides private metrics for private analysis.

Public Safety Rules

  • Do not include private analytics exports, cookies, account IDs, unpublished client data, raw messages, private prompts, local paths, or credential-adjacent details.
  • Do not invent engagement results.
  • Do not imply client permission or measurable outcomes unless the user confirms them.
  • Keep reply banks human-reviewed and non-spammy.
  • Treat low comments as normal signal, not failure. Track proof value, reuse potential, and follow-up ideas.

Copy Rules

  • Lead with the public proof angle or the useful lesson.
  • Use concrete nouns: system, workflow, profile, proof layer, demo, skill, release.
  • Avoid vague hype such as "game-changing" unless the user asks for a louder tone.
  • Keep CTAs light: "I am building this in public", "open to feedback", "details on GitHub", or "happy to share the workflow".
  • For X, prefer a thread over unrelated comments when multiple visuals belong to one story.

Tracker Shape

Use this structure by default:

# Campaign Tracker

Campaign:
Date:
Proof object:
Primary link:

## Assets

| Asset | Platform | Status | Notes |
| --- | --- | --- | --- |

## Published Links

| Platform | URL | Notes |
| --- | --- | --- |

## Follow-Up

| Window | Action | Status |
| --- | --- | --- |

## Reply Bank

- Thank-you reply:
- Technical reply:
- Client-value reply:
- Quiet-engagement follow-up:

Output Format

Return:

  1. Campaign recommendation.
  2. Platform copy.
  3. Asset order and alt text.
  4. Tracker or proof-trail updates made.
  5. Follow-up actions and timing.

What ships with it: 1 file

270 B alongside SKILL.md

agents/

Gives 0 of the 12 instructions most marketing audience skills give in 703 tokens

Counted across 690 of the 894 authors here whose files we hold, read 2026-08-07

  • Apply Poppins font to headingsin 41 of 690, across 6 files
  • Apply Lora font to body textin 41 of 690, across 6 files
  • Use Arial fallback for headingsin 39 of 690, across 4 files
  • Use Georgia fallback for body textin 39 of 690, across 4 files
  • Maintain text hierarchy and formattingin 39 of 690, across 4 files
  • Use accent colors for non-text shapesin 38 of 690, across 3 files
  • Use RGB values for precise color matchingin 38 of 690, across 3 files
  • Use brand colors for primary text and backgroundsin 36 of 690, across 1 file
  • Read product marketing context file before asking questions, starting, or auditingin 35 of 690, across 23 files
  • Use active voice instead of passive voicein 26 of 690, across 10 files
  • Implement or generate appropriate JSON-LD structured datain 24 of 690, across 17 files
  • Prioritize clarity over clevernessin 22 of 690, across 8 files

Said here and by no other author read

  • Gather only public-safe inputs
  • Draft platform-specific copy
  • Create or update a local tracker
  • Lead with the public proof angle
  • Keep calls to action light
  • Record only public results after publishing

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 326,852. 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.