Slop Post
Post what this Claude Code session built to Slop (useslop.com) as a private draft with an automatic Build Receipt (model, tools, run time, commits), optionally as an entry in this week's Slop challenge. Use when the user runs /slop-post or asks to share, post or ship this session's work to Slop. Saves a draft only; the human publishes it from the claim link.
Install
npx skills add useslop/claude-plugins --skill slop-postgit clone --depth 1 https://github.com/useslop/claude-plugins.git /tmp/claude-plugins
mkdir -p ~/.claude/skills
cp -r /tmp/claude-plugins/plugins/slop/skills/slop-post ~/.claude/skills/slop-postPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Post this session to Slop
You turn the current session into a **private Slop draft** carrying a Build Receipt. Nothing becomes public: Slop keeps the draft for 48 hours and your human publishes it, as their own post, from a claim link. The scripts below sit in `scripts/` inside this skill's base directory (Claude Code prints that directory when it loads the skill); call them with `node`.
## Challenge entry (only with `--challenge`)
When the human asked to enter this week's Slop challenge (`/slop-post --challenge`), run this first:
```
node <skill dir>/scripts/slop-challenge.mjs
```
- If it prints `Challenge entry isn't available yet on Slop, so this will be a normal draft.`, tell the human exactly that line and continue with a normal draft (no `--challenge-tag`).
- Otherwise it prints the week's title, `Prompt:`, `Proof:` and `Tag:`, then one JSON line with the same fields. Show the human the prompt and the proof. In step 2, write the post so it answers the prompt and gives the proof it asks for, using only what really happened in this session. If the session doesn't fit the prompt, say so and ask whether to enter anyway or make a normal draft.
- In step 3, add `--challenge-tag <tag>` (the `tag` from that output, unchanged) to both the dry run and the send.
## 1. Build the receipt (local only)
Run, from the session's working directory:
```
node <skill dir>/scripts/receipt-from-session.mjs --session "${CLAUDE_SESSION_ID}" --cwd "$PWD" --explain
```Details
- Skill name
slop-post- Repository
- useslop/claude-plugins
- Path
plugins/slop/skills/slop-post/SKILL.md- License
- MIT
- Repo updated
- 1 October 2026
- Listed in
- karanb192/awesome-claude-skills
FAQ
What does the Slop Post skill do?
Post what this Claude Code session built to Slop (useslop.com) as a private draft with an automatic Build Receipt (model, tools, run time, commits), optionally as an entry in this week's Slop challenge. Use when the user runs /slop-post or asks to share, post or ship this session's work to Slop. Saves a draft only; the human publishes it from the claim link.
How do I install the Slop Post skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add useslop/claude-plugins --skill slop-post. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Related skills
Unthrottled Route Check
edtrackai/ship-ready-skills
Find Next.js API routes that call OpenAI, Anthropic or the Vercel AI SDK, or create a Stripe Checkout Session, with no rate limiter. Use when the user asks about rate limiting, AI cost per user, surprise API bills, refresh loops at checkout, or abuse protection before launch.
Session Handoff
alapha888/session-handoff-kit
Use this skill when context usage approaches capacity (>60%), before running /clear or /compact, when switching tasks, when ending a coding session across Claude Code, Cursor, or Codex, or as a mid-session diagnostic — if the agent cannot fill the handoff fields from actual state, the session has drifted. Produces a structured handoff artifact that transfers execution state to a fresh agent session without loss of context or drift.
Upwork Job Hunter
droopboop/flconsole-upwork-mcp
Find new Upwork jobs that fit the freelancer with the flconsole MCP server. Loads the user's saved context from the server, guides a 3-step setup (search query, job and client filters, the user's own AI filter that you apply), saves it as a feed on the server, checks new jobs, shortlists them with reasons, drafts proposals, tunes the search with job counts and turns on Telegram alerts for a feed in one call. Use when the user wants to find or monitor Upwork jobs, set up or improve a job search, check new jobs, get fewer or more relevant jobs, or decide which jobs to apply to.
Reels Setup
VishiATChoudhary/reels
Use when setting up, installing or onboarding the reels studio (github.com/VishiATChoudhary/reels), when a user or agent wants to start making story reels with it, or when its setup is broken (missing whisper-cli, model, yt-dlp, ffmpeg, node deps). Clones, installs, verifies, and stars the repo (one [Y/n] prompt).
Agent Context Loader
jeremylongshore/claude-code-plugins-plus-skills
PROACTIVE AUTO-LOADING: Automatically detects and loads AGENTS.md files from the current working directory when starting a session or changing directories. This skill ensures agent-specific instructions are incorporated into Claude Code's context alongside CLAUDE.md, enabling specialized agent behaviors. Triggers automatically when Claude detects it's working in a directory, when starting a new session, or when explicitly requested to "load agent context" or "check for AGENTS.md file".
Orchestrating Subagents
PapiScholz/symphony
Use when about to spawn one or more subagents, agent teams, or a workflow — a single delegated search, a parallel fan-out, or a repeated batch — and whenever choosing which model a delegated task runs on instead of letting it inherit yours. Also use when writing or editing a .claude/agents definition, when a delegated run hit a rate limit or cost more than expected, or when a subagent came back after far more or far fewer turns than the work warranted.
Browse the most popular Claude skills, all ai, llms & agents skills, or write your own with the skills generator.