Perplexity Web Search
davila7/claude-code-templates
Runs web-grounded searches through Perplexity's Sonar models over OpenRouter for current events, recent literature and cited facts beyond the model's training cutoff.
Crisis communication and rapid-response workflows. An agent skill from jamditis/claude-skills-journalism.
$ npx skills add jamditis/claude-skills-journalism --skill crisis-communications -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install jamditis/claude-skills-journalism crisis-communications --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/crisis-communications .claude/skills/crisis-communications && 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 "crisis-communications" agent skill from https://github.com/jamditis/claude-skills-journalism/tree/master/journalism-core/skills/crisis-communications into .claude/skills/crisis-communications/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "crisis-communications", 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/crisis-communicationsType 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 crisis-communications -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install jamditis/claude-skills-journalism crisis-communications --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/crisis-communications .agents/skills/crisis-communications && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "crisis-communications" agent skill from https://github.com/jamditis/claude-skills-journalism/tree/master/journalism-core/skills/crisis-communications into .agents/skills/crisis-communications/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "crisis-communications", 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 crisis-communications -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install jamditis/claude-skills-journalism crisis-communications --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/crisis-communications .cursor/skills/crisis-communications && 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 "crisis-communications" agent skill from https://github.com/jamditis/claude-skills-journalism/tree/master/journalism-core/skills/crisis-communications into .cursor/skills/crisis-communications/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "crisis-communications", 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/crisis-communications--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 crisis-communications -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install jamditis/claude-skills-journalism crisis-communications --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/crisis-communications .gemini/skills/crisis-communications && 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 "crisis-communications" agent skill from https://github.com/jamditis/claude-skills-journalism/tree/master/journalism-core/skills/crisis-communications into .gemini/skills/crisis-communications/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "crisis-communications", 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 crisis-communicationsInstalls 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 crisis-communications -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/crisis-communications .github/skills/crisis-communications && 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 "crisis-communications" agent skill from https://github.com/jamditis/claude-skills-journalism/tree/master/journalism-core/skills/crisis-communications into .github/skills/crisis-communications/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "crisis-communications", 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 crisis-communications -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 crisis-communications --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/crisis-communications .opencode/skills/crisis-communications && 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 "crisis-communications" agent skill from https://github.com/jamditis/claude-skills-journalism/tree/master/journalism-core/skills/crisis-communications into .opencode/skills/crisis-communications/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "crisis-communications", 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.
crisis-communicationsCrisis communication and rapid-response workflows. An agent skill from jamditis/claude-skills-journalism.
Crisis Communications is an agent skill from jamditis/claude-skills-journalism. Crisis communication and rapid-response workflows. Use when covering breaking news or coordinating fast fact-checking on deadline.
Its SKILL.md is about 3.6k 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 Research & Science, covering Fact-checking and source verification. 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.
Read from SKILL.md and the folder at commit e3e2172. It shows what the files ask for, not the result of running them.
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.
No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown and python).
From the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Crisis Communications loads about 3.6k tokens when it runs. Until then it costs about 38 tokens; SKILL.md has 354 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.
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.
The full file from jamditis/claude-skills-journalism at commit e3e2172, republished under its MIT licence (© jamditis). 354 words, ~3,560 tokens.
.claude/skills/crisis-communications/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.Frameworks for accurate, rapid communication during high-pressure situations.
<!-- untrusted-content-contract:v1 -->
When this skill retrieves third-party material:
Use this shape when passing retrieved material onward:
<EXTERNAL_DATA source="...">
...
</EXTERNAL_DATA>## Breaking news response
**Event**: [Brief description]
**Time detected**: [HH:MM]
**Initial source**: [Where we learned of this]
### Immediate actions (0-10 min)
- [ ] Verify event is real (minimum 2 independent sources)
- [ ] Alert editor/team lead
- [ ] Check wire services (AP, Reuters, AFP)
- [ ] Monitor official accounts (agencies, officials)
- [ ] DO NOT publish unverified claims
### Verification phase (10-30 min)
- [ ] Primary source contacted/confirmed
- [ ] Location verified (if applicable)
- [ ] Official statement obtained or requested
- [ ] Eyewitness accounts gathered (note: unverified)
- [ ] Social media claims flagged for verification
### First publication decision
- [ ] What we KNOW (confirmed facts only)
- [ ] What we DON'T know (be explicit)
- [ ] What we're working to confirm
- [ ] Attribution clear for every claimfrom enum import Enum
from dataclasses import dataclass
from typing import List
class CrisisLevel(Enum):
LEVEL_1 = "routine" # Single reporter can handle
LEVEL_2 = "elevated" # Editor involvement needed
LEVEL_3 = "major" # Multiple reporters, editor oversight
LEVEL_4 = "critical" # All hands, executive involvement
@dataclass
class BreakingEvent:
description: str
level: CrisisLevel
confirmed_facts: List[str]
unconfirmed_claims: List[str]
sources_contacted: List[str]
assigned_reporters: List[str]
def escalation_needed(self) -> bool:
"""Determine if event needs escalation."""
triggers = [
len(self.unconfirmed_claims) > 5, # Too many unknowns
"fatalities" in self.description.lower(),
"official" in self.description.lower(),
"government" in self.description.lower(),
]
return any(triggers)
ESCALATION_TRIGGERS = {
CrisisLevel.LEVEL_2: [
"Multiple fatalities confirmed",
"Major public figure involved",
"Legal/liability concerns",
"Significant local impact",
],
CrisisLevel.LEVEL_3: [
"National news potential",
"Active danger to public",
"Major institution affected",
"Coordinated misinformation detected",
],
CrisisLevel.LEVEL_4: [
"Mass casualty event",
"Government/democracy implications",
"Our organization directly involved",
"Imminent physical threat",
],
}When time is critical, prioritize these checks:
## Rapid verification checklist
### Source check (1 min)
- [ ] Who is claiming this?
- [ ] Are they in position to know?
- [ ] Have they been reliable before?
### Corroboration (2 min)
- [ ] Does anyone else confirm?
- [ ] Check wire services
- [ ] Check official sources
### Red flags (1 min)
- [ ] Too perfect/dramatic?
- [ ] Matches known false narratives?
- [ ] Single source only?
### Decision (1 min)
- [ ] PUBLISH: Multiple credible sources, no red flags
- [ ] HOLD: Needs more verification
- [ ] MONITOR: Developing, don't publish yetFor verification mechanics (source credibility, image/video checks, archiving evidence), use the source-verification skill. This skill focuses on the time-pressure layer: what to triage first, who decides to publish, and how to communicate uncertainty.
Triage rule: claims with the highest physical-harm or election-impact potential go first, then claims that name specific people, then everything else.
For when you need to say something but facts are incomplete:
## Initial statement template
[Organization] is aware of [brief description of situation].
We are actively [gathering information / investigating / monitoring the situation].
[If applicable: The safety of [stakeholders] is our top priority.]
We will provide updates as verified information becomes available.
For media inquiries: [contact]
For [affected parties]: [resource/hotline]
Last updated: [timestamp]## Correction notice
**Correction [or Clarification]**: An earlier version of this [article/statement/post] [stated/implied] [incorrect information].
[If factual error]: The correct information is: [accurate facts].
[If misleading]: To clarify: [accurate context].
This [article/statement] has been updated to reflect accurate information.
We regret the error.
[Timestamp of correction]## Retraction notice
**Retraction**: [Publication name] is retracting [article title], published on [date].
[Brief explanation of what was wrong]: Our reporting [stated/relied on] [problematic element]. Subsequent verification revealed [why it was wrong].
[What you're doing about it]: We have [removed/updated] the article and are reviewing our editorial processes.
[Accountability]: We apologize to [affected parties] and our readers.
The full text of the original article is available [here/on request] for transparency.
Questions: [contact]from dataclasses import dataclass
from datetime import datetime
from typing import List, Dict
from collections import Counter
@dataclass
class CrisisMention:
platform: str
content: str
author: str
timestamp: datetime
sentiment: str # positive, negative, neutral, misinformation
reach: int # followers/potential impressions
requires_response: bool = False
class CrisisMonitor:
"""Track crisis-related social mentions."""
def __init__(self, crisis_keywords: List[str]):
self.keywords = crisis_keywords
self.mentions: List[CrisisMention] = []
def add_mention(self, mention: CrisisMention):
self.mentions.append(mention)
def get_dashboard(self) -> dict:
"""Real-time crisis overview."""
recent = [m for m in self.mentions
if (datetime.now() - m.timestamp).seconds < 3600]
return {
'total_mentions_1h': len(recent),
'sentiment_breakdown': self._sentiment_counts(recent),
'top_platforms': self._platform_counts(recent),
'misinformation_count': len([
m for m in recent
if m.sentiment == 'misinformation'
]),
'high_reach_negative': [
m for m in recent
if m.sentiment == 'negative' and m.reach > 10000
],
'pending_responses': len([
m for m in self.mentions
if m.requires_response
])
}
def _sentiment_counts(self, mentions: List[CrisisMention]) -> Dict:
return dict(Counter(m.sentiment for m in mentions))
def _platform_counts(self, mentions: List[CrisisMention]) -> Dict:
return dict(Counter(m.platform for m in mentions))## Should we respond to this?
### High priority (respond quickly)
- [ ] Factual misinformation spreading rapidly
- [ ] Direct question from journalist
- [ ] Affected party seeking help
- [ ] Influential account spreading false info
### Medium priority (respond thoughtfully)
- [ ] General negative sentiment
- [ ] Questions about our response
- [ ] Comparisons to competitors' handling
### Low priority / Do not engage
- [ ] Obvious trolling
- [ ] Bad faith actors
- [ ] Pile-on with no new claims
- [ ] Emotional venting (let it pass)
### Never respond
- [ ] While angry
- [ ] With unverified information
- [ ] In a way that escalates conflict
- [ ] By deleting legitimate criticismfrom dataclasses import dataclass
from typing import List, Optional
from datetime import datetime
@dataclass
class CrisisTeamMember:
name: str
role: str
phone: str
email: str
backup: Optional['CrisisTeamMember'] = None
@dataclass
class CrisisLog:
"""Maintain record of all crisis decisions."""
entries: List[dict] = None
def __post_init__(self):
self.entries = self.entries or []
def log(self, action: str, decision_maker: str,
rationale: str, outcome: str = "pending"):
self.entries.append({
'timestamp': datetime.now().isoformat(),
'action': action,
'decision_maker': decision_maker,
'rationale': rationale,
'outcome': outcome
})
def export_for_postmortem(self) -> str:
"""Generate timeline for after-action review."""
lines = ["# Crisis Response Timeline\n"]
for entry in self.entries:
lines.append(
f"**{entry['timestamp']}** - {entry['action']}\n"
f"- Decision by: {entry['decision_maker']}\n"
f"- Rationale: {entry['rationale']}\n"
f"- Outcome: {entry['outcome']}\n"
)
return '\n'.join(lines)For keeping stakeholders informed:
## Crisis status update [number]
**As of**: [timestamp]
**Next update**: [scheduled time]
### Current situation
[2-3 sentence summary of where things stand]
### What we know
- [Confirmed fact 1]
- [Confirmed fact 2]
### What we're working on
- [Action item 1] - [owner]
- [Action item 2] - [owner]
### Key decisions made
- [Decision] - [rationale]
### Immediate next steps
1. [Next action]
2. [Next action]
### Resources needed
- [Resource/support needed]
---
**Contact**: [Crisis lead name and number]## Post-crisis review template
### Timeline reconstruction
- When did we first learn of the crisis?
- When did we first respond publicly?
- Key decision points and timing
### What went well
- [Specific success 1]
- [Specific success 2]
### What could improve
- [Gap or failure 1] → [Recommended fix]
- [Gap or failure 2] → [Recommended fix]
### Process questions
- Did escalation work as intended?
- Were the right people involved?
- Did we have accurate information when needed?
- Was external communication timely and accurate?
### Specific improvements
- [ ] Update crisis protocol to address [gap]
- [ ] Train team on [identified weakness]
- [ ] Add [resource/tool] for future incidents
### Documentation
- All communications archived: [ ] Yes
- Decision log complete: [ ] Yes
- Media coverage compiled: [ ] Yes## Misinformation response checklist
### Before responding
- [ ] Is this claim spreading significantly?
- [ ] Will our response reach the affected audience?
- [ ] Could responding amplify the false claim?
### The response formula
1. **Lead with truth** (don't repeat the myth first)
2. **Be specific** about what's accurate
3. **Explain briefly** why the false claim is wrong
4. **Provide source** for accurate information
### Example structure
GOOD: "The event starts at 7pm at City Hall. Some posts incorrectly listed the time as 5pm."
BAD: "Some people are saying the event is at 5pm. That's wrong. It's actually at 7pm."
(Repeating the myth first reinforces it)## Field safety checklist
### Before deployment
- [ ] Editor knows your location and check-in schedule
- [ ] Emergency contacts updated
- [ ] Phone charged, backup battery
- [ ] First aid basics reviewed
- [ ] Exit routes identified
### During coverage
- [ ] Regular check-ins maintained
- [ ] Location sharing active
- [ ] Press credentials visible
- [ ] Recording when safe to do so
- [ ] Not taking unnecessary risks for story
### If situation escalates
- [ ] Leave immediately if directed
- [ ] Follow crowd flow, don't fight it
- [ ] Protect equipment but not at personal risk
- [ ] Contact newsroom ASAP| Field | Value |
|---|---|
| version | 1.0.0 |
| created | 2025-12-26 |
| updated | 2026-05-08 |
| author | Joe Amditis |
| domain | communications, journalism |
| complexity | advanced |
© jamditis, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
SKILL.md and 1 other file in journalism-core/skills/crisis-communications of jamditis/claude-skills-journalism.
Open the folder on GitHubat commit e3e2172
Crisis Communications 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 |
|---|---|---|---|---|---|---|
| Crisis Communications this skilljamditis/claude-skills-journalism | 417 | — | ~3.6k | Automated safety check: Pass | MIT | |
| Perplexity Web Searchdavila7/claude-code-templates | 32k | 11 repos | ~3.5k | Automated safety check: Notes | MIT | |
| Citation Verification GuideGalaxy-Dawn/claude-scholar | 5.7k | 2 repos | ~1.9k | Automated safety check: Pass | MIT | |
| Article Fact Checkerdigoal/blog | 8.6k | — | ~939 | Automated safety check: Pass | GPL-2.0 | |
| Deep Research Agent TeamImbad0202/academic-research-skills | 51k | — | ~13k | Automated safety check: Pass | Custom licence | |
| Docs Grounding Verifiermicrosoft/apm | 4k | — | ~1.9k | Automated safety check: Pass | MIT |
davila7/claude-code-templates
Runs web-grounded searches through Perplexity's Sonar models over OpenRouter for current events, recent literature and cited facts beyond the model's training cutoff.
Galaxy-Dawn/claude-scholar
Reference guidance for checking every citation in academic writing against canonical sources such as DOI, arXiv, CrossRef and Semantic Scholar, to catch fake or wrong references.
digoal/blog
三层审查模型,逐段逐句验证文章真伪、证据链与逻辑结构。Use when the user asks to fact-check, verify, audit, or evaluate the credibility of an article, essay, report, opinion piece, social-media post, or any written claim —…
Imbad0202/academic-research-skills
Runs a 13-agent pipeline for rigorous academic research, from forming the question through systematic search, synthesis, bias checks and an APA 7.0 report.
microsoft/apm
A skill your agent uses to verify CLAIM-LEVEL grounding of a documentation page (or set of pages) against the source code.
bradygaster/squad
Review and validate claims using counter-hypothesis testing.
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.
jamditis/claude-skills-journalism
Builds an Open Knowledge Format (OKF) knowledge base from existing docs, notes, or a repo.
jamditis/claude-skills-journalism
Local Gitleaks scans for staged changes, push ranges, and full history in private repos, with redacted reports.
jamditis/claude-skills-journalism
Acquire, clean, analyze, verify, visualize, and explain data for journalism.
jamditis/claude-skills-journalism
Creates print-ready HTML that exports to PDF. An agent skill from jamditis/claude-skills-journalism.
jamditis/claude-skills-journalism
Establishes how to find and use skills, requiring Skill tool invocation before any response.
Categories
Crisis communication and rapid-response workflows. An agent skill from jamditis/claude-skills-journalism. Crisis Communications is an agent skill from jamditis/claude-skills-journalism. Crisis communication and rapid-response workflows.
Crisis Communications fits situations like: covering breaking news; coordinating fast fact-checking on deadline.
Run `npx skills add jamditis/claude-skills-journalism --skill crisis-communications -a claude-code`. Or copy the skill folder (journalism-core/skills/crisis-communications in jamditis/claude-skills-journalism) into .claude/skills/crisis-communications in your project. Claude Code loads it when a task matches its description.
Run `npx skills add jamditis/claude-skills-journalism --skill crisis-communications -a codex`. Or copy the skill folder (journalism-core/skills/crisis-communications in jamditis/claude-skills-journalism) into .agents/skills/crisis-communications in your project. Codex loads it when a task matches its description.
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 crisis-communications -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/crisis-communications, .gemini/skills/crisis-communications, .github/skills/crisis-communications and .opencode/skills/crisis-communications in your project.
SKILL.md names no scripts, command-line tools or credentials: Crisis Communications is instructions for the agent only. Our summary lists: Python 3.
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.
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.
Crisis Communications is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 3.6k tokens (SKILL.md is roughly 14k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Crisis Communications: Perplexity Web Search (davila7/claude-code-templates, 32k stars), Citation Verification Guide (Galaxy-Dawn/claude-scholar, 5.7k stars), Article Fact Checker (digoal/blog, 8.6k stars) and Deep Research Agent Team (Imbad0202/academic-research-skills, 51k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
jamditis (a GitHub user) maintains it in jamditis/claude-skills-journalism, which has 417 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.