📦
planning-with-files
83Organize Long AI Tasks with Planning Files
Long AI sessions can lose goals, decisions, and progress. This skill guides Claude, Codex, and Claude Code to store plans, findings, and logs in project files.
Productivity View
Skills project-to-obsidian
📦
project-to-obsidian
v1.4.0 Content revision r1 High Risk 📁 Filesystem access⚙️ External commands
Convert Projects into Obsidian Knowledge Bases
Project knowledge is often scattered across code, comments, and docs. This skill turns a codebase into linked Obsidian notes for navigation and maintenance.
Supports: Claude Codex Code(CC)
This skill is part of a pack
Install the whole pack to get every skill the task needs, in one command.
Stop for confirmation before installing.
Review the plan and obtain explicit user consent before changing files.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Agent request
Review the Skillstore skill "project-to-obsidian" from https://skillstore.io/skills/zhanlincui-project-to-obsidian.md and its manifest at https://skillstore.io/api/skills/zhanlincui-project-to-obsidian/manifest. Verify the artifact. Stop and obtain explicit user consent before installing or changing files.Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Test it
Using "project-to-obsidian". User requests a quick overview for a TypeScript service.
Expected outcome:
The skill produces a project overview, directory structure note, technology stack note, and links between key modules.
Using "project-to-obsidian". User requests API documentation for a backend.
Expected outcome:
The skill creates endpoint notes with methods, parameters, responses, source file references, and related module links.
Using "project-to-obsidian". User requests full Obsidian vault output.
Expected outcome:
The skill asks for confirmation, creates a project knowledge base, adds indexes, and writes linked notes to the chosen destination.
Security Audit
High Riskv4 • 7/8/2026 Open versioned report
Most static alerts are false positives caused by Markdown code fences, slash-command examples, Obsidian links, Mermaid diagrams, and normal Claude skill installation instructions. I confirmed the .env and configuration scanning guidance because it can expose credentials when generated notes capture environment values. No prompt injection or covert exfiltration language was found.
7
Files scanned
1,074
Lines analyzed
1
Review items
0
False positives ignored
Confirmed security concerns (2)
High
Environment file access
- **/.env*, **/config.* # 配置文件
The scan pattern targets environment files and config files that commonly store secrets. The skill also generates configuration documentation, creating a credible disclosure risk.
High
Potential Secret Disclosure in Generated Documentation
The workflow scans .env and config files, then extracts environment variables and configuration into generated Obsidian documentation. Without redaction, notes can expose credentials or private endpoints.
The file scan pattern and later extraction requirements are explicit. I did not find redaction rules that prevent secret values from being written to notes.
Capability review items (1)
These are real local capabilities that may be expected for this skill, so they require review but are not counted as confirmed malicious behavior.
High
Hidden file access
- **/.env*, **/config.* # 配置文件
The workflow explicitly includes **/.env* in project scans. Hidden environment files often contain credentials, and generated notes may expose those values.
Risk Factors
📁 Filesystem access (3)
⚙️ External commands (65)
SKILL.md:32 SKILL.md:33 SKILL.md:34 SKILL.md:35 SKILL.md:41-106 SKILL.md:106-113 SKILL.md:113-116 SKILL.md:116-119 SKILL.md:119-123 SKILL.md:123-126 SKILL.md:126-137 SKILL.md:137-140 SKILL.md:140-145 SKILL.md:145-155 SKILL.md:155-168 SKILL.md:168-174 SKILL.md:174-185 SKILL.md:185-189 SKILL.md:189-215 SKILL.md:215-219 SKILL.md:219-247 SKILL.md:247-251 SKILL.md:251-279 SKILL.md:279-287 SKILL.md:287-314 SKILL.md:314-316 SKILL.md:316-328 SKILL.md:328-332 SKILL.md:332-345 SKILL.md:345-347 SKILL.md:347-357 SKILL.md:357-359 SKILL.md:359-365 SKILL.md:365-367 SKILL.md:367-373 SKILL.md:373-377 SKILL.md:377-393 SKILL.md:393-395 SKILL.md:395-397 SKILL.md:397-406 SKILL.md:406-408 SKILL.md:408-412 SKILL.md:412-416 SKILL.md:416-422 SKILL.md:422-430 SKILL.md:430-436 SKILL.md:436-440 SKILL.md:440-445 SKILL.md:445-449 SKILL.md:449-454 SKILL.md:454-462 SKILL.md:462-475 SKILL.md:475-479 SKILL.md:479-489 SKILL.md:489-493 SKILL.md:493-501 SKILL.md:501-511 SKILL.md:511-520 SKILL.md:520-524 SKILL.md:524-530 SKILL.md:530-536 SKILL.md:536-538 SKILL.md:538-555 SKILL.md:555-588 SKILL.md:588-594
Audited by: codex View Audit History →
Share & cite this report
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Copy report link
https://skillstore.io/skills/zhanlincui-project-to-obsidian/audits/4?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/zhanlincui-project-to-obsidian?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/zhanlincui-project-to-obsidian?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/zhanlincui-project-to-obsidian/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/zhanlincui-project-to-obsidian.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Academic citations (APA · BibTeX · CFF)
APA citation
Claude Code. (2026). project-to-obsidian security audit report (audit version 4) [Author version 1.4.0]. Skillstore. https://skillstore.io/skills/zhanlincui-project-to-obsidian/audits/4BibTeX citation
@techreport{claude-code-zhanlincui-project-to-obsidian-2026,
author = {Claude Code},
title = {project-to-obsidian security audit report (audit version 4)},
institution = {Skillstore},
year = {2026},
number = {4},
url = {https://skillstore.io/skills/zhanlincui-project-to-obsidian/audits/4},
note = {Author version 1.4.0}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "project-to-obsidian security audit report (audit version 4)"
version: "1.4.0"
type: report
authors:
- name: "Claude Code"
date-released: "2026-07-08"
url: "https://skillstore.io/skills/zhanlincui-project-to-obsidian/audits/4"
identifiers:
- type: other
value: "skillstore:zhanlincui-project-to-obsidian:audit:4"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: Medium 55
Architecture
100
Maintainability
87
Content
70
Community
87
Spec Compliance
What You Can Build
Onboard to an unfamiliar repository
Create a linked overview of structure, dependencies, entry points, and major modules.
Prepare architecture review notes
Generate architecture summaries, Mermaid diagrams, and module relationships for technical review.
Refresh project documentation
Build or update Obsidian notes for APIs, modules, quickstart steps, and configuration references.
Try These Prompts
Create a Quick Project Overview
/p2o ./my-project --quick and create a local folder. Ask before writing files.
Generate API Documentation
/p2o ./backend --api. Focus on routes, request parameters, response shapes, and linked API notes.
Build an Architecture Vault
/p2o ./platform --arch. Use Mermaid diagrams, module links, and a short decisions summary.
Create Full Obsidian Documentation
Convert ./monorepo into an Obsidian knowledge base. Exclude secrets, generated files, and dependencies. Output to my selected vault path.
Best Practices
- Confirm the project path and output location before scanning or writing.
- Exclude secret, dependency, build, and generated files from documentation.
- Review generated notes before moving them from an AI inbox into shared vault sections.
Avoid
- Do not point the skill at a home directory or broad filesystem root.
- Do not publish generated configuration notes without checking for secrets.
- Do not overwrite existing Obsidian notes without a review step.
Frequently Asked Questions
Does this write directly to Obsidian?
It can write through Obsidian MCP when available. It can also create a local folder or project docs directory after confirmation.
Which languages and frameworks are supported?
It recognizes JavaScript, TypeScript, Python, Go, Rust, Java, and common framework markers. Templates can adapt to other projects.
Does it execute project code?
It is intended to inspect files and structure, not run the application. Users should decline unexpected commands.
How should secrets be handled?
Exclude or redact environment files and secret configuration before generation. Review configuration notes before sharing them.
Can it update existing notes?
The workflow prefers append and patch operations in an AI inbox. Review changes before moving notes into shared vault sections.
Does it work with Claude, Codex, and Claude Code?
The skill declares support for Claude, Codex, and Claude Code. File and vault access depend on the active tool environment.
Developer Details
Author
Claude CodeLicense
MIT
Author version
v1.4.0
Skillstore revision
r1
Repository
https://github.com/ZhanlinCui/Ultimate-Agent-Skills-Collection/tree/main/project-to-obsidianRef
88a205c7f635a966e31156313b590d59007c5caa
Maintenance freshness
7/18/2026
Usage
67 downloads · 214 views
File structure
More from Claude Code
📦
github-release-assistant
83Generate Bilingual GitHub Release READMEs
Release notes and README updates can take time before each GitHub release. This skill generates bilingual release documentation and guides review, commit, and push steps.
Documentation View
📦
obsidian-helper
81Organize Obsidian Notes with AI
Obsidian vaults can become hard to review and update consistently. This skill helps Claude and Codex create daily notes, capture ideas, and summarize recent work.
Productivity View
📦
Process PDFs with Extraction and Form Tools
PDF work often requires separate tools for text, tables, pages, and forms. This skill gives Claude, Codex, and Claude Code guided workflows and helper scripts for PDF tasks.
Office & Reports View
📦
frontend-design
79Build Distinctive Frontend Interfaces
Generic web interfaces can feel unfinished and forgettable. This skill guides Claude, Codex, and Claude Code toward polished frontend work with clear visual direction.
Design & Creative View
📦
brainstorming
79Plan Creative Work Before Building
Teams often start implementation before goals, constraints, and trade-offs are clear. This skill guides Claude, Codex, and Claude Code through structured brainstorming before design work begins.
Productivity View
Related Skills
View all📦
maintain-codex-wiki
80Maintain a Verified Codex Knowledge Wiki
by phelan164
Codex guidance becomes stale, duplicated, and difficult to trace. This skill maintains a review-first wiki with source provenance, explicit knowledge states, safe paths, and deterministic linting.
Documentation View
📦
project-planner
86Plan Software Projects With Structured Documents
by Dwsy
Software projects often fail when requirements, design choices, and tasks are unclear. This skill turns project ideas into structured planning documents for Claude, Codex, and Claude Code workflows.
Documentation View
📦
arch-view
82Visualize Service Architecture
by AstraBit-CPT
Distributed services are hard to understand when metadata is spread across repositories. This skill aggregates catalog metadata and creates diagrams, tables, and summaries for architecture review.
Documentation View
📦
human-docs
81Create Human-Ready AI Documentation
by Brownbull
Detailed AI context files are often too long for quick human review. This skill turns them into summaries, quick starts, and Mermaid visual guides.
Documentation View
📦
skill-creation-guide
81Create Effective AI Skills
by notedit
Teams need repeatable guidance to build useful AI skills without adding unnecessary context. This skill provides a structured process for planning, writing, validating, and packaging skills.
Documentation View
📦
material-component-doc
81Create FlowGram Component Docs
by bytedance
FlowGram material components need consistent docs, runnable Story examples, API tables, and bilingual review steps. This skill gives Claude, Codex, and Claude Code a structured workflow for producing those assets.
Documentation View