Blogger Distiller
otter1101/blogger-distiller
A skill your agent uses when the user wants to analyze or distill a blogger/account on Xiaohongshu or Douyin, benchmark a target creator, or diagnose their own content strategy.
Manages newsroom editorial workflows. An agent skill from jamditis/claude-skills-journalism.
Install Editorial Workflow
$ npx skills add jamditis/claude-skills-journalism --skill editorial-workflow -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install jamditis/claude-skills-journalism editorial-workflow --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/jamditis/claude-skills-journalism.git skills-src && mkdir -p .claude/skills && cp -r skills-src/journalism-core/skills/editorial-workflow .claude/skills/editorial-workflow && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "editorial-workflow" agent skill from https://github.com/jamditis/claude-skills-journalism/tree/master/journalism-core/skills/editorial-workflow into .claude/skills/editorial-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "editorial-workflow", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/jamditis/claude-skills-journalism/tree/master/journalism-core/skills/editorial-workflowType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add jamditis/claude-skills-journalism --skill editorial-workflow -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install jamditis/claude-skills-journalism editorial-workflow --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jamditis/claude-skills-journalism.git skills-src && mkdir -p .agents/skills && cp -r skills-src/journalism-core/skills/editorial-workflow .agents/skills/editorial-workflow && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "editorial-workflow" agent skill from https://github.com/jamditis/claude-skills-journalism/tree/master/journalism-core/skills/editorial-workflow into .agents/skills/editorial-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "editorial-workflow", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add jamditis/claude-skills-journalism --skill editorial-workflow -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install jamditis/claude-skills-journalism editorial-workflow --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jamditis/claude-skills-journalism.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/journalism-core/skills/editorial-workflow .cursor/skills/editorial-workflow && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "editorial-workflow" agent skill from https://github.com/jamditis/claude-skills-journalism/tree/master/journalism-core/skills/editorial-workflow into .cursor/skills/editorial-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "editorial-workflow", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/jamditis/claude-skills-journalism.git --path journalism-core/skills/editorial-workflow--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add jamditis/claude-skills-journalism --skill editorial-workflow -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install jamditis/claude-skills-journalism editorial-workflow --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jamditis/claude-skills-journalism.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/journalism-core/skills/editorial-workflow .gemini/skills/editorial-workflow && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "editorial-workflow" agent skill from https://github.com/jamditis/claude-skills-journalism/tree/master/journalism-core/skills/editorial-workflow into .gemini/skills/editorial-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "editorial-workflow", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install jamditis/claude-skills-journalism editorial-workflowInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add jamditis/claude-skills-journalism --skill editorial-workflow -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/jamditis/claude-skills-journalism.git skills-src && mkdir -p .github/skills && cp -r skills-src/journalism-core/skills/editorial-workflow .github/skills/editorial-workflow && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "editorial-workflow" agent skill from https://github.com/jamditis/claude-skills-journalism/tree/master/journalism-core/skills/editorial-workflow into .github/skills/editorial-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "editorial-workflow", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add jamditis/claude-skills-journalism --skill editorial-workflow -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install jamditis/claude-skills-journalism editorial-workflow --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jamditis/claude-skills-journalism.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/journalism-core/skills/editorial-workflow .opencode/skills/editorial-workflow && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "editorial-workflow" agent skill from https://github.com/jamditis/claude-skills-journalism/tree/master/journalism-core/skills/editorial-workflow into .opencode/skills/editorial-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "editorial-workflow", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
editorial-workflow- GitHub stars
- 416
- Token cost
- ~2.5k tokens
- SKILL.md length
- 283 words
- Files
- 2
- Skills in repo
- 53
- Repo updated
- First seen
- Licence
- MIT
At a glance
Manages newsroom editorial workflows. An agent skill from jamditis/claude-skills-journalism.
- Works in 4 steps: Notify immediately - Don't wait until… → Explain briefly - What's blocking progress → Propose new deadline - Realistic estimate → …
- Tracking assignments
- SKILL.md covers When to use, Story status taxonomy, Story assignment tracking and Editorial calendar, plus 4 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Editorial Workflow is an agent skill from jamditis/claude-skills-journalism. Manages newsroom editorial workflows. Use when tracking assignments, managing deadlines, or coordinating editorial calendars.
Its SKILL.md is about 2.5k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files (for example `agents/openai.yaml`).
It sits in Writing & Content, covering Content strategy. The repository describes itself as: Claude Code skills for journalism, media, and academia - verification, FOIA, data journalism, academic writing, and more. The licence is MIT.
When your agent uses it
- Tracking assignments
- Managing deadlines
- Coordinating editorial calendars
Example prompts
- “Use the editorial-workflow skill to manage newsroom editorial workflows. An agent skill from jamditis/claude-skills-journalism”
- “/editorial-workflow”
Workflow steps
4 steps, taken from the first numbered list in SKILL.md.
- Notify immediately - Don't wait until the deadline passes
- Explain briefly - What's blocking progress
- Propose new deadline - Realistic estimate
- Offer alternatives - Shorter version? Different angle?
What it can do on your machine
Read from SKILL.md and the folder at commit e3e2172. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Editorial Workflow loads about 2.5k tokens when it runs. Until then it costs about 36 tokens; SKILL.md has 283 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from jamditis/claude-skills-journalism at commit e3e2172, republished under its MIT licence (© jamditis). 283 words, ~2,459 tokens.
Download SKILL.mdSave it as
.claude/skills/editorial-workflow/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- editorial-workflow
- description
- Manages newsroom editorial workflows. Use when tracking assignments, managing deadlines, or coordinating editorial calendars.
Editorial workflow management
Newsrooms run on systems. This skill provides templates and processes for tracking stories, managing deadlines, and coordinating between reporters and editors.
When to use
- Setting up story tracking systems
- Creating editorial calendars
- Establishing assignment and handoff protocols
- Managing multiple stories and deadlines
- Training new editors on workflow
Story status taxonomy
Standard statuses
| 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 |
Status flow
Pitch → Assigned → Reporting → Draft → Edit → Revision (loop) → Copy → Final → Scheduled → Published
↓
Hold/KillStory assignment tracking
Assignment record template
## 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] |Assignment handoff checklist
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 helpEditorial calendar
Calendar template
## 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] |Planning meeting template
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 management
Deadline types
| 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 |
Deadline tracking template
## 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] | ☐ |Missed deadline protocol
When a deadline is at risk:
- Notify immediately - Don't wait until the deadline passes
- Explain briefly - What's blocking progress
- Propose new deadline - Realistic estimate
- 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]Edit handoff protocols
Reporter → Editor
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
- [ ] [Outstanding item]
- [ ] [Waiting for source callback]
### Questions for editor
- [Question about structure, angle, etc.]
### Source notes
[Any attribution issues, off-record info, etc.]
### Multimedia status
- Photos: [ready/pending/needed]
- Graphics: [ready/pending/needed]Editor → Reporter
When returning for revision:
## Edit notes: [story title]
**Overall:** [brief assessment - on track, needs work, etc.]
### Structural changes needed
- [Major reorg, missing elements, etc.]
### Specific fixes
- Line [X]: [issue/change]
- Line [X]: [issue/change]
### Questions to resolve
- [Question requiring reporter input]
### Deadline for revisions
[date/time]
### Discussion needed?
[Yes - let's talk before you revise / No - changes are clear]Publication checklist
Pre-publish checklist
## Pre-publish: [story title]
### Content
- [ ] Headline is accurate and compelling
- [ ] Dek/subhead summarizes well
- [ ] Lede works
- [ ] All facts verified
- [ ] All sources attributed correctly
- [ ] Quotes are accurate
- [ ] Numbers double-checked
### Style
- [ ] AP Style applied
- [ ] Consistent voice throughout
- [ ] No typos or grammatical errors
- [ ] Appropriate length
### Legal/Ethics
- [ ] No defamation risk
- [ ] Sources of comment contacted
- [ ] Corrections from previous versions applied
- [ ] Embargoes respected
### Multimedia
- [ ] Photos have captions and credits
- [ ] Alt text added
- [ ] Video/audio plays correctly
- [ ] Graphics are accurate
### Metadata
- [ ] SEO headline filled
- [ ] Meta description written
- [ ] Tags/categories applied
- [ ] Author byline correct
- [ ] Publication date/time set
### Final sign-off
- [ ] Reporter reviewed final
- [ ] Editor approved
- [ ] Copy editor signed offPost-publish checklist
## Post-publish: [story title]
### Immediate (within 1 hour)
- [ ] Story displays correctly
- [ ] Links work
- [ ] Images load
- [ ] No obvious errors
- [ ] Social posts scheduled/published
### Same day
- [ ] Monitor comments/feedback
- [ ] Watch for corrections needed
- [ ] Track initial metrics
- [ ] Respond to any issues
### Follow-up
- [ ] Note any updates needed
- [ ] Document corrections made
- [ ] Capture reader response
- [ ] Plan follow-up stories if warrantedWorkflow documentation
Process documentation template
For documenting your newsroom's workflows:
## Workflow: [Name of process]
### Purpose
[What this workflow accomplishes]
### When to use
[Triggers for this workflow]
### Roles involved
| Role | Responsibility |
|------|----------------|
| [Role] | [What they do] |
### Process steps
**Step 1: [Name]**
- Owner: [role]
- Action: [what happens]
- Output: [what's produced]
- Next: [what triggers next step]
**Step 2: [Name]**
[same format]
### Tools used
- [Tool]: [what it's used for]
### Templates/Forms
- [Link to templates]
### Exceptions
- [When normal process doesn't apply]
- [What to do instead]
### Escalation
- [When to escalate]
- [Who to contact]Onboarding new staff
## Editorial workflow onboarding
### Day 1
- [ ] Access to CMS granted
- [ ] Added to editorial chat/channels
- [ ] Received style guide
- [ ] Introduced to direct editor
### Week 1
- [ ] Shadow experienced reporter
- [ ] Review workflow documentation
- [ ] Complete first assignment (low-stakes)
- [ ] Learn deadline expectations
### Month 1
- [ ] Independently handle standard assignments
- [ ] Know escalation paths
- [ ] Understand publication calendar
- [ ] Comfortable with all tools
### Key contacts
| Need | Contact |
|------|---------|
| Assignment questions | [name] |
| Technical issues | [name] |
| Editorial disputes | [name] |
| HR/Admin | [name] |Good workflows disappear. You only notice them when they break.
© jamditis, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 1 other file in journalism-core/skills/editorial-workflow of jamditis/claude-skills-journalism.
- SKILL.md
- agents/openai.yaml
Open the folder on GitHubat commit e3e2172
Compare with similar skills
Editorial Workflow next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Editorial Workflow this skilljamditis/claude-skills-journalism | 416 | — | ~2.5k | Automated safety check: Pass | MIT | |
| Blogger Distillerotter1101/blogger-distiller | 693 | — | ~3.8k | Automated safety check: Notes | MIT | |
| Linkedin Content Plannersergebulaev/linkedin-skills | 4.3k | 1 repos | ~2.1k | Automated safety check: Pass | MIT | |
| Blog Post Draftingluongnv89/claude-howto | 42k | — | ~2.1k | Automated safety check: Pass | MIT | |
| Benchmark Account ImporterXBuilderLAB/cheat-on-content | 7.2k | 1 repos | ~2.3k | Automated safety check: Notes | MIT | |
| WeChat Hot Article AnalysisSpaceZephyr/creator-buddy | 1.6k | — | ~847 | Automated safety check: Pass | None |
Similar skills
Linkedin Content Planner
sergebulaev/linkedin-skills
Generate a 7-day LinkedIn content plan from a theme, audience, and pillars.
Blog Post Drafting
luongnv89/claude-howto
Guides drafting a blog post from an idea and optional source material: research, brainstorming, outlining and version-tracked drafts, with user approval at each step.
Benchmark Account Importer
XBuilderLAB/cheat-on-content
Imports scripts and engagement numbers from an account you want to emulate, then extracts content patterns and starting scoring signals from them.
WeChat Hot Article Analysis
SpaceZephyr/creator-buddy
Fetches hot WeChat Official Account articles by sector or keywords and produces a data file and an HTML report with rankings, style patterns and writing references.
Brand Voice Content Creator
davila7/claude-code-templates
Analyzes a brand's existing writing to lock in a consistent voice, then builds SEO blog posts and platform-specific social content around it.
More from jamditis/claude-skills-journalism
All 53 skills in this repoWeb Design Picker
jamditis/claude-skills-journalism
A skill your agent uses when creating distinct website directions, a client review picker, asset catalog, previews, and Cloudflare-ready handoffs.
Okf Wiki
jamditis/claude-skills-journalism
Builds an Open Knowledge Format (OKF) knowledge base from existing docs, notes, or a repo.
Private Secret Scanning
jamditis/claude-skills-journalism
Local Gitleaks scans for staged changes, push ranges, and full history in private repos, with redacted reports.
Data Journalism
jamditis/claude-skills-journalism
Acquire, clean, analyze, verify, visualize, and explain data for journalism.
Document Design
jamditis/claude-skills-journalism
Creates print-ready HTML that exports to PDF. An agent skill from jamditis/claude-skills-journalism.
Using Superjawn
jamditis/claude-skills-journalism
Establishes how to find and use skills, requiring Skill tool invocation before any response.
Related
Categories
Questions about Editorial Workflow
What does Editorial Workflow do?
Manages newsroom editorial workflows. An agent skill from jamditis/claude-skills-journalism. Editorial Workflow is an agent skill from jamditis/claude-skills-journalism. Manages newsroom editorial workflows.
When should I use Editorial Workflow?
Editorial Workflow fits situations like: tracking assignments; managing deadlines; coordinating editorial calendars.
How do I install Editorial Workflow in Claude Code?
Run `npx skills add jamditis/claude-skills-journalism --skill editorial-workflow -a claude-code`. Or copy the skill folder (journalism-core/skills/editorial-workflow in jamditis/claude-skills-journalism) into .claude/skills/editorial-workflow in your project. Claude Code loads it when a task matches its description.
How do I install Editorial Workflow in Codex?
Run `npx skills add jamditis/claude-skills-journalism --skill editorial-workflow -a codex`. Or copy the skill folder (journalism-core/skills/editorial-workflow in jamditis/claude-skills-journalism) into .agents/skills/editorial-workflow in your project. Codex loads it when a task matches its description.
Can I use Editorial Workflow in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add jamditis/claude-skills-journalism --skill editorial-workflow -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/editorial-workflow, .gemini/skills/editorial-workflow, .github/skills/editorial-workflow and .opencode/skills/editorial-workflow in your project.
What does Editorial Workflow need to run?
SKILL.md names no scripts, command-line tools or credentials: Editorial Workflow is instructions for the agent only.
Does Editorial Workflow access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Editorial Workflow safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Editorial Workflow use?
Editorial Workflow is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Editorial Workflow use?
About 2.5k tokens (SKILL.md is roughly 9.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Editorial Workflow?
Skills that share tags, products or a category with Editorial Workflow: Blogger Distiller (otter1101/blogger-distiller, 693 stars), Linkedin Content Planner (sergebulaev/linkedin-skills, 4.3k stars), Blog Post Drafting (luongnv89/claude-howto, 42k stars) and Benchmark Account Importer (XBuilderLAB/cheat-on-content, 7.2k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Editorial Workflow?
jamditis (a GitHub user) maintains it in jamditis/claude-skills-journalism, which has 416 GitHub stars. The repository holds 53 skills in this directory. The repository was last updated on October 4, 2026.
Source: jamditis/claude-skills-journalism on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.