Use this skill when generating higher-level synthesis notes such as literature reviews, comparison matrices, project summaries, or other cross-note summaries inside the project knowledge base.
Scanned 9/2/2026
Install to Claude Code
npx -y skills add majiayu000/claude-skill-registry --skill obsidian-synthesis-map --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Obsidian Synthesis Map?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/majiayu000-obsidian-synthesis-map)More formats (shields.io, HTML) on the badges page.
---
name: obsidian-synthesis-map
description: Use this skill when generating higher-level synthesis notes such as literature reviews, comparison matrices, project summaries, or other cross-note summaries inside the project knowledge base.
---
# Obsidian Synthesis Map
This is a **legacy compatibility helper**.
Despite the name, the current default workflow focuses on **synthesis notes**, not Bases or Canvas artifacts.
## Default outputs
- `Writing/` synthesis notes
- project summaries tied to `Knowledge/`, `Papers/`, `Experiments/`, and `Results/`
- comparison notes that help writing, planning, or result interpretation
## Guidelines
- Use `obsidian-project-memory` as the main workflow authority.
- Use `$obsidian-markdown` for note quality.
- Keep synthesis notes anchored to real papers, experiments, results, and project questions via wikilinks.
- Prefer one durable synthesis note per purpose instead of many overlapping summaries.
- If the user explicitly asks for `.base` or `.canvas` artifacts, treat them as optional add-ons, not default outputs.
## Default stance
Do **not** generate:
- `Views/*.base`
- `Maps/*.canvas`
unless the user explicitly asks for those artifacts.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!
Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...
Ultra-compressed communication mode. Cuts token usage ~75% by speaking like caveman while keeping full technical accuracy. Supports intensity levels: lite, full (default), ultra, wenyan-lite, wenyan-full, wenyan-ultra. Use when user says "caveman mode", "talk like caveman", "use caveman", "less tokens", "be brief", or invokes /caveman. Also auto-triggers when token efficiency is requested.
**Complete production-ready guide for Google Gemini embeddings API** This skill provides comprehensive coverage of the `gemini-embedding-001` model for generating text embeddings, including SDK usage, REST API patterns, batch processing, RAG integration with Cloudflare Vectorize, and advanced use cases like semantic search and document clustering. ---
Interview, source-challenge, verify, save, and ADR-gate fuzzy coding requests into Codex-ready implementation specs. Use when a feature, bugfix, refactor, migration, repo-wide change, or architecture task needs user-verified requirements, source-backed decisions, durable architecture decisions, acceptance criteria, validation commands, rollout notes, saved spec/ADR files, and a Codex execution prompt. Do not use when already fully specified or when the user wants direct implementation now.
Use when a repo needs CodeGraph plus ast-grep for Codex MCP setup, exploration, impact analysis, structural search, or safe refactor planning.