newsletter-curation
Create Curated Newsletter Issues
Teams need a repeatable way to turn scattered sources into useful newsletter issues. This skill helps Claude, Codex, and Claude Code plan formats, source topics, write commentary, and improve growth habits.
Do not auto-install this skill.
The canonical policy requires operator review before any installation action.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "newsletter-curation" from https://skillstore.io/skills/inference-sh-9-newsletter-curation.md and its manifest at https://skillstore.io/api/skills/inference-sh-9-newsletter-curation/manifest. Verify the artifact. Do not auto-install. Inspect the skill and report your findings, then wait for an operator or manual installation decision.Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Test it
Using "newsletter-curation". A weekly AI newsletter for product managers needs a clear issue structure.
Expected outcome:
- Opening note: two sentences on the week in AI product work.
- Big story: one launch or policy change with practical product impact.
- Worth reading: five curated links with short editorial commentary.
- Quick hits: three brief updates for scanning readers.
- Closing: one question that invites replies from subscribers.
Using "newsletter-curation". A founder wants better commentary for a link about pricing research.
Expected outcome:
This piece matters because it connects pricing experiments to customer trust. I would highlight the research method, the strongest finding, and one practical test readers can run this week.
Using "newsletter-curation". An editorial team needs subject line ideas for a developer tools digest.
Expected outcome:
- #18: The build tool shift hiding in plain sight
- 5 developer tools worth testing this week
- This week in dev tools: faster builds, fewer tabs
- The migration guide teams keep asking for
Security Audit
CriticalMost backtick-related static findings are false positives from Markdown fences and inline formatting. The remote installer command on SKILL.md line 14 is a confirmed critical pipe-to-shell risk, and several infsh command examples create real external service exposure.
Confirmed security concerns (2)
Capability review items (6)
These are real local capabilities that may be expected for this skill, so they require review but are not counted as confirmed malicious behavior.
Risk Factors
⚙️ External commands (21)
🌐 Network access (3)
Detected Patterns
Share & cite this report
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Copy report link
https://skillstore.io/skills/inference-sh-9-newsletter-curation/audits/4?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/inference-sh-9-newsletter-curation?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/inference-sh-9-newsletter-curation?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/inference-sh-9-newsletter-curation/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/inference-sh-9-newsletter-curation.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Academic citations (APA · BibTeX · CFF)
APA citation
inference-sh-9. (2026). newsletter-curation security audit report (audit version 4) [Author version unspecified]. Skillstore. https://skillstore.io/skills/inference-sh-9-newsletter-curation/audits/4BibTeX citation
@techreport{inference-sh-9-inference-sh-9-newsletter-curation-2026,
author = {inference-sh-9},
title = {newsletter-curation security audit report (audit version 4)},
institution = {Skillstore},
year = {2026},
number = {4},
url = {https://skillstore.io/skills/inference-sh-9-newsletter-curation/audits/4},
note = {Author version unspecified}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "newsletter-curation security audit report (audit version 4)"
version: "unspecified"
type: report
authors:
- name: "inference-sh-9"
date-released: "2026-07-05"
url: "https://skillstore.io/skills/inference-sh-9-newsletter-curation/audits/4"
identifiers:
- type: other
value: "skillstore:inference-sh-9-newsletter-curation:audit:4"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: MediumWhat You Can Build
Plan a Weekly Industry Digest
Build a repeatable issue structure with curated links, short commentary, and a consistent send schedule.
Develop a Creator Newsletter
Turn personal expertise into a focused issue with an essay, selected links, and a clear reader call to action.
Standardize Editorial Curation
Create source filters, commentary rules, subject line patterns, and quality checks for a team newsletter.
Try These Prompts
Create a weekly link roundup for [audience] about [topic]. Include five source slots, a short introduction, commentary prompts, and a clear closing call to action.
Plan issue #[number] for [newsletter name]. Include a big story, worth reading section, quick hits, stat of the week, subject lines, and a send cadence recommendation.
Review these candidate sources for [audience]. Select the strongest items, explain why each matters, and write concise commentary with my editorial point of view.
Create a six-week newsletter growth plan for [newsletter]. Include distribution channels, referral ideas, archive strategy, engagement prompts, and metrics to monitor after each issue.
Best Practices
- Verify each source before writing commentary or recommending it to readers.
- Keep each issue focused on the reader value promised by the subject line.
- Use a consistent send cadence and review performance after every issue.
Avoid
- Sending long lists of links without editorial context.
- Publishing AI-written summaries without checking source accuracy.
- Running external posting commands before the user approves final copy.
Frequently Asked Questions
What does this skill help create?
Can it find current sources?
Does it send email campaigns?
Can it help with subscriber growth?
Is external publishing automatic?
Which AI tools can use this skill?
Developer Details
Author
inference-sh-9License
MIT
Skillstore revision
r1
Version notice
The author did not declare a version.
Ref
a25199bc7d6b82598536822d1738eb5d5f54025b
Maintenance freshness
7/23/2026
Usage
5 downloads · 171 views
File structure
📄 SKILL.md