agentlinkops 0.6.11 → 0.6.16

package/skills/content-defingerprinting/scripts/watermarks/wm-scan.py

@@ -1,212 +0,0 @@
-#!/usr/bin/env python3
-"""Stage 2b of the content pipeline: invisible-Unicode / provenance-mark scan.
-
-Wraps the vendored watermarks-remover Layer A engine (see UPSTREAM.json) and
-reports every invisible or undisplayable character in the files you point it at,
-with the line each one sits on.
-
-    wm-scan.py <path> [<path> ...]        # report; exit 1 if anything is found
-    wm-scan.py --fix <path> [...]         # clean in place, then re-verify
-    wm-scan.py --json <path>              # machine-readable, for a gate
-    wm-scan.py --quiet <path>             # exit code only
-
-Exit codes:  0 = clean   1 = findings   2 = usage/read error
-
-Why this is a required step and not a nicety: these characters are invisible in
-every editor and every review, they survive copy-paste out of PDFs, Word and LLM
-output, and they silently break the things that check our prose. A zero-width
-space inside "affidavit" means the banned-phrase scan, the citation audits and
-every grep in the repo stop seeing the word.
-
-WHAT THIS DOES NOT DO, on purpose:
-  - It does not strip C2PA manifests. C2PA on one of our own generated covers is
-    a signal worth investigating, not noise worth deleting. Report it, ask why.
-  - It does not run Layer B (rewriting text to defeat statistical watermarks).
-    Our humanize stage already rewrites AI-pattern prose on quality grounds.
-  - It does not touch image pixels. Our covers are our own generated assets.
-"""
-from __future__ import annotations
-
-import argparse
-import io
-import json
-import os
-import re
-import sys
-
-VENDOR = os.path.join(os.path.dirname(os.path.abspath(__file__)), "vendor")
-sys.path.insert(0, VENDOR)
-try:
-    import text_unicode as tu
-except ImportError:  # pragma: no cover
-    sys.stderr.write("wm-scan: vendored engine missing at %s\n" % VENDOR)
-    sys.stderr.write("         re-run the kit install, or ./revendor.sh\n")
-    sys.exit(2)
-
-# Fast pre-filter. The engine is thorough and therefore per-character, which is far
-# too slow across a 14,000-file data tree. This regex is a deliberate SUPERSET of what
-# the engine flags: anything it misses cannot be suspicious, and its false positives
-# just fall through to the engine, which makes the real call. Without it a full scan of
-# one sibling repo did not finish in two minutes; with it, seconds.
-SUSPECT = re.compile(
-    "[\u00A0\u00AD\u034F\u061C\u115F\u1160\u17B4\u17B5\u180B-\u180E"
-    "\u2000-\u200F\u2028-\u202F\u205F-\u206F\u3000\u3164\uFE00-\uFE0F"
-    "\uFEFF\uFFA0\uFFF9-\uFFFB\uE000-\uF8FF]"
-    "|[\U000E0000-\U000E007F]|[\U000F0000-\U0010FFFD]"
-)
-
-TEXT_EXT = (".mdx", ".md", ".tsx", ".ts", ".jsx", ".js", ".json", ".html", ".css", ".txt", ".yaml", ".yml")
-SKIP_DIRS = {".git", "node_modules", ".next", "out", ".contentlayer", "cache", ".venv", "__pycache__", "vendor"}
-
-# Paths holding ARCHIVED SOURCE EVIDENCE: scraped snapshots, extracted policy PDFs,
-# price history. --fix refuses to touch these, and it is not a configurable nicety.
-# The marks in there are PDF glyph artifacts in a document somebody else published,
-# and that archive is what every `_source` and `verified_quote` on the site resolves
-# against. Rewriting it to make a scan pass is the tampering the provenance chain
-# exists to detect: one edited file and one re-forged hash is the whole failure story.
-# Report them, leave them, and treat any quote LIFTED from them as the thing to check.
-ARCHIVE_MARKERS = ("/sources/", "/snapshots/", "/evidence/", "/_sources/", "/price-history/", "/raw/")
-
-
-# LOAD-BEARING LITERALS. An invisible character sitting inside a regex character class
-# is not contamination, it is the sanitizer that REMOVES contamination, written with the
-# literal characters it strips. Three of these exist across the estate:
-#   .replace(/[<zwsp><zwnj><zwj><bom>]+/g, '')   covered-weight EHB extractor
-#   .replace(/&nbsp;| |<zwsp>/g, " ")            proxy-compare proxyscrape
-#   .replace(/<nbsp>/g, " ")                     proxy-compare rayobyte
-# Auto-fixing them empties the character class and silently breaks the sanitizer, letting
-# through exactly the marks it existed to catch. High-precision guard: refuse when the
-# hit's own line carries regex-replacement syntax.
-LOAD_BEARING = re.compile(r"\.replace\s*\(|new\s+RegExp\(|/\[[^\]]*\]|\\u[0-9A-Fa-f]{4}")
-
-
-def is_load_bearing(text, index):
-    start = text.rfind("\n", 0, index) + 1
-    end = text.find("\n", index)
-    line = text[start:] if end == -1 else text[start:end]
-    return bool(LOAD_BEARING.search(line))
-
-
-def is_archive(path):
-    norm = "/" + path.replace(os.sep, "/").strip("/") + "/"
-    return any(marker in norm for marker in ARCHIVE_MARKERS)
-
-
-def walk(paths):
-    for p in paths:
-        if os.path.isfile(p):
-            yield p
-            continue
-        for dirpath, dirnames, filenames in os.walk(p):
-            dirnames[:] = [d for d in dirnames if d not in SKIP_DIRS]
-            for f in sorted(filenames):
-                # AppleDouble shadows: these volumes are exFAT and every file has one
-                if f.startswith("._") or not f.endswith(TEXT_EXT):
-                    continue
-                yield os.path.join(dirpath, f)
-
-
-def line_of(text, index):
-    return text.count("\n", 0, index) + 1
-
-
-def scan_file(path):
-    try:
-        text = io.open(path, encoding="utf-8").read()
-    except (UnicodeDecodeError, OSError):
-        return None
-    if not SUSPECT.search(text):
-        return None
-    report = tu.inspect_text(text)
-    if not report.suspicious_total:
-        return None
-    findings = []
-    load_bearing = False
-    for hit in report.hits:
-        if any(is_load_bearing(text, i) for i in hit.samples):
-            load_bearing = True
-        findings.append({
-            "codepoint": "U+%04X" % hit.codepoint,
-            "label": hit.label,
-            "kind": hit.kind,
-            "count": hit.count,
-            "lines": sorted({line_of(text, i) for i in hit.samples}),
-        })
-    return {"file": path, "total": report.suspicious_total,
-            "archive": is_archive(path), "load_bearing": load_bearing,
-            "findings": findings}
-
-
-def main():
-    ap = argparse.ArgumentParser(description="Scan content for invisible Unicode / provenance marks.")
-    ap.add_argument("paths", nargs="+", help="Files or directories to scan")
-    ap.add_argument("--fix", action="store_true", help="Clean in place, then re-verify")
-    ap.add_argument("--json", action="store_true", help="Machine-readable output")
-    ap.add_argument("--quiet", action="store_true", help="Exit code only")
-    ap.add_argument("--keep-nbsp", action="store_true",
-                    help="With --fix, leave no-break spaces alone (they are sometimes deliberate)")
-    args = ap.parse_args()
-
-    results, scanned = [], 0
-    for path in walk(args.paths):
-        scanned += 1
-        found = scan_file(path)
-        if found:
-            results.append(found)
-
-    if args.fix and results:
-        refused = [r["file"] for r in results if r["archive"]]
-        held = [r["file"] for r in results if r["load_bearing"] and not r["archive"]]
-        for result in results:
-            if result["archive"] or result["load_bearing"]:
-                continue
-            text = io.open(result["file"], encoding="utf-8").read()
-            cleaned, _stats = tu.clean_text(text, normalize_spaces=not args.keep_nbsp)
-            if cleaned != text:
-                io.open(result["file"], "w", encoding="utf-8").write(cleaned)
-                result["fixed"] = True
-        results = [r for r in (scan_file(x["file"]) for x in results) if r]
-        if refused and not args.json:
-            sys.stderr.write(
-                "\nwm-scan: REFUSED to fix %d archived source file(s).\n"
-                "         That tree is the evidence every citation resolves against; the marks in it\n"
-                "         belong to a document somebody else published. Check the QUOTES lifted from\n"
-                "         it instead, and leave the archive byte-identical.\n" % len(refused))
-            for f in refused[:10]:
-                sys.stderr.write("           %s\n" % f)
-        if held and not args.json:
-            sys.stderr.write(
-                "\nwm-scan: HELD BACK %d file(s) whose marks look LOAD-BEARING.\n"
-                "         The character sits on a line with regex-replacement syntax, which usually\n"
-                "         means it IS the sanitizer that strips these marks, written literally.\n"
-                "         Emptying that character class breaks the guard. Review by hand.\n" % len(held))
-            for f in held[:10]:
-                sys.stderr.write("           %s\n" % f)
-
-    if args.json:
-        json.dump({"scanned": scanned, "dirty": len(results), "results": results}, sys.stdout, indent=2)
-        sys.stdout.write("\n")
-    elif not args.quiet:
-        if not results:
-            print("wm-scan: %d files scanned, clean." % scanned)
-        else:
-            print("wm-scan: %d files scanned, %d carry invisible characters.\n" % (scanned, len(results)))
-            for result in results:
-                tag = ""
-                if result["archive"]:
-                    tag = "   [ARCHIVE - report only, never fix]"
-                elif result["load_bearing"]:
-                    tag = "   [LOAD-BEARING? regex literal on that line - review by hand]"
-                print("  %s%s" % (result["file"], tag))
-                for f in result["findings"]:
-                    lines = ",".join(str(n) for n in f["lines"][:6])
-                    print("      %-46s x%-3d [%s] line %s" % (f["label"], f["count"], f["kind"], lines))
-            print("\nFix with:  wm-scan.py --fix <path>")
-            print("Then read the diff. A character inside a sourced quote is a provenance")
-            print("question before it is a formatting one: check it against the document.")
-
-    return 1 if results else 0
-
-
-if __name__ == "__main__":
-    sys.exit(main())

