agentleFS
dkadtsdkadts/landing-kit-building/.claude/skills/inbox/SKILL.md

inbox

Skill2 starsChanged 3 months agoMITView on GitHub

Sorts client materials from inbox/. Verifies compliance with content-pipeline requirements (naming, formats, sizes). Produces a "ready / needs rework" report.

28 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use journey, tailor and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • MeshJSSkill

    journey

    Create session learning logs that persist institutional memory across Claude Code sessions.

    Also in 3 projects that use this

  • ledqSkill

    tailor

    Tailor the resume to one job posting. Give it a URL, paste the posting (or refer to one pasted earlier in this chat), or point at a saved application folder; it resolves the JD and runs the tailor-pipeline workflow end to end.

    Also in 3 projects that use this

  • gaiaaiagentSkill

    weekly

    Generate a weekly digest rolling up dailies into higher-level pattern analysis

    Also in 3 projects that use this

  • endlessblinkSkill

    task

    Create a new task in MASTER_PLAN.md with auto-generated sequential IDs. Supports TASK, BUG, FEATURE, and INQUIRY types. Triggers on "/task", "add task", "new task", "create task", "track this".

    Also in 3 projects that use this

  • AnthropicSkill

    update

    Sync tasks and refresh memory from your current activity. Use when pulling new assignments from your project tracker into TASKS.md, triaging stale or overdue tasks, filling memory gaps for unknown people or projects, or running a comprehensive scan to catch todos buried in chat and email.

    Also in 4 projects that use this

  • genomewalkerSkill

    tasks

    Browse and resume tasks, threads, and background jobs across sessions

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

6 rules. 0 are common, 3 are distinctive, and 3 are very specific to this project.

  • 0

    Common

    Most of the 23 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 3

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    After a new batch arrives (top-up).

    line 13
  2. Distinctive:

    Verify: naming ASCII? correct format?

    line 24
  3. Very specific:

    No embedded raster (no <image> inside).

    line 47
  4. Very specific:

    If notes contain URLs — offer to move them into references/ by aspect.

    line 97
  5. Distinctive:

    Do not convert files here: Only validate and sort.

    line 101
  6. Very specific:

    Do not delete reject files: Only mark in the report — user decides.

    line 103

“Common” is measured: kept by at least 6 in 10 of the 23 edited versions of this file we could read. “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

/inbox

First pass over client materials. Does not convert (that's /media), does not analyze text (that's /copy-analyze) — only sorts and validates.

When to use

  • Client says "materials uploaded".
  • After a new batch arrives (top-up).

Process

Step 1. Read brief/08-content-pipeline.md Load requirements: naming, formats, sizes.

Step 2. Walk inbox/ folders

For each folder (texts/, media/photos/, media/videos/, brand/logo/, brand/fonts/, notes/):

  • List files.
  • Verify: naming ASCII? correct format? size within limits?
  • Mark: ✅ OK / ⚠️ warning / ❌ reject.

Step 3. Specific checks

texts/:

  • UTF-8?
  • Section headings present (# Hero, # Offer)?

media/photos/:

  • Min side ≥ 2400px (read via image tool or identify).
  • sRGB (not Adobe RGB — otherwise color shift in the browser).
  • ASCII filenames.
  • No IMG_1234.jpg.

media/videos/:

  • 1080p+.
  • Bitrate ≤ 20 Mbps.
  • H.264 in MP4 (not HEVC — poor browser support).

brand/logo/:

  • SVG only.
  • Text outlined (check: is there a <text> tag inside SVG — if yes, NOT outlined).
  • No embedded raster (no <image> inside).

brand/fonts/:

  • .woff2 only.
  • LICENSE.txt present.

notes/:

  • List with type (audio / image / md / other).
  • Transcribe voice notes (if possible).

Step 4. Produce the report

Create/update inbox/inbox-report.md:

# Inbox report — 2026-08-08

## Overall
- Files total: N
- OK: N | Warning: N | Reject: N

## texts/
- `copy.md` — ✅ OK (UTF-8, 5 sections)
- `about.docx` — ⚠️ convert to MD

## media/photos/
- `hero-01.jpg` — ✅ 3600×2400, sRGB
- `IMG_1234.jpg` — ❌ rename to ASCII
- `founder.tif` — ⚠️ 6000×4000 > 6000px — will be cropped

## brand/logo/
- `logo.svg` — ❌ text not outlined (found <text>)

## Summary for the client
### Ready
- Texts can go to /copy-analyze
- Hero photo (after rename)

### Needs rework
- 3 photos: rename
- Logo: outline (in Illustrator: Type → Create Outlines)
- `about.docx`: convert to MD

## Next
- Wait for client rework
- OR if user says "ship with what we have" — run /media on ok-files and /copy-analyze on texts

Step 5. Extract links from notes/

If notes contain URLs — offer to move them into references/ by aspect.

Rules

  • Do not convert files here. Only validate and sort.
  • Do not complain if materials are thin. Just report "we have X, for a full landing we need Y".
  • Do not delete reject files. Only mark in the report — user decides.

Next

  • /copy-analyze on texts.
  • /media on photos and videos.

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.