Atlas / Skills / galaxy-dawn / Obsidian Literature Workflow

Obsidian Literature WorkflowSAFE

skills/galaxy-dawn/obsidian-literature-workflow

Semi-automated research assistant for academic research and software development. Supports Claude Code, Codex CLI, Kimi Code CLI, and OpenCode across ideation, coding, experiments, writing, and publication.

Verdict
SAFE
Grade
B
Trust score
89 /100
Version
1.0.0
Hosts
—
License
MIT
Stars
5,693
01

Overview

Semi-automated research assistant for academic research and software development. Supports Claude Code, Codex CLI, Kimi Code CLI, and OpenCode across ideation, coding, experiments, writing, and publication.

Read from source at commit 29ad4d4206fbOBSERVED · 2026-10-07
02

What it tells the agent

The instruction file, verbatim from the audited commit — this is the text the model reads, and the surface the audit's instruction layer examines. Quoted here so you can judge it without cloning anything.

---
name: obsidian-literature-workflow
description: Use this skill for project-scoped literature review built on Sources/Papers, with synthesis landing in Knowledge, writing handoff in Writing, and the default literature canvas under Maps/literature.canvas.
version: 1.0.0
---

# Obsidian Literature Workflow

This skill owns the **project literature workflow**.

## Main flow

```text
Sources/Papers/ -> Knowledge/ -> Writing/ -> Maps/literature.canvas
```

## Default outputs

- `Sources/Papers/{paper-slug}.md`
- `Knowledge/Literature Overview.md`
- `Knowledge/Method Taxonomy.md`
- `Knowledge/Research Gaps.md`
- `Knowledge/Claim Map.md`
- `Writing/related-work-draft.md` only after promoted claims pass the evidence gate
- `Writing/comparison-matrix.md` only after promoted claims pass the evidence gate
- `Maps/literature.canvas`

## Rules

- paper notes stay under `Sources/Papers/`
- literature synthesis does not live inside source notes
- every synthesis note must link its supporting source notes
- every research gap must carry evidence
- every promoted claim must carry an Evidence Record ID, source type, claim strength, allowed wording, and forbidden stronger wording when it may flow into writing or rebuttal
- weak paper notes, abstract-only pages, and webpage placeholders may update coverage or `To-Read`, but they cannot support `Knowledge` or `Writing` conclusions
- default graph output is `Maps/literature.canvas`
- do not generate extra canvases unless explicitly requested

## Read next

- `references/PAPER-NOTE-SCHEMA.md`
- `references/LITERATURE-OVERVIEW.md`
- `references/CLAIM-EXTRACTION.md`
- `references/METHOD-TAXONOMY.md`
- `references/RESEARCH-GAPS.md`
- `references/LITERATURE-CANVAS.md`
03

Trust audit

SAFEgrade B · trust 89/100 Nothing in the source contradicts what it says it does. Grade A is reserved for packages that have also passed the behavioural sandbox.

LayerWhat it checksResult
L0Provenance & inventoryPASS
L1Static analysis of the codePASS
L2Instruction surface (what it tells the agent)PASS
L3Class-specific surfacePASS
L4Behavioural (sandbox)SKIPPED

What the source does

Filesystem
none-observed
Network
none-observed
Shell
none-observed
Dependencies
pinned
Secrets in source
none-found

Findings (2)

LOWInsecure crypto · crypto.weak_hash · CWE-327, CWE-338
scripts/build_literature_canvas.py:210
digest = hashlib.sha1(f"{prefix}:{value}".encode("utf-8")).hexdigest()
LOWInsecure crypto · crypto.weak_hash · CWE-327, CWE-338
scripts/build_literature_canvas.py:254
digest = hashlib.sha1(f"{source}:{target}:{label}".encode("utf-8")).hexdigest()

Gates applied: no_behavioural_pass.

Audited 2026-10-07 · audit v0.4.1 · source sha 29ad4d4206fbfull audit observations/trust-audit/skill/galaxy-dawn__obsidian-literature-workflow.json · Report an issue / request a re-scan
04

Audit history

Every audit this skill has had.

DateSourceVerdictGradeScoreChange
2026-10-0729ad4d4206fbSAFEB89first audit
05

Questions

What does the Obsidian Literature Workflow skill do?

Semi-automated research assistant for academic research and software development. Supports Claude Code, Codex CLI, Kimi Code CLI, and OpenCode across ideation, coding, experiments, writing, and publication.

Is Obsidian Literature Workflow safe to install?

The audit found nothing in the source that contradicts what it says it does, and graded it B (89/100). Grade A is held back for packages that have also passed a sandboxed behavioural run, which is why a clean skill reads B.

What can Obsidian Literature Workflow access on my machine?

The audit observed no filesystem, network or shell use at all in its source.

How current is this page?

The grade is for one exact copy of the source (29ad4d4206fb), read on 2026-10-07. The repository is watched, and a new audit runs when it changes — this is the first audit.

Advertisement