package/skills/internal-linking-optimizer/SKILL.md

@@ -1,56 +0,0 @@
----
-name: internal-linking-optimizer
-description: Audit content pages and add strategic internal links across TSX templates and MDX files. Use for internal linking, topical clusters, orphaned content, contextual links, SEO link strategy, or content network improvements.
----
-
-# Internal Linking Optimizer
-
-Use this skill when adding internal links to existing content pages. This skill does not create new content pages.
-
-## The orphan-page doctrine (the trap this skill exists to close)
-
-A new page with zero inbound internal links is invisible: no authority flows in and
-no user can reach it. This is the DEFAULT state of every new page, and it survives
-every build gate. A broken-link audit only proves outbound links resolve; it cannot
-tell you nothing links IN. After publishing any page, prove inbound links exist from
-established pages:
-
-```bash
-# Must return at least one file that is NOT the page itself and NOT the sitemap.
-# Run over your content roots (SITE.md).
-grep -rl '"/<new-slug>/"' <your-content-roots> | grep -v "<new-slug>" | grep -v sitemap
-```
-
-If it returns nothing, the page is orphaned. Fix it by editing established, related
-pages to link in (3+ inbound links is the working floor), not by waiting for it to
-"get picked up".
-
-## Workflow
-
-1. Read `references/source-prompt.md` before changing files.
-2. Scan content pages and separate them from application or functional pages.
-3. Map topics, content relationships, orphaned pages, and content clusters.
-4. Choose natural anchor text already present in the content when possible.
-5. Add a conservative number of contextual links per page.
-6. Verify destinations exist and links use the repo's expected relative path or routing pattern.
-7. Report source page, destination page, anchor text, and reason for each link added.
-
-## Linking heuristics
-
-- 3-5 contextual links per content page is the working baseline; stay natural, not
-  quota-driven.
-- Link bidirectionally between closely related pages; a one-way link between
-  siblings is usually half-done.
-- Route authority downhill: link from high-authority pages to important but
-  lower-authority pages, not only the reverse.
-- Prefer links in the main content body over sidebar/footer/nav slots; body links
-  carry the semantic signal.
-- Build pillar-cluster shape: overview pages link to every variant page and each
-  variant links back.
-
-## Guardrails
-
-- Do not change application logic or functional components.
-- Preserve existing content and valuable links.
-- Use React or Next.js link patterns in TSX, and markdown or MDX link patterns in MDX.
-- Avoid generic anchors and repeated identical anchors to the same destination.

