feat(content): add Plasma Wiki skill

[ryanpettry]

Summary

Adds Plasma Wiki as one focused Skills content entry. Plasma Wiki is an Apache-2.0 CLI and agent skill for indexed Markdown knowledge bases with deterministic map, search, read, update, and lint workflows.

Submission path

No linked issue: this is a free-resource content submission using the direct PR path documented in CONTRIBUTING.md. The repository issue form is reserved for product and feature work and explicitly directs free content submissions to the PR-first flow.

This supersedes #5542 and #5543, which were closed by the previous automated issue-link gate.

Improvements in this submission

• Pins the download archive to the immutable v1.1.0 tag instead of the main branch.
• Adds plasma-ai/plugins to the verification sources for the documented Claude Code and Codex marketplace installation routes.
• Keeps the change scoped to one raw content/skills/plasma-wiki.mdx entry with no generated artifacts.
• Includes source, install, compatibility, disclosure, safety, privacy, and duplicate-review details.

Validation

• pnpm validate:content:strict — passed; validated 1,386 content files. The reported 24 warnings are pre-existing entries unrelated to this change.
• git diff --check — passed.
• No visual impact; content-only submission.

Disclosure

I am affiliated with Plasma AI, which maintains Plasma Wiki.

[loopover-orb]

Caution

🛑 LoopOver review result - reject/close recommended

_{Review updated: 2026-07-27 19:04:00 UTC}

1 file · 1 AI reviewer · 1 blocker · CI green · clean

🛑 Suggested Action - Reject/Close

Review summary
The PR adds a new 'plasma-wiki' skill entry to the 'skills' category, providing comprehensive metadata and verification sources. The change is scoped to a single MDX file with no generated artifacts, aligning with the repository's content submission guidelines. The entry includes detailed safety/privacy notes and addresses duplicate review concerns.

Nits — 4 non-blocking

• The 'difficultyScore' of 64 might benefit from clarification (is this a 0-100 scale?); consider adding a note if this is a standardized metric.
• Verify all URLs in 'retrievalSources' and 'sourceUrls' are active and point to the correct v1.1.0 release
• Consider adding a brief note in 'safetyNotes' explicitly stating the Apache-2.0 license for transparency
• Diff looks like trivial or whitespace-only churn — Reduce whitespace-only or formatting-only churn and keep the diff focused on substantive changes.

Why this is blocked

• No linked issue detected: No closing reference or linked issue number was found in the PR metadata/body. — If this PR is intended to solve an issue, link it explicitly in the PR body.

📋 Copy for AI agents — paste into your coding agent

Fix the following blocker(s) from this PR review:

1. No linked issue detected: No closing reference or linked issue number was found in the PR metadata/body. — If this PR is intended to solve an issue, link it explicitly in the PR body.

Decision drivers

• ❌ Code review — 1 blocker (1 reviewer)
• ❌ Gate result — Blocking (Repo-configured hard blocker found.)

Context & advisory signals — never blocks the verdict

Signal	Result	Evidence
Linked issue	✅ No-issue rationale	PR body explains why no issue is linked.
Related work	✅ No active overlap found	No same-issue or scoped active PR overlap found.
Change scope	✅ 20/20	Low review scope from cached public metadata (no linked issue context).
Validation posture	✅ 25/25	PR body includes validation/test evidence.
Contributor workload	✅ 10/10	Author activity: 0 registered-repo PR(s), 0 merged, 0 issue(s).
Contributor context	ℹ️ No public Gittensor match	ryanpettry; not a blocker.
Improvement	ℹ️ Insufficient signal	risk: low · value: insufficient-signal

Review context

• Author: ryanpettry
• Role context: outside_contributor
• Public audience mode: oss maintainer
• Lane context: Repository is configured for direct PR review.
• Public profile languages: not available
• Contributor context: Public profile only; not a blocker.
• PR-specific overlap: none found.

Contributor next steps

• Keep the PR focused and include validation evidence before maintainer review.

Signal definitions

• Related work = same linked issue, overlapping active PRs, or title/path similarity.
• Change scope = cached public metadata such as size labels, draft state, and review-burden hints.
• Validation posture = whether the PR provides enough public validation/test evidence for maintainer review.
• Contributor workload = public contributor activity and cleanup pressure, not a repo-wide quality failure.
• Contributor context = public GitHub/Gittensor identity context; non-Gittensor status is not a blocker.

🧪 Chat with LoopOver

Ask LoopOver a question about this PR directly in a comment — grounded only in the same cached, public-safe facts shown above, never a new claim.

• @loopover ask <question> answers contribution-quality Q&A with source citations and freshness.
• @loopover chat <question> answers in natural prose from cached decision-pack facts via local inference (maintainer/collaborator; read-only).
• A plain-language @loopover mention with a real question is routed to the closest matching read-only command automatically — no exact syntax required.

Full command reference: https://loopover.ai/docs/loopover-commands

🧪 Experimental — new and may change.

Decision record

• action: hold · clause: missing_linked_issue
• config: d7e545c82b455c21587ee8f7bc9026fe57068ccc92e696aca30c4dbe035f5e91 · pack: oss-anti-slop · ci: passed
• note: diverted by the randomized close-audit holdout (#8831) — the deterministic pipeline would otherwise have closed this PR
• record: b8d250ead3640ddd8dc1dedf8ddcecd3d09a7bbd033005bad36870b1cd4da428 (schema v5, head 6f017c2)

Visual preview

Route	Viewport	Before (production)	After (this PR's preview)	Diff
/	desktop (light)	before / (light)	after / (light)	—
/	mobile (light)	before / (mobile) (light)	after / (mobile) (light)	—
/	desktop (dark)	before / (dark)	after / (dark)	—
/	mobile (dark)	before / (mobile) (dark)	after / (mobile) (dark)	—

Click any thumbnail to open the full-size screenshot. Before = production · After = this PR's preview deploy.

Scroll preview

Route	Before (production)	After (this PR's preview)
/ (light)	—	after / (light) (scroll)
/ (dark)	before / (dark) (scroll)	after / (dark) (scroll)

A short scroll-through clip (desktop) — click either thumbnail to open the full animation. Evidence for scroll-linked behavior a single screenshot can't show.

_{🟩 Safe / merged · 🟦 Advisory · 🟨 Held for review · 🟥 Blocked / closed}

---

💰 Earn for open-source contributions like this. Gittensor lets GitHub contributors earn for the work they already do — register to start earning →.

Checked by LoopOver, a quiet PR intelligence layer for OSS maintainers.

• Re-run LoopOver review