Hig Project Context
raintree-technology/hig-doctor
Create or update a shared Apple design context document that other HIG skills use to tailor guidance.
Validate Personal Assistant runtime and UI changes in the repo-local Obsidian test vault.
Install Obsidian Test Vault Smoke
$ npx skills add edonyzpc/personal-assistant --skill obsidian-test-vault-smoke -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install edonyzpc/personal-assistant obsidian-test-vault-smoke --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/edonyzpc/personal-assistant.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/obsidian-test-vault-smoke .claude/skills/obsidian-test-vault-smoke && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "obsidian-test-vault-smoke" agent skill from https://github.com/edonyzpc/personal-assistant/tree/master/.agents/skills/obsidian-test-vault-smoke into .claude/skills/obsidian-test-vault-smoke/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "obsidian-test-vault-smoke", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/edonyzpc/personal-assistant/tree/master/.agents/skills/obsidian-test-vault-smokeType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add edonyzpc/personal-assistant --skill obsidian-test-vault-smoke -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install edonyzpc/personal-assistant obsidian-test-vault-smoke --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/edonyzpc/personal-assistant.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/obsidian-test-vault-smoke .agents/skills/obsidian-test-vault-smoke && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "obsidian-test-vault-smoke" agent skill from https://github.com/edonyzpc/personal-assistant/tree/master/.agents/skills/obsidian-test-vault-smoke into .agents/skills/obsidian-test-vault-smoke/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "obsidian-test-vault-smoke", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add edonyzpc/personal-assistant --skill obsidian-test-vault-smoke -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install edonyzpc/personal-assistant obsidian-test-vault-smoke --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/edonyzpc/personal-assistant.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/obsidian-test-vault-smoke .cursor/skills/obsidian-test-vault-smoke && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "obsidian-test-vault-smoke" agent skill from https://github.com/edonyzpc/personal-assistant/tree/master/.agents/skills/obsidian-test-vault-smoke into .cursor/skills/obsidian-test-vault-smoke/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "obsidian-test-vault-smoke", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/edonyzpc/personal-assistant.git --path .agents/skills/obsidian-test-vault-smoke--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add edonyzpc/personal-assistant --skill obsidian-test-vault-smoke -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install edonyzpc/personal-assistant obsidian-test-vault-smoke --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/edonyzpc/personal-assistant.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/obsidian-test-vault-smoke .gemini/skills/obsidian-test-vault-smoke && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "obsidian-test-vault-smoke" agent skill from https://github.com/edonyzpc/personal-assistant/tree/master/.agents/skills/obsidian-test-vault-smoke into .gemini/skills/obsidian-test-vault-smoke/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "obsidian-test-vault-smoke", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install edonyzpc/personal-assistant obsidian-test-vault-smokeInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add edonyzpc/personal-assistant --skill obsidian-test-vault-smoke -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/edonyzpc/personal-assistant.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/obsidian-test-vault-smoke .github/skills/obsidian-test-vault-smoke && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "obsidian-test-vault-smoke" agent skill from https://github.com/edonyzpc/personal-assistant/tree/master/.agents/skills/obsidian-test-vault-smoke into .github/skills/obsidian-test-vault-smoke/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "obsidian-test-vault-smoke", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add edonyzpc/personal-assistant --skill obsidian-test-vault-smoke -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install edonyzpc/personal-assistant obsidian-test-vault-smoke --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/edonyzpc/personal-assistant.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/obsidian-test-vault-smoke .opencode/skills/obsidian-test-vault-smoke && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "obsidian-test-vault-smoke" agent skill from https://github.com/edonyzpc/personal-assistant/tree/master/.agents/skills/obsidian-test-vault-smoke into .opencode/skills/obsidian-test-vault-smoke/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "obsidian-test-vault-smoke", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
obsidian-test-vault-smoke- GitHub stars
- 147
- Token cost
- ~2.2k tokens
- SKILL.md length
- 955 words
- Files
- 5 (incl. references)
- Skills in repo
- 19
- Repo updated
- First seen
- Licence
- AGPL-3.0
At a glance
Validate Personal Assistant runtime and UI changes in the repo-local Obsidian test vault.
- Works in 5 steps: Classify the latest runtime delta as… → Freeze the observable target. For… → Map changed surfaces to the minimum… → …
- Desktop interaction
- SKILL.md covers Core Rules, Scope Freeze And Evidence Reuse, Validation Gate and Smoke Tiers, plus 4 more sections
- Calls make and git
What it does
Obsidian Test Vault Smoke is an agent skill from edonyzpc/personal-assistant. Validate Personal Assistant runtime and UI changes in the repo-local Obsidian test vault. Use for app smoke, desktop interaction, and general mobile validation with Obsidian CLI mobile simulator. Real-device iPhone validation uses obsidian-ios-real-device-smoke only for an explicit user request or a verified iOS-specific capability.
Its SKILL.md is about 2.2k tokens, which your agent loads only when the skill is triggered. The skill folder holds 6 other files, including reference files (for example `agents/openai.yaml`, `references/cli-runtime.md` and `references/pagelet-smoke.md`).
It sits in Mobile. It works with Obsidian and iOS. The repository describes itself as: A plugin that harnesses AI agents and streamlining techniques to help you automatically manage Obsidian. The licence is AGPL-3.0.
When your agent uses it
- Desktop interaction
- General mobile validation with Obsidian CLI mobile simulator
Example prompts
- “/obsidian-test-vault-smoke”
Workflow steps
5 steps, taken from the first numbered list in SKILL.md.
- Classify the latest runtime delta as code-only, runtime, visual/layout,
- Freeze the observable target. For screenshot-led UI work, state direction,
- Map changed surfaces to the minimum evidence. Mark unaffected surfaces
- Reuse automated checks under AGENTS.md Validation Planning And Reuse,
- Freeze runtime files before make deploy. If they change afterward, rerun
What it can do on your machine
Read from SKILL.md and the folder at commit 5c22410. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
makegit
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Obsidian Test Vault Smoke loads about 2.2k tokens when it runs, and up to ~6.5k if it reads all its reference files. Until then it costs about 90 tokens; SKILL.md has 955 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from edonyzpc/personal-assistant at commit 5c22410, republished under its AGPL-3.0 licence (© edonyzpc). 955 words, ~2,240 tokens.
Download SKILL.mdSave it as
.claude/skills/obsidian-test-vault-smoke/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.- name
- obsidian-test-vault-smoke
- description
- Validate Personal Assistant runtime and UI changes in the repo-local Obsidian test vault. Use for app smoke, desktop interaction, and general mobile validation with Obsidian CLI mobile simulator. Real-device iPhone validation uses obsidian-ios-real-device-smoke only for an explicit user request or a verified iOS-specific capability.
Obsidian Test Vault Smoke
Core Rules
- Do not claim Obsidian validation without deploying the current build to
test/and observing the affected behavior in the running app. - Treat Jest, lint, type-check, build, and source scans as implementation validation, not app smoke.
- Require visible-window interaction for UI/UX PASS; CLI, DOM, and screenshots support the finding but do not replace real interaction.
- Use
obsidian vault=test <command>for every Obsidian CLI call.vault=testmust precede the command. - Choose the lightest tier that covers the changed surface.
- Follow the mobile environment rule in
AGENTS.mdbefore choosing a smoke skill. Use this skill for general mobile validation with CLI mobile simulator; a tool failure does not create a real-device requirement.
Scope Freeze And Evidence Reuse
Before an expensive gate or app interaction:
- Classify the latest runtime delta as
code-only,runtime,visual/layout,interaction/state, orrelease/broad. - Freeze the observable target. For screenshot-led UI work, state direction, order, spacing, viewport, and interaction expectations in testable terms. Ask one product question before deployment if the target is ambiguous.
- Map changed surfaces to the minimum evidence. Mark unaffected surfaces
SKIP; do not run full Pagelet, provider, or cross-surface flows for a geometry-only change. - Reuse automated checks under
AGENTS.mdValidation Planning And Reuse, verifying relevant source/tests/fixtures/config and build inputs/results. Reuse observed app smoke when its runtime/assets, target vault state, loaded build, and acceptance conditions are verifiably unchanged. A new turn alone does not invalidate it. Changed or unknown relevant state requires only the affected proof; docs/evidence-only edits do not invalidate runtime smoke unless they change its acceptance conditions. - Freeze runtime files before
make deploy. If they change afterward, rerun only the affected validation gate and app proof.
Stop when every frozen acceptance check has current deployed evidence. Do not add adjacent gestures, orientations, provider calls, or unrelated surfaces solely to strengthen an already sufficient proof.
Validation Gate
Satisfy the complete Local Validation Gate from repo-root AGENTS.md
before app smoke. Reuse checks covered by the selected enclosing gate with
verified inputs/results: the production build covers type-checking and full
Jest covers the focused suites it includes. Supplement remaining checks,
including the runtime <style> / innerHTML / outerHTML source scan.
For failures, follow AGENTS.md Test Failure Diagnosis; an unavailable
app/device remains a validation gap, never a PASS.
Treat the source-scan rg exit code 1 with no output as PASS. Inspect every match manually. make deploy and the hosted community scan do not replace this local source scan.
Smoke Tiers
| Tier | Use when | Required checks |
|---|---|---|
quick | Narrow code-only or test-only change | Complete Local Validation Gate with focused suites; stop before app smoke only when no runtime/user path changed |
app-runtime | Runtime, command, packaging, Pagelet shell, Chat/Preview/Stats mount, Memory readiness | Local Validation Gate, make deploy, plugin reload, affected CLI/DOM probes, fresh console/error capture |
full-ui | Visible UI, CSS/layout/copy, Pagelet workflow, settings, keyboard/focus, mobile emulation | app-runtime plus real Obsidian interaction, screenshots, UX notes, and provider/write-path checks when applicable |
release-gate | Release, broad refactor, shared infrastructure | Local Validation Gate, make deploy, broad runtime matrix, required UI surfaces, and release evidence reconciliation |
make deploy already runs lint, a production build, full Jest, and asset
deployment. If those checks already passed for the current changes, use
make deploy-current to verify and copy the current build without repeating
them. Reuse conditions and test groups live in AGENTS.md Local Deployment;
build identity alone does not prove tests passed.
Show full SKILL.md (399 more words)Show less
Workflow
- Inspect
git status --short, relevant diffs, and affected surfaces. - Freeze the observable target and classify the runtime delta. Before changing app modes or reloading for smoke, record the actual CLI debug and mobile-emulation states and the commands needed to restore them; see CLI runtime smoke.
- Select the deployment path below and complete or reuse its checks together
with the remaining Local Validation Gate checks from
AGENTS.md. - Select the smoke tier.
- For app smoke, deploy with
make deploybelow, or replace only that command withmake deploy-currentwhen the reuse conditions above hold, then reload:
make deploy
obsidian vault=test vault info=path
obsidian vault=test plugin:reload id=personal-assistant
obsidian vault=test plugin id=personal-assistant- For visible changes, perform the cheapest visual target check immediately after reload. Stop on a direction, order, clipping, or viewport mismatch before deeper interactions.
- Read only the references required by the changed surface:
- For any
app-runtime,full-ui, orrelease-gaterun, read CLI runtime smoke. - For visible UI/UX work, read UI/UX interaction smoke.
- For Pagelet work, read both CLI runtime smoke and Pagelet smoke.
- For any
- For historical fixtures, regression expectations, and prior evidence, consult the current Pagelet smoke checklist. Treat its verification log as provenance, not current-run evidence.
- Record concrete
PASS,FAIL,BLOCKED, orSKIPoutcomes. - Restore the recorded debug/mobile states after success, failure, or
interruption;
offis correct only when that was the initial state. Restore mobile first if it triggers a reload, then restore and verify debug. Report an unknown initial state or failed restoration without claiming cleanup PASS.
Safety Boundaries
- Limit provider-backed checks to repo-local test-vault fixtures unless the user approves broader data. Report provider/model, note paths, and prompts sent.
- If a provider, browser, CLI, or GUI tool blocks the action, do not bypass the block; report
BLOCKEDand residual risk. - Stop before deleting or rewriting test-vault data that may be user-authored.
- Stop before publishing, pushing, creating releases, or mutating non-test external systems unless the user authorized that action.
- Keep hosted Obsidian Community scans distinct from the local source scan. A hosted scan submits a ref to an external service and is never an automatic part of this skill.
- During
release-gate, invokeobsidian-community-checkonly when the user explicitly requested the hosted scan or the activestable-releaseworkflow explicitly authorized it. Otherwise report it as not run.
Output
Validation:
- Runtime delta: `<code-only/runtime/visual-layout/interaction-state/release-broad>`
- Frozen target: `<observable acceptance checks>`
- Reused evidence: `<same-state evidence or none>`
- PASS: `<check>` - `<observed result>`
- FAIL: `<path>` - `<regression or product gap>`
- BLOCKED: `<path>` - `<external blocker and residual risk>`
- SKIP: `<path>` - `<why it was outside this tier>`
- Stop point: `<why the selected tier is complete>`
CLI runtime smoke:
- Vault: `test/`
- Tier: `<quick/app-runtime/full-ui/release-gate>`
- Deployment/reload: `<result>`
- Obsidian: `<version>`
- Target: `<note/view/command>`
- Provider/model/prompt: `<if used>`
- Artifact: `<DOM output, console excerpt, runtime file>`
UI/UX smoke:
- Visible path: `<entry and interaction>`
- Observed UX: `<layout, copy, feedback, accessibility>`
- Screenshot: `<path if captured>`
- UX findings: `<UX-P0/UX-P1/UX-P2 or none>`
Cleanup:
- Initial debug/mobile states: `<observed states or unknown>`
- Restored debug/mobile states: `<observed states; PASS/FAIL/BLOCKED>`
Hosted community scan:
- Authorized and run / not authorized and not run / BLOCKEDRelated Skills
- Use
personal-assistant-reviewfor code-level review. - Use
obsidian-ios-real-device-smokeafter local app smoke for real-device iOS validation. - Use
obsidian-community-checkonly for an authorized hosted community scan.
© edonyzpc, AGPL-3.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 4 other files (references) in .agents/skills/obsidian-test-vault-smoke of edonyzpc/personal-assistant.
- SKILL.md
- agents/openai.yaml
- references/cli-runtime.md
- references/pagelet-smoke.md
- references/ui-ux-smoke.md
Open the folder on GitHubat commit 5c22410
Compare with similar skills
Obsidian Test Vault Smoke next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Obsidian Test Vault Smoke this skilledonyzpc/personal-assistant | 147 | — | ~2.2k | Automated safety check: Pass | AGPL-3.0 | |
| Hig Project Contextraintree-technology/hig-doctor | 144 | 5 repos | ~1.2k | Automated safety check: Pass | MIT | |
| Store Submitzhitongblog/solomd | 1.2k | — | ~1.7k | Automated safety check: Notes | MIT | |
| Hig Components Contentraintree-technology/hig-doctor | 144 | 5 repos | ~1.3k | Automated safety check: Pass | MIT | |
| Discover iOS KeysPoomSmart/MGKeys | 238 | — | ~1.4k | Automated safety check: Pass | MIT | |
| Argent Metro Debuggerbbplayer-app/BBPlayer | 1.2k | — | ~3.4k | Automated safety check: Pass | MIT |
Similar skills
Store Submit
zhitongblog/solomd
Publish a SoloMD release to the stores that have no usable submission API — Google Play Console and Microsoft Partner Center — by driving them through the local Unzoo Browser REST API.
Hig Components Content
raintree-technology/hig-doctor
Apple Human Interface Guidelines for content display components.
Discover iOS Keys
PoomSmart/MGKeys
Discover and map new MobileGestalt keys for a new iOS version in MGKeys.
Argent Metro Debugger
bbplayer-app/BBPlayer
Debug a JS runtime via CDP using argent debugger tools. An agent skill from bbplayer-app/BBPlayer.
Solomd
zhitongblog/solomd
Read, search, edit, and version-control any folder of Markdown notes via the SoloMD MCP server.
More from edonyzpc/personal-assistant
All 19 skills in this repoObsidian Dataview
edonyzpc/personal-assistant
Dataview plugin query syntax, inline expressions, DataviewJS API, and common vault analysis patterns.
Obsidian Community Check
edonyzpc/personal-assistant
Trigger and inspect Obsidian Community checks for personal-assistant.
Pa Brat Beta Release
edonyzpc/personal-assistant
Manage Personal Assistant BRAT beta prerelease workflow. An agent skill from edonyzpc/personal-assistant.
Pa Docs Lifecycle Manager
edonyzpc/personal-assistant
Maintain PA task records and documentation lifecycle. An agent skill from edonyzpc/personal-assistant.
Personal Assistant Review
edonyzpc/personal-assistant
Review uncommitted or PR diffs in the personal-assistant Obsidian plugin with project-specific risk lanes, second-layer future-risk checks, severity discipline, subagent review routing, and…
Personal Assistant Review Followup
edonyzpc/personal-assistant
Triage, confirm, fix, and validate code review findings in the personal-assistant repository after an agent team or human review.
Related
Categories
Questions about Obsidian Test Vault Smoke
What does Obsidian Test Vault Smoke do?
Validate Personal Assistant runtime and UI changes in the repo-local Obsidian test vault. Obsidian Test Vault Smoke is an agent skill from edonyzpc/personal-assistant. Validate Personal Assistant runtime and UI changes in the repo-local Obsidian test vault.
When should I use Obsidian Test Vault Smoke?
Obsidian Test Vault Smoke fits situations like: desktop interaction; general mobile validation with Obsidian CLI mobile simulator.
How do I install Obsidian Test Vault Smoke in Claude Code?
Run `npx skills add edonyzpc/personal-assistant --skill obsidian-test-vault-smoke -a claude-code`. Or copy the skill folder (.agents/skills/obsidian-test-vault-smoke in edonyzpc/personal-assistant) into .claude/skills/obsidian-test-vault-smoke in your project. Claude Code loads it when a task matches its description.
How do I install Obsidian Test Vault Smoke in Codex?
Run `npx skills add edonyzpc/personal-assistant --skill obsidian-test-vault-smoke -a codex`. Or copy the skill folder (.agents/skills/obsidian-test-vault-smoke in edonyzpc/personal-assistant) into .agents/skills/obsidian-test-vault-smoke in your project. Codex loads it when a task matches its description.
Can I use Obsidian Test Vault Smoke in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add edonyzpc/personal-assistant --skill obsidian-test-vault-smoke -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/obsidian-test-vault-smoke, .gemini/skills/obsidian-test-vault-smoke, .github/skills/obsidian-test-vault-smoke and .opencode/skills/obsidian-test-vault-smoke in your project.
What does Obsidian Test Vault Smoke need to run?
Going by SKILL.md and its folder, Obsidian Test Vault Smoke needs the command-line tools its instructions call (make and git).
Does Obsidian Test Vault Smoke access the network?
SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Obsidian Test Vault Smoke safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Obsidian Test Vault Smoke use?
Obsidian Test Vault Smoke is published under the AGPL-3.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Obsidian Test Vault Smoke use?
About 2.2k tokens (SKILL.md is roughly 9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 4.2k tokens, read only when the agent opens those files.
What are the alternatives to Obsidian Test Vault Smoke?
Skills that share tags, products or a category with Obsidian Test Vault Smoke: Hig Project Context (raintree-technology/hig-doctor, 144 stars), Store Submit (zhitongblog/solomd, 1.2k stars), Hig Components Content (raintree-technology/hig-doctor, 144 stars) and Discover iOS Keys (PoomSmart/MGKeys, 238 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Obsidian Test Vault Smoke?
edonyzpc (a GitHub user) maintains it in edonyzpc/personal-assistant, which has 147 GitHub stars. The repository holds 19 skills in this directory. The repository was last updated on October 10, 2026.
Source: edonyzpc/personal-assistant on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.