Is jiang-episode-publisher safe to install?

SaferSkills independently audited jiang-episode-publisher (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.

CategoryWeightCategory scoreContribution

Securityprompt, exec, net, exfil, eval

35%

100

35.0 pts

Supply chainhash, typosquat, maintainer, lockfile

20%

100

20.0 pts

Maintenancestaleness, pinning, CI

15%

100

15.0 pts

TransparencySKILL.md, perms, README

15%

100

15.0 pts

Communityinstalls, verify, response

15%

100

15.0 pts

Findings & checks · 0 flagged

Securityscore 100 · 0 findings

✓—All security checks passedNo findings in this category for the latest scan.pass

Supply chainscore 100 · 0 findings

✓—All supply chain checks passedNo findings in this category for the latest scan.pass

Maintenancescore 100 · 0 findings

✓—All maintenance checks passedNo findings in this category for the latest scan.pass

Transparencyscore 100 · 0 findings

✓—All transparency checks passedNo findings in this category for the latest scan.pass

Communityscore 100 · 0 findings

✓—All community checks passedNo findings in this category for the latest scan.pass

The primary manifest — the file an agent reads to learn what this artifact does.

.codex/skills/jiang-episode-publisher/SKILL.md · 1 file

.codex/skills/jiang-episode-publisher/SKILL.md2.2 KB · Markdown

name: jiang-episode-publisher

description: Use this skill when taking an already-ingested Jiang Lens source and an existing episode/interview read JSON through generated website data, route validation, transcript/video linkage, and public-site build checks.

Jiang Episode Publisher

Use this after content/lens/episodes/<source-slug>/read.json exists. This skill is mechanical publication and validation. It should not become the episode writer.

Inputs

content/sources/videos/<source-slug>/
content/lens/evidence/videos/<source-slug>.semantic.json
content/lens/episodes/<source-slug>/read.json
compiler scripts under ops/scripts/

Flow

Compile content:

node ops/scripts/compile-content.mjs

Validate content:

node ops/scripts/validate-content.mjs

Build the website:

cd website && npm run build

Verify expected outputs:

website/src/data/lens/episodes/<source-slug>.json
/episodes/<source-slug>/
/episodes/<source-slug>/transcript/

# or, when source_class is interview:
website/src/data/lens/interviews/<source-slug>.json
/interviews/<source-slug>/
/interviews/<source-slug>/transcript/

If a dev server is running, spot-check the episode and transcript routes. For UI changes, take screenshots before accepting.

Checks

Confirm:

the episode or interview page renders,
the transcript page renders,
the video ID is present,
timestamp links seek the video,
transcript current-segment highlighting works,
phrase-level highlighting exists only when timed_chunks exist,
evidence marks and lens point hovers render without broken refs,
generated data is fresh.

Boundary

Do not rewrite public prose except for small structural fixes required by validation. If the read is shallow, wrong, or missing Jiang's voice, hand it back to jiang-episode-read-writer.

Do not edit generated files by hand.

After successful publication, stop. Corpus impact, lens links, concept extension, new lens seeds, atlas mutation, and canon-candidate review are downstream jobs for separate agents. Mention obvious follow-up in the handoff, but do not create or require corpus-impact.json as part of episode publication.

jiang-episode-publisher— agent skill

Is jiang-episode-publisher safe to install?

Jiang Episode Publisher

Inputs

Flow

Checks

Boundary

Audit the pieces. Scan the whole. Decide.