跳至正文
OpenAgentSkill
浏览已开放 · 目录记录日期 2026-11-21 · 自动更新和账户服务暂时关闭。
开发与测试

anti-slop-personal-brand

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.

Joy T <101039451+FAIRY123456789@users.noreply.github.com> · 已有静态检查记录

安装与使用

运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。

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

技能说明


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.