Obsidian Ci IntegrationSAFE
Model-agnostic agent-skills platform with a harness-free canonical layer, verified adapters, and the ccpi package manager. Explore at tonsofskills.com.
Overview
Model-agnostic agent-skills platform with a harness-free canonical layer, verified adapters, and the ccpi package manager. Explore at tonsofskills.com.
4f83675ca38aOBSERVED · 2026-10-09Host compatibility
What the documentation claims. We have not run a compatibility test.
| Host | Status | Notes |
|---|---|---|
| claude-code | mentioned |
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-ci-integration description: 'Set up GitHub Actions CI/CD for Obsidian plugin development. Use when automating builds, tests, and releases for your plugin, or setting up continuous integration for Obsidian projects. Trigger with phrases like "obsidian CI", "obsidian github actions", "obsidian automated build", "obsidian CI/CD". ' allowed-tools: Read, Write, Edit, Bash(npm:*) version: 1.13.0 license: MIT author: Jeremy Longshore <[email protected]> tags: - saas - obsidian - testing - ci-cd compatibility: Designed for Claude Code --- # Obsidian CI Integration ## Overview GitHub Actions workflows for Obsidian plugin development: build validation on every push, automated releases when you tag, version-bump scripting, manifest.json validation, and BRAT beta channel support. ## Prerequisites - GitHub repository with an Obsidian plugin - Working local build (`npm run build` produces `main.js`) - `manifest.json` and `versions.json` in repo root - GitHub Actions enabled on the repository ## Instructions ### Step 1: Create Build Workflow ```yaml # .github/workflows/build.yml name: Build Plugin on: push: branches: [main] pull_request: branches: [main] jobs: build: runs-on: ubuntu-latest steps: - uses: actions/checkout@v4 - uses: actions/setup-node@v4 with: node-version: 18 - name: Install dependencies run: npm ci - name: Build plugin run: npm run build - name: Verify build output run: | if [ ! -f main.js ]; then echo "ERROR: main.js not found after build" exit 1 fi echo "main.js size: $(wc -c < main.js) bytes" - name: Validate manifest.json run: | node -e " const m = require('./manifest.json'); const required = ['id', 'name', 'version', 'minAppVersion', 'description', 'author']; const missing = required.filter(f => !m[f]); if (missing.length) { console.error('Missing manifest fields:', missing.join(', ')); process.exit(1); } console.log('manifest.json valid:', m.id, 'v' + m.version); " ``` ### Step 2: Create Release Workflow ```yaml # .github/workflows/release.yml name: Release Plugin on: push: tags: - '*' jobs: release: runs-on: ubuntu-latest permissions: contents: write steps: - uses: actions/checkout@v4 - uses: actions/setup-node@v4 with: node-version: 18 - run: npm ci - run: npm run build - name: Create GitHub Release uses: softprops/action-gh-release@v2 with: files: | main.js manifest.json styles.css draft: false generate_release_notes: true ``` ### Step 3: Create Version Bump Script ```javascript // version-bump.mjs import { readFileSync, writeFileSync } from 'fs'; const targetVersion = process.env.npm_package_version; // Update manifest.json const manifest = JSON.parse(readFileSync('manifest.json', 'utf8')); const { minAppVersion } = manifest; manifest.version = targetVersion; writeFileSync('manifest.json', JSON.stringify(manifest, null, '\t')); // Update versions.json — maps plugin version to minimum Obsidian version const versions = JSON.parse(readFileSync('versions.json', 'utf8')); versions[targetVersion] = minAppVersion; writeFileSync('versions.json', JSON.stringify(versions, null, '\t')); console.log(`Bumped to ${targetVersion} (minAppVersion: ${minAppVersion})`); ``` ### Step 4: Wire Version Bump into package.json ```json { "scripts": { "build": "node esbuild.config.mjs", "dev": "node esbuild.config.mjs --watch", "version": "node version-bump.mjs && git add manifest.json versions.json" } } ``` Now `npm version patch` (or minor/major) runs the bump script automatically. ### Step 5: Add Manifest Validation Workflow ```yaml # .github/workflows/validate.yml name: Validate Plugin on: [push, pull_request] jobs: validate: runs-on: ubuntu-latest steps: - uses: actions/checkout@v4 - name: Check manifest/versions consistency run: | node -e " const manifest = require('./manifest.json'); const versions = require('./versions.json'); const pkg = require('./package.json'); let fail = false; if (manifest.version !== pkg.version) { console.error('Version mismatch: manifest=' + manifest.version + ' package=' + pkg.version); fail = true; } if (!versions[manifest.version]) { console.error('versions.json missing entry for ' + manifest.version); fail = true; } if (fail) process.exit(1); console.log('All versions consistent: ' + manifest.version); " ``` ### Step 6: BRAT Beta Support Add a `beta-manifest.json` for [BRAT](https://github.com/TfTHacker/obsidian42-brat) beta testers: ```json { "id": "your-plugin-id", "name": "Your Plugin (Beta)", "version": "1.2.0-beta.1", "minAppVersion": "1.5.0", "description": "Beta channel — install via BRAT", "author": "Your Name" } ``` Beta users install via BRAT by entering your GitHub repo URL. BRAT fetches the latest release (including pre-releases) automatically — no submission to the community repo needed. ## Output - `.github/workflows/build.yml` — validates build on every push/PR - `.github/workflows/release.yml` — creates GitHub release with `main.js`, `manifest.json`, `styles.css` on tag push - `.github/workflows/validate.yml` — checks version consistency across manifest, package.json, and versions.json - `version-bump.mjs` — keeps manifest.json and versions.json in sync with package.json version - Optional `beta-manifest.json` for BRAT beta channel ## Error Handling | Error | Cause | Solution | |-
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.
| Layer | What it checks | Result |
|---|---|---|
| L0 | Provenance & inventory | PASS |
| L1 | Static analysis of the code | PASS |
| L2 | Instruction surface (what it tells the agent) | PASS |
| L3 | Class-specific surface | PASS |
| L4 | Behavioural (sandbox) | SKIPPED |
What the source does
- Filesystem
- none-observed
- Network
- none-observed
- Shell
- none-observed
- Dependencies
- pinned
- Secrets in source
- none-found
Findings (0)
No findings outside the package's declared scope.
Gates applied: no_behavioural_pass.
4f83675ca38afull audit observations/trust-audit/skill/jeremylongshore__obsidian-ci-integration.json · Report an issue / request a re-scanAudit history
Every audit this skill has had.
| Date | Source | Verdict | Grade | Score | Change |
|---|---|---|---|---|---|
| 2026-10-09 | 4f83675ca38a | SAFE | B | 89 | first audit |
Questions
What does the Obsidian Ci Integration skill do?
Model-agnostic agent-skills platform with a harness-free canonical layer, verified adapters, and the ccpi package manager. Explore at tonsofskills.com.
Is Obsidian Ci Integration 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 Ci Integration access on my machine?
The audit observed no filesystem, network or shell use at all in its source.
Which assistants does Obsidian Ci Integration work with?
Its documentation mentions claude-code. That is what the text claims, not a compatibility test we ran.
How current is this page?
The grade is for one exact copy of the source (4f83675ca38a), read on 2026-10-09. The repository is watched, and a new audit runs when it changes — this is the first audit.