Skip to content
Back to skills

Anti Slop Personal Brand

ASecurity

Audit a resume, GitHub profile, personal website, portfolio, bio, README, or project list for generic AI slop, stale student-project signals, unsupported grand claims, fragmented identity, weak proof, and outdated first-screen positioning. Use when the user wants a personal brand that feels current, specific, technically credible, and earned rather than over-designed or stuffed with fashionable keywords.

  • 96 stars
  • 0 votes
  • 0 copies
  • 1 view
  • Added September 30, 2026
ai-agentsgit

Security analysis

A100/100

Pro scans all 3 files and shows the line behind each finding

Scanned September 30, 2026

npx -y skills add FAIRY123456789/human-edge-agent-skills --skill anti-slop-personal-brand --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Anti Slop Personal Brand?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Anti Slop Personal Brand
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/fairy123456789-anti-slop-personal-brand/badge)](https://www.skillsdirectory.com/skills/fairy123456789-anti-slop-personal-brand)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: anti-slop-personal-brand
description: "Audit a resume, GitHub profile, personal website, portfolio, bio, README, or project list for generic AI slop, stale student-project signals, unsupported grand claims, fragmented identity, weak proof, and outdated first-screen positioning. Use when the user wants a personal brand that feels current, specific, technically credible, and earned rather than over-designed or stuffed with fashionable keywords."
license: MIT
metadata:
  author: Joy T <101039451+FAIRY123456789@users.noreply.github.com>
  tags:
    - personal-branding
    - portfolio
    - writing
---

# Anti-Slop Personal Brand

Make the first screen look current, real, and earned.

## Workflow

1. Identify the intended audience and next action: recruiter, founder, research collaborator, customer, investor, or community user.
2. Inventory every visible signal: title, bio, first-screen projects, metrics, repos, writing, awards, skills, social proof, and contact path.
3. Score each item on:
   - relevance;
   - recency;
   - proof strength;
   - distinctiveness;
   - explanation cost.
4. Detect slop signals using `references/slop-signals.md`.
5. Remove or demote low-proof items before adding new visual decoration.
6. Put the strongest current work near the top. Older work can remain as evidence without defining the current identity.
7. Replace generic positioning with a narrow sentence that connects capability + problems + proof.
8. For GitHub, prefer a canonical flagship repository, pinned proof-producing work, clear README, topics, and deep links to individual Skills or projects.
9. For resumes, never add trendy keywords without interview-ready evidence.
10. End with a first-screen mock hierarchy and a “delete / demote / keep / promote” table.

## Output

- current impression in 15 seconds;
- strongest signals;
- slop and stale signals;
- delete, demote, keep, and promote table;
- new first-screen hierarchy;
- one-sentence positioning;
- missing proof needed for the next upgrade.

Files in this skill

  • README.md1 KB
  • SKILL.md2 KB
  • references/slop-signals.md1 KB

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.