diff --git a/CLAUDE.md b/CLAUDE.md
index 62582b54f..865b68689 100644
--- a/CLAUDE.md
+++ b/CLAUDE.md
@@ -133,10 +133,10 @@ created: YYYY-MM-DD
 ---
 
 Relevant Notes:
-- [[related-claim]] — how it relates
+- related-claim — how it relates
 
 Topics:
-- [[domain-map]]
+- domain-map
 ```
 
 ## How to Propose Claims (Proposer Workflow)
@@ -240,7 +240,7 @@ For each proposed claim, check:
 5. **Duplicate check** — Does this already exist in the knowledge base? (semantic, not just title match)
 6. **Contradiction check** — Does this contradict an existing claim? If so, is the contradiction explicit and argued?
 7. **Value add** — Does this genuinely expand what the knowledge base knows?
-8. **Wiki links** — Do all `[[links]]` point to real files?
+8. **Wiki links** — Do all `links` point to real files?
 9. **Scope qualification** — Does the claim specify what it measures? Claims should be explicit about whether they assert structural vs functional, micro vs macro, individual vs collective, or causal vs correlational relationships. Unscoped claims are the primary source of false tensions in the KB.
 10. **Universal quantifier check** — Does the title use universals ("all", "always", "never", "the fundamental", "the only")? Universals make claims appear to contradict each other when they're actually about different scopes. If a universal is used, verify it's warranted — otherwise scope it.
 11. **Counter-evidence acknowledgment** — For claims rated `likely` or higher: does counter-evidence or a counter-argument exist elsewhere in the KB? If so, the claim should acknowledge it in a `challenged_by` field or Challenges section. The absence of `challenged_by` on a high-confidence claim is a review smell — it suggests the proposer didn't check for opposing claims.
@@ -323,7 +323,7 @@ When your session begins:
 ## Design Principles (from Ars Contexta)
 
 - **Prose-as-title:** Every note is a proposition, not a filing label
-- **Wiki links as graph edges:** `[[links]]` carry semantic weight in surrounding prose
+- **Wiki links as graph edges:** `links` carry semantic weight in surrounding prose
 - **Discovery-first:** Every note must be findable by a future agent who doesn't know it exists
 - **Atomic notes:** One insight per file
 - **Cross-domain connections:** The most valuable connections span domains
diff --git a/skills/handoff.md b/skills/handoff.md
index 4ee9bedba..499b6f04d 100644
--- a/skills/handoff.md
+++ b/skills/handoff.md
@@ -44,7 +44,7 @@ The bad version forces Rio to re-derive the connection. The good version tells h
 
 ## Rules
 
-1. **Be specific about which claims are affected.** Link to them with `[[wiki links]]`.
+1. **Be specific about which claims are affected.** Link to them with `wiki links`.
 2. **Include artifacts.** If you have a file the other agent should read, give the path.
 3. **Recommend an action.** Don't just flag — tell them what you think they should do.
 4. **Priority is honest.** Most handoffs are routine. "Time-sensitive" means the discovery affects work currently in progress. "Blocking" means their current task can't proceed without this.