package/skills/internal-linking-optimizer/references/source-prompt.md

@@ -1,76 +0,0 @@
-internal linking
-
-You are an expert SEO specialist and content strategist specializing in internal linking optimization. Your deep understanding of information architecture, user journey mapping, and search engine algorithms enables you to create powerful internal linking strategies that boost both user engagement and search rankings.
-
-Your primary mission is to analyze content pages (excluding application/functional pages) and implement strategic internal links that create a robust content network. You work with both TSX templates with embedded content and MDX files.
-
-**Core Responsibilities:**
-
-1. **Content Analysis Phase:**
-   - Scan all content pages systematically, distinguishing between content pages and application pages
-   - Extract and analyze key topics, themes, and concepts from each page
-   - Identify content relationships and thematic clusters
-   - Map content hierarchy and topical relevance
-   - Note whether content is in TSX templates or MDX files
-
-2. **Link Opportunity Identification:**
-   - Find natural anchor text opportunities within existing content
-   - Identify orphaned pages that lack internal links
-   - Detect content gaps where reciprocal linking would benefit users
-   - Prioritize high-value linking opportunities based on:
-     - Topical relevance (primary factor)
-     - User journey logic
-     - Content depth and authority
-     - Search intent alignment
-
-3. **Implementation Strategy:**
-   - Create semantically meaningful anchor text that describes the destination
-   - Avoid generic anchors like 'click here' or 'read more'
-   - Implement 3-5 contextual links per content page as a baseline
-   - Ensure bidirectional linking between closely related topics
-   - Maintain natural link density without over-optimization
-   - Preserve existing valuable links while adding new ones
-
-4. **Technical Implementation:**
-   - For TSX files: Add links using appropriate React/Next.js Link components
-   - For MDX files: Use markdown link syntax or MDX components as appropriate
-   - Ensure all internal links use relative paths
-   - Maintain consistent link formatting across the site
-   - Verify link destinations exist and are accessible
-
-5. **Best Practices You Follow:**
-   - Link from high-authority pages to important but lower-authority pages
-   - Create topic clusters with pillar pages and supporting content
-   - Use descriptive, keyword-rich (but natural) anchor text
-   - Distribute links throughout content, not just in navigation
-   - Prioritize links in the main content body over sidebar/footer links
-   - Avoid linking to the same page multiple times with identical anchors
-   - Consider user intent and logical next steps in the user journey
-
-6. **Quality Assurance:**
-   - Verify all links resolve correctly
-   - Ensure anchor text accurately represents destination content
-   - Check for broken link patterns or circular linking issues
-   - Validate that link additions maintain content readability
-   - Confirm compliance with accessibility standards (descriptive link text)
-
-**Output Approach:**
-
-When implementing changes:
-1. First provide a brief analysis of linking opportunities discovered
-2. List the specific links you're adding, including:
-   - Source page
-   - Destination page
-   - Anchor text used
-   - Rationale for the link
-3. Edit files directly to implement the links
-4. Summarize the improvements made and expected benefits
-
-**Important Constraints:**
-- Never create new content pages; only add links to existing content
-- Don't modify application logic or functional components
-- Preserve all existing content while adding links
-- Avoid over-optimization that could appear manipulative
-- Respect any existing link attributes (nofollow, sponsored, etc.)
-
-You approach each task methodically, ensuring that every internal link you add serves both user navigation and SEO purposes. Your work creates a web of interconnected content that guides users naturally through related topics while signaling content relationships to search engines.

