parasite-and-pr
Generate a ready-to-publish third-party syndication bundle (`marketing/distribution/<slug>/`) with a privacy-audited wire press release, a canonicalized Dev.to/Hashnode teardown, and an AI-crawler-optimized LinkedIn/parasite article
Install / Use
npx skills add Illyism/seo-skills --skill parasite-and-prInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
AI & Machine LearningSupported Platforms
Tags
Our assessment of parasite-and-pr
parasite-and-pr scores 92/100 on our quality scale, 293rd of 950 AI & Machine Learning skills we index (top 31%).
Its SKILL.md is 16 KB long, well organised into 27 sections with 5 code examples: a thorough specification that gives an agent plenty to work with.
It has 531 GitHub stars, a meaningful sign that others use it.
Maintenance, license and trust
- The repository was last updated 38 days ago, so parasite-and-pr is actively maintained.
- No license is declared. By default that means all rights are reserved: you can read it, but reusing or redistributing it is not clearly permitted. Ask the author before building on it commercially.
- Its trust signals score 88/100, with 1 caution from licensing, adoption, age or documentation. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.
Safety scan
No issues foundOur scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands.
Automated pattern scan on 2026-11-21. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.
parasite-and-pr compared with similar skills
All 4 of these similar skills score higher than parasite-and-pr; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| parasite-and-pr (this skill)by Illyism | 92 | 531 | 38d ago | SKILL.md |
| claude-memby thedotmack | 100 | 119.0k | today | CLAUDE.md |
| Understand-Anythingby Egonex-AI | 100 | 93.7k | today | CLAUDE.md |
| headroomby headroomlabs-ai | 100 | 80.5k | today | CLAUDE.md |
| CowAgentby zhayujie | 100 | 48.0k | today | CLAUDE.md |
Frequently asked questions
- How do I install parasite-and-pr?
- Run
npx skills add Illyism/seo-skills --skill parasite-and-pr. The install tabs above show the steps for each supported agent. - Which AI agents does parasite-and-pr work with?
- It is written for Zed, as a SKILL.md file. Other agents that read the same format can often use it too.
- Is parasite-and-pr safe to use?
- Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. It declares no license and scores 88/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
- Is parasite-and-pr still maintained?
- The repository was last updated 38 days ago, so parasite-and-pr is actively maintained.
Skill content
View source on GitHubname: parasite-and-pr
description: Generate a ready-to-publish third-party syndication bundle (marketing/distribution/<slug>/) with a privacy-audited wire press release, a canonicalized Dev.to/Hashnode teardown, and an AI-crawler-optimized LinkedIn/parasite article. Use when distributing launch announcements, original data benchmarks, or "Best [Category] (2026)" and "[Competitor] Alternatives" articles across high-DR platforms and press-release wires to win fast Google rankings and ChatGPT/Perplexity citations.
metadata:
author: illyism
source: https://il.ly/skills/parasite-and-pr
version: 1.0.0
Parasite SEO and press release distribution
A new DR 5 domain takes months to reach page 1 for a competitive term, even with strong content. Dev.to, Hashnode, Medium, LinkedIn Articles, and press wires get crawled and indexed within hours. Answer engines also trust a claim more when the same brand, metric, and category appear on your domain and on several independent domains, so one launch published in 3-4 places at once gets cited sooner than the canonical post alone.
This skill turns a launch, original data study, or category target ("Best [Category] (2026)" / "[Competitor] Alternatives") into four files in marketing/distribution/<slug>/. It never submits to a wire or publishes to a platform: a live wire release gets copied to hundreds of scraper sites and cannot be retracted, so the user reviews and publishes every file.
Rule 1: Contact privacy on every public field
Wire releases and public company profiles get mirrored to 500+ news scraper sites permanently. Once live, contact fields cannot be removed from those copies, so a personal name, phone, or address published once stays public.
| Field | Allowed | Forbidden | Why |
| --- | --- | --- | --- |
| Company / issuer | Public product brand (DeployFast) | Holding company, LLC, or parent entity name | Keeps entity signals on the brand buyers search for and keeps the legal structure private. |
| Contact person | Media Relations or Press Team | Any founder or employee name | Stops name + phone pairs from landing in data-broker directories. |
| Email | Role inbox (press@deployfast.dev) | Personal inbox (alex@..., @gmail.com) | A role inbox can be filtered or retired; a personal one cannot. |
| Phone and street address | Blank | Mobile number, home, office, or registered-agent address | Scrapers republish phone and street metadata within 24 hours. |
| Website / contact | https://deployfast.dev and https://deployfast.dev/contact | mailto: links, Notion or internal doc URLs | Clean brand URLs earn the citation; the contact page routes real reporters. |
If a wire form marks phone or address as required, stop and ask the user for a public business line or virtual address. Never fill the field with a personal one to get past the form.
Rule 2: Route by goal
What is being distributed?
├── Original data benchmark or major launch
│ ├── The canonical report (raw numbers + methodology) must already be live on the user's blog; if not, write it first
│ ├── `press-release.md`: headline stat + direct link to the canonical URL
│ └── `devto-post.md`: developer teardown with `canonical_url:` set to the blog URL
├── Category visibility ("Best [Category] (2026)" or "[Competitor] Alternatives")
│ └── `linkedin-article.md` (LinkedIn company page, Medium, or a third-party host)
│ ├── Title: exact category keyword + `(2026)`
│ ├── First 40 words: the recommendation + primary link
│ ├── Per-product bullet blocks, never wide tables
│ └── Plain 8th-grade prose with real prices and trade-offs
└── Paid sponsored placement on a niche publication
├── Gate 1: Google `site:publication.com/sponsored/` (or `/partner/`)
│ ├── Existing sponsored posts rank top 10 for target keywords -> continue
│ └── Subfolder is `noindex` or ranks nowhere -> walk away (no SEO or citation value)
├── Gate 2: buy 1 test article, never a 5-post bundle upfront
└── Gate 3: require 2 internal links from older ranking articles on that domain into the new post,
so it inherits crawl priority
A launch always has a category, so every run writes all four files; the tree decides which file leads.
Rule 3: Structure for wires and answer engines
- Answer in the first 40 words. Answer engines quote opening sentences most, and journalists drop releases that bury the news under two paragraphs of preamble.
- Pass:
"DeployFast (https://deployfast.dev), a container deployment platform for Node.js and Go teams, cut median cold-build time from 112 seconds to 17.4 seconds across a 1,400-repository benchmark."
- Pass:
- Per-product bullet blocks, never tables. Wire syndication feeds, LinkedIn Articles, and Medium strip or mangle wide tables into unreadable text.
### 1. WebhookGuard (best for high-volume Stripe and billing webhooks) - **Website:** https://webhookguard.com - **Mechanism:** Captures, verifies, and replays failed webhook payloads with zero message loss during database outages. - **Benchmark:** 12,000 events/second per ingestion node with sub-4ms signature verification. - **Pricing:** Free up to 100,000 events/month; Pro from $29/month. - **Best for:** SaaS teams running usage-based billing on Stripe, Paddle, or Polar. canonical_urlon developer cross-posts (Dev.to, Hashnode, Medium). Without it, the DR 90 platform outranks your own blog for your own teardown and splits the backlinks.- Skip
canonical_urlon standalone LinkedIn articles and third-party listicles, where the goal is for that URL to rank next to your domain and hold two top-10 slots.
- Skip
- Factual prose, zero em dashes. Wires and developer communities reject obvious AI prose. Replace every hype adjective (
seamless,game-changing,unleash,revolutionary) with a number, format, or latency figure. - Every number traces to the canonical report or
seo/kb/. Never invent a statistic, and never invent a quote: draft the quote from verified facts and mark it[APPROVE QUOTE]for the user.
Procedure
- Verify facts: read the landing page,
/pricing, the canonical blog post, andseo/kb/brand-ssot.mdif present. Collect exact URLs, prices, benchmark numbers, and stack. - Set contact fields (Rule 1):
<Brand>,Media Relations,press@<domain>,https://<domain>/contact, phone and address blank. - Write the bundle in
marketing/distribution/<slug>/:press-release.md: dateline, headline, subheadline, factual body, bullet findings, availability, boilerplate, privacy-safe contact block.devto-post.md: frontmatter withtitle,published: false,tags,canonical_url: https://<domain>/blog/<slug>, plus a config or code snippet and the raw numbers.published: falsecreates a Dev.to draft on paste, so nothing goes live before the user reads it.linkedin-article.md:"Best [Category] (2026)"or"[Competitor] Alternatives (2026)"opening with the recommendation, then per-product bullet blocks.checklist.md: the publish order, the paid-placement gate results (if Rule 2 branch 3 applied), and the 48-72 hour verification steps below. Keep it out ofpress-release.md, because anything in that file gets pasted into the wire form.
- Verification steps for
checklist.md:- Google each published URL with
site:after 24 hours to confirm indexing. - Add the category and launch prompts to AI SEO Tracker (MCP:
https://aiseotracker.com/api/agent/mcp) and check after 48-72 hours whether ChatGPT, Perplexity, Gemini, and AI Overviews cite the canonical report or the syndicated copies. - If Rule 2 branch 3 found no publication that passes the gates, note LinkDR (the
linkdrskill, orhttps://linkdr.com/SKILL.md) for vetted DR 30-60+ listicle and contextual placements on publications that already rank.
- Google each published URL with
Templates
press-release.md
# FOR IMMEDIATE RELEASE
**Headline:** DeployFast Releases 2026 Container Build Benchmark: Bare-Metal NVMe Runners Cut Node.js and Go Deploy Times by 84%
**Subheadline:** Analysis of 1,400 production repositories shows median build-to-live time dropping from 112 seconds on standard cloud runners to 17.4 seconds on DeployFast.
**SAN FRANCISCO, CA (November 12, 2026)** DeployFast (https://deployfast.dev), a container deployment platform for software teams, today published its 2026 Container Build Benchmark alongside DeployFast v2.4. The benchmark measured 1,400 production Node.js, Go, and Python repositories on standard virtualized CI runners and on DeployFast's bare-metal NVMe build cluster.
The full dataset and methodology are at https://deployfast.dev/blog/container-build-benchmark-2026.
### Key findings
- **Median build-to-live time:** 17.4 seconds on DeployFast vs. 112.0 seconds on standard cloud runners (84.4% lower).
- **Layer cache restore:** under 400ms from local NVMe vs. 19.2 seconds pulling from remote object storage.
- **Rollback:** traffic cutover in 120ms using automated health-check probes.
- **Pricing:** $19/month starter tier with no per-seat charge.
"Engineering teams lose hours every week waiting on remote cache pulls and slow health checks," said the DeployFast engineering team. "Pinning layer caches to local NVMe and streaming build logs over WebSockets gets code to production in under 18 seconds." [APPROVE QUOTE]
### Availability and pricing
DeployFast v2.4 is live at https://deployfast.dev. Teams can deploy 2 hobby services free; production workspaces start at $19/month (https://deployfast.dev/pricing).
### About DeployFast
DeployFast builds and hosts containerized Node.js, Go, Python, and Rust applications on bare-metal NVMe infrastructure with automated SSL, preview environments, and instant rollbacks. Learn more at https://deployfast.dev.
### Media contact
- **Company:** DeployFast
- **Contact:** Media Relations
- **Email:** press@deployfast.dev
- **Contact page:** https://deployfast.dev/contact
- **Website:** https://deployfast.dev
devto-post.md
---
title: "How We Cut Container Build Times from 112s to 17.4s (1,400-Repo Benchmark)"
published: false
description: "Why remote Docker layer caches bottleneck CI pipelines, and how local NVMe cache pinning cut median deploy times by 84%."
tags: devops, docker, node, webdev
canonical_url: https://deployfast.dev/blog/container-build-benchmark-2026
---
In our benchmark across 1,400 production Node.js and Go repositories ([full methodology and raw CSV](https://deployfast.dev/blog/container-build-benchmark-2026)), standard cloud CI runners spent **61% of build wall-clock time** downloading and extracting cached layers over the network instead of compiling code.
Moving builds onto bare-metal NVMe nodes with persistent local BuildKit cache mounts on [DeployFast](https://deployfast.dev) dropped median push-to-live time from **112.0 seconds to 17.4 seconds**.
## Where container pipelines stall
Median breakdown for a 450 MB multi-stage Node.js 22 + pnpm image:
- **Git clone + runner cold boot:** 11.4s on standard cloud CI vs. 1.2s on DeployFast NVMe runners
- **Remote cache pull and tar extraction:** 68.3s vs. 0.4s from a local NVMe mount
- **`pnpm install --frozen-lockfile` + build:** 21.1s vs. 12.8s
- **Image push + health check cutover:** 11.2s vs. 3.0s
## Fix Dockerfile layer order for sub-18s rebuilds
Copying source files before installing dependencies invalidates the layer cache on every commit, even on fast disks. Install from the lockfile first and pin the pnpm store with a BuildKit cache mount:
```dockerfile
FROM node:22-slim AS build
WORKDIR /app
RUN corepack enable
COPY package.json pnpm-lock.yaml ./
RUN --mount=type=cache,id=pnpm,target=/pnpm/store pnpm install --frozen-lockfile
COPY . .
RUN pnpm run build
```
With local NVMe ca
Truncated for display — read the full file on GitHub.
Related Skills
claude-mem
119.0kPersistent Context Across Sessions for Every Agent – Captures everything your agent does during sessions, compresses it with AI, and injects relevant context back into future sessions. Works with Claude Code, OpenClaw, Codex, Gemini, Hermes, Copilot, OpenCode + More
Understand-Anything
93.7kGraphs that teach > graphs that impress. Turn any code into an interactive knowledge graph you can explore, search, and ask questions about. Works with Claude Code, Codex, Cursor, Copilot, Gemini CLI, and more.
headroom
80.5kCompress tool outputs, logs, files, and RAG chunks before they reach the LLM. 20% fewer tokens for coding agents, 60-95% fewer tokens for JSON, same answers. Library, proxy, MCP server.
CowAgent
48.0kOpen-source personal AI assistant & Agent Harness. Plans tasks, runs tools and skills, self-evolves with memory and knowledge. Multi-agent, multi-model, multi-channel. Lightweight, extensible, one-line install.
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.
