jamesgray-ai/editing-hbr-articles
.claude/skills/editing-hbr-articles/SKILL.md
This skill should be used when the user wants to edit a business article to HBR publication quality, review a draft before publication, improve business writing for executive audiences, or mentions "HBR quality" or "publication ready". Makes prescriptive edits for clarity, structure, evidence quality, and executive voice. Targets feature articles and thought leadership pieces.
$ install --global
skillsauthnpx skillsauth add jamesgray-ai/handsonai editing-hbr-articlesInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 15, 2026, 2:05 PM47.0s2 files scanned
SKILL.md
- name:
- editing-hbr-articles
- description:
- >
- user-invocable:
- true
Editing HBR Articles
Edit articles to Harvard Business Review publication standards. Make direct, prescriptive edits.
Workflow
- Read the article completely before making any edits
- Assess against criteria in references/editorial-criteria.md
- Make edits directly to the file, focusing on highest-impact issues first
- Provide summary of changes made and rationale
Edit Priority Order
Address issues in this order:
- Structure: Does the opening hook? Is the thesis clear by paragraph 3? Do sections flow logically?
- Evidence: Are claims supported with specific data, named companies, and credible sources?
- Redundancy: Cut repeated points, excessive examples (keep 2-3 strong ones), and summary conclusions that rehash the intro
- Voice: Remove hedging, jargon, and promotional language. Strengthen to active voice.
- Length: Target 2,500-3,500 words for features, 1,500-2,500 for thought leadership
What to Cut
- Throat-clearing openings ("In today's rapidly changing...")
- Redundant examples after a point is proven
- Conclusions that repeat the introduction
- Hedge words ("perhaps," "it seems," "might")
- Business jargon (see editorial-criteria.md for list)
What to Strengthen
- Vague claims → specific data ("improved efficiency" → "reduced costs by 30%")
- Unnamed examples → named companies and executives
- Passive voice → active voice
- Generic statements → concrete implications for the reader
Output Format
After editing, provide:
## Editorial Summary
**Major changes:**
- [List 2-4 significant structural or content changes]
**Tightening:**
- Word count: [before] → [after] ([X]% reduction)
- [Key cuts made]
**Remaining considerations:**
- [Any optional improvements or decisions for the author]
Save the edited article to the same file path.
Related Skills
jamesgray-ai/writing-workflow-sops
documentation
VerifiedTrustedCommunity
Write Standard Operating Procedure documentation for workflows and save as markdown files. Selects full or lightweight SOP template based on autonomy level (deterministic vs. guided/autonomous), then adapts for workflow type (Manual, Augmented, Automated). Use when the user asks to write an SOP, document a workflow, create procedure documentation, or capture how a workflow is executed. Triggers on "write an SOP", "document this workflow", "create operating instructions", "how is this workflow executed".
3SKILL.mdUpdated Apr 15, 2026
jamesgray-ai/writing-process-guides
documentation
VerifiedTrustedCommunity
Write Business Process Guide documentation that explains when, why, and how to execute a complete business process with its component workflows, and save as markdown files. Use when documenting a business process end-to-end, creating playbooks, or explaining how multiple workflows fit together. Triggers on "write process guide", "document this process", "create a playbook for", "how do these workflows connect".
3SKILL.mdUpdated Apr 15, 2026
jamesgray-ai/syncing-skills-to-github
development
VerifiedTrustedCommunity
This skill should be used when the user wants to sync skills to GitHub, push skill changes to a remote repository, or back up local skills. Syncs Claude Agent Skills from ~/.claude/skills/ (local) to GitHub repository using git commands. Commits changes, pushes to remote, and updates Notion AI Building Blocks with GitHub URLs.
3SKILL.mdUpdated Apr 15, 2026
jamesgray-ai/registering-building-blocks
development
VerifiedTrustedCommunity
This skill should be used when the user wants to register or update AI building blocks (Skills, Agents, Prompts, Context MDs) in the Notion AI Building Blocks database. Triggers after skill creation, agent creation, prompt authoring, context MD updates, or when the user asks to register, add, or track a building block in Notion.
3SKILL.mdUpdated Apr 15, 2026