skills/log-skill/SKILL.md
Log a new or updated Claude Code skill to the Skills Install Log in the Obsidian vault. Use when a skill is created, significantly modified, or when the PostToolUse hook fires after a SKILL.md write. Asks for YouTube source link if the skill was inspired by a video.
npx skillsauth add asets-gobizit/claude-skills log-skillInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Append a row to Skills Install Log.md in the Obsidian vault every time a skill is created or significantly updated.
/log-skillC:\Users\dansk\.claude\skills\*\SKILL.md (the hook injects a system reminder that points here)/log-skill
/log-skill <skill-name> [new|update] "<description>"
Examples:
/log-skill — Claude detects the most recent skill change from git status and logs it/log-skill comic-book new "KDP print-ready PDF pipeline" — explicit entryDetect the skill change
git status and git diff in C:\Users\dansk\.claude to find recent skills/*/SKILL.md changesnew (folder didn't exist before) or update (folder existed)Ask for YouTube source — MANDATORY
— in the YouTube columnBuild the row
| YYYY-MM-DD | skill-name | new/update | Description | YouTube URL or — |description field, git commit message, or conversation context)Append to the log
C:\Users\dansk\Claude\Obsidian@Claude\Skills Install Log.mdConfirm to user
[[Skills Install Log]] (use the structure — do not invent history).skills/ + Skills Install Log.md together so they stay in sync."data-ai
Automated backup skill for PKA + Obsidian + Claude memory. Snapshots pka.db (via SQLite .backup so WAL is handled safely), the Obsidian vault, Claude memory files, agent profiles, and the help-content Excel into a single timestamped zip in Zoho WorkDrive. Daily/weekly/monthly retention rotation built in. USE WHEN Danny says "backup", "run backup", "snapshot pka", or to recover from a snapshot.
testing
Run any question, idea, or decision through a council of 5 AI advisors who independently analyze it, peer-review each other anonymously, and synthesize a final verdict. Based on Karpathy's LLM Council methodology, packaged as the stress-test skill. MANDATORY TRIGGERS: 'stress-test this', 'stress test this', 'pressure-test this', 'pressure test this', 'war room this', 'council this', 'run the council', 'debate this'. STRONG TRIGGERS (use when combined with a real decision or tradeoff): 'should I X or Y', 'which option', 'what would you do', 'is this the right move', 'validate this', 'get multiple perspectives', 'I can't decide', 'I'm torn between'. Do NOT trigger on simple yes/no questions, factual lookups, or casual 'should I' without a meaningful tradeoff (e.g. 'should I use markdown' is not a stress-test question). DO trigger when the user presents a genuine decision with stakes, multiple options, and context that suggests they want it pressure-tested from multiple angles.
content-media
Weekly scan of Obsidian vault for empty/low-content notes. Moves them to zToBeDeleted/ for user review. Use when the user says "tidy obsidian", "clean obsidian", "obsidian cleanup", or on scheduled weekly run.
development
Design-first website builder. Accepts a Claude Design export (HTML or screenshot) as a visual blueprint, collects business inputs, calls Claude API to generate a design-matched index.html, and publishes to GitHub Pages. Falls back to vibe-based generation if no design is provided. Use when the user says "make-website-design", "design website", "build from design", or provides a Claude Design export for website generation.