Profile My skills Saved Collections Edit profile Submit a skill

← all publishers

brianlovin

@brianlovin source repo

6 published skills

  1. ▌
    Notion Skills Usage · brianlovin
    Use the notion-skills CLI to manage AI agent skills from one or more Notion-backed workspace stores. Invoke when the user wants to install a skill from their team's store, publish a local skill they authored, sync installed skills, generate a new skill via their coding agent, manage Notion sources (one database per source), or inspect the state of installed/available/outdated/draft skills. Triggers on commands like install, publish, sync, gen, list, uninstall, unpublish, doctor, init, upgrade, open, import, source.
    0 installs
  2. ▌
    Reclaude · brianlovin
    Refactor CLAUDE.md files to follow progressive disclosure principles. Use when CLAUDE.md is too long or disorganized.
    1 install
  3. ▌
    Workflow · brianlovin
    Workflow orchestration for complex coding tasks. Use for ANY non-trivial task (3+ steps or architectural decisions) to enforce planning, subagent strategy, self-improvement, verification, elegance, and autonomous bug fixing. Triggers: multi-step implementation, bug fixes, refactoring, architectural changes, or any task requiring structured execution.
    1 install
  4. ▌
    Playwriter · brianlovin bundle
    Control the user's currently open Chrome tab through the Playwriter CLI (no new browser launch). Use when you need to inspect live UI state, run scripted browser actions, capture console output, or reproduce frontend issues directly in the user's tab.
    1 install
  5. ▌
    Fix Sentry Issues · brianlovin
    Use Sentry MCP to discover, triage, and fix production issues with root-cause analysis. Use when asked to fix Sentry issues, triage production errors, investigate error spikes, or clean up Sentry noise. Requires Sentry MCP server. Triggers on "fix sentry", "triage errors", "production bugs", "sentry issues".
    1 install
  6. ▌
    Chrome Webstore Release Blueprint · brianlovin
    Guide a user end-to-end through setting up Chrome Web Store API release automation in any repository. Use when asked to walk someone through OAuth/CWS credential setup, refresh token creation, local/CI secret setup, version-based publish automation, and submission status checks.
    1 install