Profile My skills Saved My plugins Edit profile Submit a skill

← all publishers

danblaare

@danblaare source repo

3 published skills

  1. ▌
    Skill Management · danblaare bundle
    General manager for the user's Claude skills (local, claude.ai and plugins). Use ONLY when the user explicitly asks to manage their skills: run a skills check or look for updates; install, create, edit, disable, enable, uninstall or roll back a skill; check skill health, overlaps, conflicts, context cost or triggering; review how skills were used and improve them from feedback; discover new skills; export or sync skills; see where a skill works (Claude chat or Claude Code), package a skill for claude.ai or edit a claude.ai skill; or show the skills dashboard or log (e.g. 'run my skills check', 'manage my skills', 'install this skill', 'which skills overlap?'). Do not trigger automatically during other tasks.
    0 installs
  2. ▌
    Skilltotal Preinstall · danblaare bundle
    Mandatory security gate that scans a component with SkillTotal BEFORE installing it. ALWAYS use this whenever the user asks to install, add, set up, enable, clone, download, or upgrade anything — npm/pnpm/yarn/bun packages, pip/uv/poetry/PyPI packages, MCP servers, Claude Code skills or plugins, agents, GitHub repos, VS Code extensions, CLI tools, or archives. Triggers on phrases like "install X", "add the X package", "npm i", "pip install", "set up the X MCP server", "add this skill/plugin", "clone and run", "upgrade X to vN". Run the scan first; never run the install command until the scan is reviewed. The scan report goes to the Obsidian skills log note, not to the chat.
    0 installs
  3. ▌
    Super Coding · danblaare bundle
    Complete software-building workflow that turns Claude into a disciplined senior engineer for a non-technical owner: define, plan, build, debug, review, verify, ship. Merges superpowers, agent-skills, karpathy-skills and gstack into one process and calls the user's existing skills instead of duplicating them. Use AUTOMATICALLY (without being asked) whenever a task involves creating, changing, fixing, testing, reviewing, deploying or launching software: apps, websites, landing pages, APIs, scripts, automations, bots, browser extensions, games or any digital product; a product or feature idea that will be built; bugs, errors, stack traces, failing tests or 'it doesn't work'; code review, refactoring or cleanup; setting up projects, repos, CI/CD, hosting or domains; shipping, releasing or monitoring. Not for skill management, pure data analysis, office documents, or questions that involve no code.
    0 installs