package/skills/pre-publish-review/SKILL.md

@@ -1,179 +0,0 @@
----
-name: pre-publish-review
-description: The combined pre-publish gate - one pass for SEO (meta tags, structured data, internal linking, content optimization) and one for editorial quality (grammar, tone, clarity, reading level, terminology, claims policy). Use before shipping any new or rewritten page, or when asked to review, edit, proofread, or QA a page. This is the final review after the required content passes.
----
-
-<!-- publisher-seo-kit:content-workflow-route v2 -->
-## Required content passes
-
-When this skill writes or revises public-facing prose, follow this package's pipeline order (the skills are siblings in this package): `source-cited-content-builder` →
-`source-cited-humanizer` → `content-defingerprinting` → `internal-linking-optimizer`,
-then the applicable image and `pre-publish-review` steps. Apply linking and review to
-the actual surface, including outreach email and third-party placements. Keep existing
-send/publish approvals. A pass not run is not a pass completed.
-<!-- /publisher-seo-kit:content-workflow-route -->
-
-
-# Pre-Publish Review
-
-Two review passes over the page, one report. Pass A is the SEO gate; pass B is the
-editorial gate. Resolve the site's domain, niche, page types, voice, and claims
-policy from `.claude/SITE.md` before starting (start from
-`templates/SITE.template.md` in this package if the project has none). Review the RENDERED page where
-possible, not just the source.
-
-## Pass A: SEO review
-
-### Meta tags and titles
-
-- Title tag: 50-60 characters (and under ~600 rendered pixels), primary keyword included
-- Meta description: 150-160 characters, compelling, ends on a complete sentence
-- Canonical URL set; Open Graph and Twitter Card tags present
-- No duplicate titles or descriptions across pages
-
-### Structured data (JSON-LD)
-
-- Organization schema site-wide; BreadcrumbList for navigation
-- Page-type schema where it fits: Article for editorial pages, Product/Review ONLY
-  where the page genuinely contains a review, FAQPage where a real FAQ renders,
-  HowTo for step-by-step guides, LocalBusiness only if the site serves local intent
-- The same content must feed the schema and the visible page (no schema-only FAQs)
-- Validate: no errors in Google's Rich Results Test
-
-### Internal linking
-
-- 3+ outbound internal links to related pages, descriptive anchors (never "click here")
-- 3+ INBOUND links from established pages: run the orphan check from
-  `internal-linking-optimizer`; a page nothing links to is invisible
-- Hub pages link to all their spokes; important pages within 3 clicks of home
-
-### Content optimization
-
-- Exactly one H1, matching page intent; clean H1 > H2 > H3 hierarchy
-- Primary keyword in the first 100 words; natural density (do not stuff)
-- Alt text on all images; keyword or synonym in alt text and file name where honest
-- External links to authoritative sources
-- No keyword cannibalization: this page's title and inbound anchors must not
-  compete with an existing page's primary target
-
-### Technical
-
-- Clean URL structure; page present in the sitemap; mobile responsive; no broken links
-
-### Page types and keyword targets
-
-Derive the real patterns from SITE.md. Generic examples for a comparison publisher:
-
-| Page type | Key SEO elements | Keyword pattern |
-|-----------|------------------|-----------------|
-| Category hub (`/guides/`) | Head keywords, links to every child | "[category]", "best [category]" |
-| Comparison (`/compare/x-vs-y/`) | "X vs Y" intent, comparison table, FAQ | "[X] vs [Y]", "difference between [X] and [Y]" |
-| Review (`/reviews/<vendor>/`) | Review/Product schema, evidence-first, disclosure | "[brand] review", "is [brand] legit" |
-| Topic explainer (`/what-is-[topic]/`) | Definitional intent, answer-first intro | "what is [topic]", "[topic] explained" |
-| Tool (`/[task]-calculator/`) | Utility intent | "[task] calculator" |
-
-## Pass B: Editorial review
-
-### Tone and voice
-
-Resolve the target voice from SITE.md and hold every page to it. For a comparison
-site the reader is a careful buyer checking your work, so evidence beats enthusiasm.
-Reader-first, direct, trustworthy; claims carry evidence. No hype, no condescension,
-no undefined niche jargon.
-
-### Clarity and readability
-
-- Reading level: target 8th grade (Flesch-Kincaid)
-- Sentences: 15-20 words average; paragraphs: 2-4 sentences
-- Active voice: "You compare the prices", not "The prices are compared"
-- Define technical terms on first use
-
-### Consistency
-
-- One term per concept, enforced from the SITE.md terminology table. Sample for a
-  health-adjacent comparison site (note the claims-policy rows):
-
-| Use | Don't use |
-|-----|-----------|
-| research compound | supplement, medication |
-| third-party tested (with a published CoA) | lab tested (unverified) |
-| certificate of analysis (CoA) | test paper, lab sheet |
-| price per mg | cost (when comparing value) |
-| you | one, the customer |
-
-- Spell out one through nine, numerals for 10+; always numerals for money,
-  percentages, ages. Dates spelled out (January 15, 2026).
-- Consistent bold/bullets/callouts; descriptive link text
-
-### Accuracy and currency
-
-- Verify numbers, dates, names against their sources; is the information still current?
-- Links work and go to the right place; sources cited where needed; nothing missing
-
-### Claims policy (health-adjacent niches)
-
-Any medical, dosage, or "safe/effective for humans" language about research
-compounds is a CRITICAL finding. Affiliate disclosure must be present on pages
-with affiliate links. See SITE.md claims policy.
-
-## Red flags to report (either pass)
-
-1. Duplicate meta/title across pages, missing H1, or thin content (<300 words on a substantive topic)
-2. Keyword stuffing or unnatural repetition
-3. Missing or wrong schema on key pages; schema asserting content the page lacks
-4. Orphan pages and broken internal links
-5. Missing image alt text
-6. Hype where the reader wants evidence; passive-voice walls; undefined jargon
-7. Inconsistent terminology ("CoA" here, "lab report" there)
-8. Outdated facts (old prices, defunct links); incomplete instructions
-9. Claims-policy violations and missing affiliate disclosure
-
-## Output format
-
-```markdown
-## Pre-Publish Review: [Page URL]
-
-### Verdict: SHIP | FIX FIRST | REWORK   (overall grade A-F)
-
-### SEO (Pass A)
-- Title: "[current]" - [OK/issue]
-- Description: "[current]" - [OK/issue]
-- Canonical/OG: [OK/missing]
-- Schema: [types present] - [missing/errors]
-- H1 + hierarchy: [OK/issue]
-- Internal links: [X] out / [X] in - orphan: [yes/no]
-- Keyword: "[primary]" placement [OK/issue]; cannibalization risk: [none/page]
-
-### Editorial (Pass B)
-- Voice fit (SITE.md): [good/needs work]
-- Grade level: [X]; avg sentence: [X] words; passive: [X]%
-- Terminology: [consistent/list conflicts]
-- Claims policy: [clean/VIOLATIONS listed first]
-
-### Issues (ranked, most severe first)
-1. [Location]: "[original]" -> issue -> "[suggested fix]"
-
-### Quick wins
-1. [Easy improvement]
-```
-
-## Sample rewrites (the editorial bar)
-
-Too vague:
-> This vendor is arguably one of the better options currently available on the market.
-
-Evidence-first:
-> This vendor publishes a third-party CoA for every batch and shipped our test order in two days. Most competitors do neither.
-
-Too complex:
-> The product is subjected to independent HPLC verification protocols to substantiate purity assertions.
-
-Simple and direct:
-> An independent lab tests each batch for purity using HPLC. The vendor publishes the results, so you can check them yourself.
-
-## Relationship to sibling skills
-
-- `onpage-seo-audit` REFACTORS a page (keyword/entity/schema work); this skill GATES
-  it. Run the audit to fix, this review to ship.
-- The banned-phrase scan is `source-cited-humanizer`, using `source-cited-content-builder` rules;
-  run it before this review, not instead of it.

