agentleFS
namddpnamddp/social-media-agent-skills/skills/social-source-miner/SKILL.md

social-source-miner

Skill0 starsChanged 3 months agoMITView on GitHub

Turn notes, changelogs, transcripts, or research into a traceable source brief for social content.

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 4 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    No claim appears without a traceable source or an unverified label.

    line 42
  2. Distinctive:

    Do not browse private locations or files outside the user-provided scope.

    line 49
  3. Distinctive:

    Never convert assumptions into facts.

    line 51
  4. Distinctive:

    Stop at the source brief; do not draft or publish automatically.

    line 52

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Social Source Miner

Purpose

Extract useful, defensible social angles from real source material before drafting begins.

Inputs

  • One or more user-approved source documents
  • Target audience and campaign objective
  • Optional time window and topics to exclude

Workflow

  1. List the sources and label their reliability.
  2. Extract claims, examples, decisions, mistakes, and surprising details.
  3. Attach each claim to a source location or mark it unverified.
  4. Rank angles by usefulness, specificity, novelty, and evidence strength.
  5. Separate facts from interpretation and opinion.
  6. Recommend the best three angles with a reason for each.

Output

# Source brief
## Source inventory
## Verified claims
| Claim | Source | Confidence |
## Human stories and examples
## Candidate angles
## Claims requiring verification
## Recommended lead angle

Quality gate

  • No claim appears without a traceable source or an unverified label.
  • Recommendations contain concrete detail, not generic topic labels.
  • The brief preserves meaningful disagreement between sources.
  • The lead angle matches the stated audience and objective.

Safety

  • Do not browse private locations or files outside the user-provided scope.
  • Redact customer, employee, and partner information unless approved for use.
  • Never convert assumptions into facts.
  • Stop at the source brief; do not draft or publish automatically.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.