accessibility-complian…
Web accessibility patterns for news and academic sites. Use for WCAG audits, alt text, accessible data viz, and assistive tech.
Manages newsroom editorial workflows. Use when tracking assignments, managing deadlines, or coordinating editorial calendars.
$ npx -y skills add jamditis/claude-skills-journalism --skill editorial-workflow --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/editorial-workflowContext preview
The summary Claude sees to decide when to auto-load this skill.
Manages newsroom editorial workflows. Use when tracking assignments, managing deadlines, or coordinating editorial calendars.
name: editorial-workflow description: Manages newsroom editorial workflows. Use when tracking assignments, managing deadlines, or coordinating editorial calendars.
Newsrooms run on systems. This skill provides templates and processes for tracking stories, managing deadlines, and coordinating between reporters and editors.
| Status | Meaning | Owner | |--------|---------|-------| | **Pitch** | Idea submitted, awaiting approval | Reporter | | **Assigned** | Approved, reporter working | Reporter | | **Reporting** | Active reporting in progress | Reporter | | **Draft** | First draft submitted | Editor | | **Edit** | Editor making changes | Editor | | **Revision** | Back with reporter for changes | Reporter | | **Copy** | Copy editing stage | Copy editor | | **Final** | Ready for publication | Editor | | **Scheduled** | Queued for specific date | System | | **Published** | Live | Complete | | **Hold** | Paused, not abandoned | Editor | | **Kill** | Story abandoned | Editor |
Pitch → Assigned → Reporting → Draft → Edit → Revision (loop) → Copy → Final → Scheduled → Published
↓
Hold/Kill## Story: [Slug/working title] ### Assignment details - **Reporter:** [name] - **Assigning editor:** [name] - **Date assigned:** [date] - **Deadline:** [date/time] - **Target publication:** [outlet/section] ### Story specs - **Format:** [brief, feature, enterprise, etc.] - **Word count:** [target] - **Multimedia:** [photos, video, graphics needed] - **Sources required:** [minimum sources] ### The assignment [What the story is, angle, key elements to include] ### Key contacts [Sources to interview, PR contacts, experts] ### Background/resources [Links to previous coverage, documents, data] ### Budget line [One sentence for editorial budget meetings] ### Status history | Date | Status | Notes | |------|--------|-------| | [date] | Assigned | | | [date] | [status] | [note] |
When assigning a story:
## Assignment handoff ### From editor to reporter - [ ] Story scope clearly defined - [ ] Deadline confirmed - [ ] Word count/format specified - [ ] Key sources identified - [ ] Background materials shared - [ ] Multimedia needs discussed - [ ] Questions answered ### Reporter confirms - [ ] Deadline is realistic - [ ] Have access to necessary sources - [ ] Understand the angle - [ ] Know who to ask for help
## Editorial calendar: [Week/Month of Date] ### Monday [date] | Time | Story | Reporter | Status | Notes | |------|-------|----------|--------|-------| | AM | [story] | [name] | [status] | | | PM | [story] | [name] | [status] | | ### Tuesday [date] [same format] ### Evergreen queue | Story | Reporter | Ready date | Notes | |-------|----------|------------|-------| | [story] | [name] | [date] | [can run anytime after this] | ### Upcoming (next 2 weeks) | Story | Reporter | Target date | Status | |-------|----------|-------------|--------| | [story] | [name] | [date] | [status] |
For weekly/daily editorial meetings:
## Editorial meeting: [date] ### Today's lineup | Story | Reporter | Status | Publish time | Notes | |-------|----------|--------|--------------|-------| | [story] | [name] | [status] | [time] | | ### Tomorrow's lineup [same format] ### In progress (due this week) | Story | Reporter | Due | Status | Blockers | |-------|----------|-----|--------|----------| | [story] | [name] | [date] | [status] | [any issues] | ### Pipeline (next 2+ weeks) | Story | Reporter | Target | Status | |-------|----------|--------|--------| | [story] | [name] | [date] | [status] | ### Discussion items - [Topic 1] - [Topic 2] ### Action items - [ ] [Action] - [Owner] - [Deadline]
| Deadline | Purpose | Typical lead time | |----------|---------|-------------------| | **Reporting** | Complete interviews/research | 2-5 days before draft | | **First draft** | Submit to editor | 24-48 hours before edit | | **Final draft** | After revisions | 12-24 hours before copy | | **Art/photos** | Visuals ready | Same as first draft | | **Copy edit** | Language/style review | 4-8 hours before publish | | **Publish** | Goes live | Set time |
## Story: [title] **Final publish deadline:** [date/time] ### Working backward | Milestone | Deadline | Status | |-----------|----------|--------| | Reporting complete | [date] | ☐ | | First draft due | [date] | ☐ | | Art/photos due | [date] | ☐ | | Edit complete | [date] | ☐ | | Revisions due | [date] | ☐ | | Copy edit complete | [date] | ☐ | | Final review | [date] | ☐ | | Schedule/publish | [date] | ☐ |
When a deadline is at risk:
1. **Notify immediately** - Don't wait until the deadline passes 2. **Explain briefly** - What's blocking progress 3. **Propose new deadline** - Realistic estimate 4. **Offer alternatives** - Shorter version? Different angle?
## Deadline alert **Story:** [title] **Original deadline:** [date/time] **Issue:** [what's blocking] **New proposed deadline:** [date/time] **Impact:** [what this affects] **Alternatives:** [options if any]
When submitting draft:
## Draft submission: [story title] **Draft location:** [link/file] **Word count:** [count] ### What's in the draft - [Key points covered] ### What's still needed - [ ] [Ou
A collection of Agent Skills for journalists, researchers, academics, media professionals, and communications practitioners. The same repository serves Claude Code and Codex while keeping Claude-only commands, agents, and hooks clearly labeled.
Repo: jamditis/claude-skills-journalism
Web accessibility patterns for news and academic sites. Use for WCAG audits, alt text, accessible data viz, and assistive tech.
Scans the session for lessons and workflows, then proposes scoped CLAUDE.md edits. Use for save this lesson or add to context.
Manages attention and evidence in long agent sessions. Use for lost instructions, dropped evidence, or large multi-agent contexts.
Directs the current request through configured lower-tier agents. Use only for explicit /director or /dev-toolkit:director invocation.
Electron desktop apps with React, TypeScript, and Vite. Use for IPC, window/tray, PTY terminals, WebRTC, and packaging.
Remote JavaScript console and debugging on mobile. Use for phone/tablet console errors, responsive testing, Eruda, and vConsole.