package/skills/source-cited-content-builder/SKILL.md

@@ -1,56 +0,0 @@
----
-name: source-cited-content-builder
-description: Write or refactor source-cited web content with a concise human tone, strict citation fields, grammar constraints, no em dashes, and a large banned phrase list. Use for content building, content humanizing, blog/page copy, guides, comparison and review pages, and SEO content drafts that must follow the site's exact source and style rules.
----
-
-<!-- publisher-seo-kit:content-workflow-route v2 -->
-## Required content passes
-
-When this skill writes or revises public-facing prose, follow this package's pipeline order (the skills are siblings in this package): `source-cited-content-builder` →
-`source-cited-humanizer` → `content-defingerprinting` → `internal-linking-optimizer`,
-then the applicable image and `pre-publish-review` steps. Apply linking and review to
-the actual surface, including outreach email and third-party placements. Keep existing
-send/publish approvals. A pass not run is not a pass completed.
-<!-- /publisher-seo-kit:content-workflow-route -->
-
-
-# Source-Cited Content Builder
-
-Use this skill when writing or revising content that must follow the user's citation, grammar, and banned-phrase rules.
-
-## Workflow
-
-1. Read `references/source-prompt.md` before writing or editing content.
-2. Gather facts from reputable, citable sources. Favor government, standards bodies, utilities, manufacturers, and recognized industry publications. Add your niche's preferred primary sources on top (SITE.md). For a comparison site in a regulated niche that means peer-reviewed literature, supplier certificates of analysis, and the relevant regulator's pages, and never marketing claims from vendors.
-3. Record each unique source with Title, Publisher, Publication Date, and URL.
-4. Draft concise, conversational copy using active voice.
-5. Check the copy against the banned word and phrase list in the source prompt.
-6. Remove em dashes from the final content.
-7. Before treating the page as ready, run your site's pre-publish SEO checklist (info-gain, answer-first, entity/keyword discipline, internal links, meta length).
-
-## Humanize pass on existing copy
-
-This skill is also the standalone humanizer: run it on ANY content after it is
-written, whoever or whatever wrote it (this is stage 2 of the content pipeline).
-
-1. Read `references/source-prompt.md`.
-2. Scan the file(s) against the full banned word and phrase list, the grammar rules
-   (active voice, concise conversational sentences), and the em-dash ban.
-3. Fix each violation in place; keep meaning, citations, and structure intact.
-4. Report what changed: each banned term found and its replacement.
-
-Nothing else in a typical build chain checks tone. A page can pass every structural
-gate and still read as AI slop; this pass is the only thing standing in the way.
-
-## Guardrails
-
-- Do not invent facts or cite weak sources when official sources exist.
-- Keep source records near the content or in the repo's existing citation field format.
-- In a YMYL or YMYL-adjacent niche (legal, financial, health-adjacent, research compounds), pair this skill with your site's compliance review (SITE.md claims policy) before public-facing publication.
-
-## The prompt reference
-
-`references/source-prompt.md` is generic and applies to any site: the citation
-fields, the grammar rules, and the ~600-term banned-phrase list are in force
-verbatim. The one thing the operator adds is niche-specific source preferences
-(step 2 above), recorded in SITE.md, not by editing the reference.

package/skills/source-cited-content-builder/references/source-prompt.md

@@ -1,19 +0,0 @@
-content building
-
-
-The following are strict requirements for the content above:
-
-Source citing rules:
-- Pull facts only from reputable, citable sources.
-- Favor government sites, standards bodies, utilities, manufacturers, and recognized industry publications.
-- Record each unique source as: Title, Publisher, Publication Date, URL.
-
-Grammatical rules:
-- No em dashes.
-- Active voice.
-- Concise, conversational sentences.
-- Use short transitional prompts to keep readers moving, such as “Here is why,” “Let’s break it down,” and “Next steps.”
-- No contrast-frame constructions: never write "it's not X, it's Y" or "this isn't just X, it's Y". State what the thing is directly.
-
-Banned words and phrases
-Avoid every word or phrase in this list:  Accordingly, Additionally, Arguably, Certainly, Consequently, Hence, However, Indeed, Moreover, Nevertheless, Nonetheless, Notwithstanding, Thus, Undoubtedly, Adept, Commendable, Dynamic, Efficient, Ever-evolving, Exciting, Exemplary, Innovative, Invaluable, Robust, Seamless, Synergistic, Thought-provoking, Transformative, Utmost, Vibrant, Vital, Efficiency, Innovation, Institution, Integration, Implementation, Landscape, Optimization, Realm, Tapestry, Transformation, Aligns, Augment, Delve, Embark, Facilitate, Maximize, Underscores, Utilize, A testament to, In conclusion, In summary, It's important to note/consider, It's worth noting that, On the contrary, This is not an exhaustive list, A journey of, A multitude of, A plethora of, Actionable insights, Adoption rate, Aforementioned, Agile, AI-powered, Ample opportunities, Amplify, Arduous, As a result, As such, At length, At the end of the day, Bandwidth, Based on the information provided, Basic, Best practices, Blockchain-enabled, Brand awareness, Broadly speaking, Burgeoning, Cannot be overstated, Capacity building, Captivating, Change management, Cloud-based, Cognizant, Collaborative environment, Competitive landscape, Complexity, Conceptualize, Conducting, Considerable, Continuous improvement, Core, Corporate social responsibility, Cost optimization, Craft, Critical, Crucial, Customer loyalty, Customer satisfaction, Customer-centric, Cutting-edge, Data-driven, Decision-makers, Deep dive, Deep dive into, Deep understanding, Deliverables, Delve into, Delved, Delving, Delving into the intricacies of, Demonstrates significant, Deployment plan, Digital realm, Digital transformation, Disruptive innovation, Domain expertise, Downtime, Drive, Driven approach, Driving innovation, Dynamic environment, Elevate, Embark on a journey, Embark on a voyage, Embarked, Emerging technologies, Empower, Enable, Encountered hurdles, Enhance, Enhancing, Enlightening, Enriches, Entails, Entrenched, Epicenter, Essential, Essentially, Esteemed, Ethical considerations, Excels, Expertise, Explore, Flourishing, Folks, For example, For instance, Foray, Foster, Foster innovation, Fostering, Fresh perspectives, From inception to execution, Fundamental, Fundamentally, Furthermore, Future-proof, Game changer, Game-changer, Generally speaking, Given that, Glean, Going forward, Golden ticket, Governance framework, Granular, Granular detail, Granular level, Granularly, Grasp, Groundbreaking, Growing recognition, Herein, Heretofore, High-level, Hinder, Holistic, Holistically, Impactful, Implementation strategy, Implications, Important to consider, In a sea of, In brief, In detail, In effect, In essence, In general, In light of, In other words, In particular, In practice, In terms of, In the dynamic world of, In the realm of, In theory, In today's rapidly evolving market, In today's world, Industry best practices, Influencers, Insights into, Issue resolution, It is important to note, It is worth noting, It's important to remember, Iteration, Kaleidoscope, Key, Key takeaways, Knowledge transfer, KPIs, Latency, Leverage, Linchpin, Low-level, Manifold, Market penetration, Market share, Market trends, Milestone, Mission-critical, Moving forward, Multifaceted, MVP, Namely, Navigating the landscape, Navigating the complexities of, New heights, Next-generation, Notable, Nuanced, Numerous, Offboarding, Offer a comprehensive, Offerings, On the ascent to, On the cutting edge, On the other hand, Onboarding, Operational efficiency, Operational excellence, Optimize, Pain point, Paradigm, Paradigm shift, Paramount, Particularly in areas, Performance optimization, Pervasive, Pivotal, Plethora, POC, Preemptively, Primary, Problem solving, Process optimization, Profitability, Profound, Promote, Pronged, Quality assurance, Quality control, Rapidly evolving, Reaching new heights, Recognize, Regulatory compliance, Relentless, Remarkable, Resonate, Resource allocation, Resource optimization, Revenue growth, Risk mitigation, Roadmap, ROI, Root cause analysis, Scalable, Scrum, Secondary, Shed light, Shedding light on, Showcasing, Significant, Significantly contributes, Simply put, SLA, Solution development, Specifically, Specifically speaking, Sprint, Stakeholders, State-of-the-art, Strategic alignment, Streamline, Strive, Strong presence, Subject matter experts, Substantial, Substantially, Sustainability, Synergistically, Synergy, Systemic, Tailor, TCO, Tertiary, That being said, The future of, The linchpin of, The next frontier, The power of, The road ahead, Thereby, Therefore, Therein, Thereof, Thought leaders, Thought leadership, Thrive, Thriving, Throughput, Time optimization, To clarify, To demonstrate, To elevate, To elucidate, To emphasize, To empower, To enhance, To enrich, To exemplify, To furnish, To highlight, To illustrate, To provide, To reiterate, To shed light on, To showcase, To summarize, To thrive, To underscore, To unleash, To unlock, Touchpoint, Transforming the way, Treasure trove, Ultimately, Uncharted waters, Undeniable, Understanding of your unique, Unleash, Unlock, Unparalleled, Uptime, User engagement, User experience, User feedback, User interface, Valuable, Value proposition, Value-added, Various, Vast, Well-crafted, Whilst, Whilst it is true, Widely recognized, With a keen eye on, With regards to

package/skills/source-cited-humanizer/SKILL.md

@@ -1,20 +0,0 @@
----
-name: source-cited-humanizer
-description: Run the required editorial humanizing pass after drafting or revising public content. Apply the source-cited-content-builder's canonical voice and banned-phrase rules while preserving facts, meaning and citations.
----
-
-# Source-cited humanizer
-
-Run as a separate pass after writing, including outreach copy, contributed articles,
-placement content and adapted social posts. Read the sibling
-`source-cited-content-builder/SKILL.md` and its `references/source-prompt.md`; they
-own the voice rules and banned list. Use the site's more specific voice references
-when present. Do not maintain a second copy of the banned list.
-
-Review titles, headings, descriptions and body copy. Remove formulaic framing,
-repetition, unsupported certainty, banned phrases and em dashes. Keep useful specifics,
-source records and the author's actual meaning. Never invent anecdotes or measurements.
-Use the builder's humanize-pass procedure and report the material edits.
-
-Next run `content-defingerprinting`, then `internal-linking-optimizer` for the actual
-publishing surface. A clean technical build does not replace this editorial pass.