Source profileQuality 92/100

WYRE-AI/msp-claude-plugins/msp-claude-plugins/blumira/blumira/skills/msp/SKILL.md

Blumira MSP

Blumira's MSP path group (`/msp/*`): managed-account enumeration, cross-account and per-account finding queries, per-account device, agent-key and user management, and how MSP paths differ from org paths.

Source repository stars
42
Declared platforms
0
Static risk flags
0
Last source update
2026-08-28
Source checked
2026-08-28

Decision brief

What it does: where it fits

Blumira's MSP path group (`/msp/*`): managed-account enumeration, cross-account and per-account finding queries, per-account device, agent-key and user management, and how MSP paths differ from org paths.

Best for

    Not for

    • Tasks that require unconfirmed production actions or broad system permissions.
    • Environments where the pinned source and install steps cannot be inspected.

    Compatibility matrix

    Platform support, with evidence labels

    PlatformStatusEvidenceWhat to check
    CodexNot declaredNo explicit evidencePortability before use
    Claude CodeNot declaredNo explicit evidencePortability before use
    CursorNot declaredNo explicit evidencePortability before use
    Gemini CLINot declaredNo explicit evidencePortability before use
    Open the compatibility checker

    Installation

    Inspect first. Install second.

    The source command is displayed only when detected. A safe inspection prompt is always available so your agent can explain every action before execution.

    Source-detected install commandSource
    npx skills add https://github.com/WYRE-AI/msp-claude-plugins --skill "msp-claude-plugins/blumira/blumira/skills/msp"
    Safe inspection promptEditorial

    Inspect the Agent Skill "Blumira MSP" from https://github.com/WYRE-AI/msp-claude-plugins/blob/5005f73ba2f52cd299f58aa6bb79f4e70ae87103/msp-claude-plugins/blumira/blumira/skills/msp/SKILL.md at commit 5005f73ba2f52cd299f58aa6bb79f4e70ae87103. List every install step, command, network request, credential, file read/write, external action, and rollback step. Explain whether it fits my task. Do not install or execute anything until I approve.

    Workflow

    What the source asks the agent to do

    1. 01

      Anti-triggers

      Working inside a single organization with org-level credentials —

      Working inside a single organization with org-level credentials —"MSP" meaning the multi-tenant view of another vendor — anResolution-type semantics — the codes behave identically at MSP
    2. 02

      Key Concepts

      MSP tools require an accountid parameter to target a specific client account. Use blumiramspaccountslist to enumerate available accounts.

      MSP tools require an accountid parameter to target a specific client account. Use blumiramspaccountslist to enumerate available accounts.
    3. 03

      MSP vs Org Paths

      Review the “MSP vs Org Paths” section in the pinned source before continuing.

      Review and apply the “MSP vs Org Paths” source section.
    4. 04

      Account Context

      MSP tools require an accountid parameter to target a specific client account. Use blumiramspaccountslist to enumerate available accounts.

      MSP tools require an accountid parameter to target a specific client account. Use blumiramspaccountslist to enumerate available accounts.
    5. 05

      API Patterns

      Returns findings from ALL managed accounts with account context included.

      Returns findings from ALL managed accounts with account context included.

    Permission review

    Static risk signals and limitations

    No configured static risk pattern was detected

    This is not proof of safety. Runtime behavior, indirect dependencies, and hidden external systems are outside the static scan.

    Evidence record

    Why each signal appears

    EvidenceSourceComputedTestedEditorial
    SignalValueEvidence typeMeaning
    Quality score92/100ComputedDocumentation, specificity, maintenance, and trust rules
    Repository stars42SourceRepository attention, not individual Skill quality
    Compatibility0 platformsSourceDeclared in the catalog source record
    Usage guideautomated source guideEditorialGenerated or reviewed according to the visible evidence level

    Pinned source

    Provenance and original SKILL.md

    Repository
    WYRE-AI/msp-claude-plugins
    Skill path
    msp-claude-plugins/blumira/blumira/skills/msp/SKILL.md
    Commit
    5005f73ba2f52cd299f58aa6bb79f4e70ae87103
    License
    Apache-2.0
    Collected
    2026-08-28
    Default branch
    main
    View the original SKILL.md

    Blumira MSP Operations

    Overview

    Blumira's MSP path group (/msp/*) enables managed service providers to operate across multiple client organizations from a single set of credentials. This skill covers account management, cross-account queries, and per-account operations.

    Anti-triggers

    • Working inside a single organization with org-level credentials — the /msp/* tools need an MSP-scoped JWT and an account_id on every call. Use blumira-findings, blumira-agents, or blumira-users.
    • "MSP" meaning the multi-tenant view of another vendor — an M365-tenant portfolio is cipp-tenants or inforcer-tenant-management; a CompassOne partner sweep is blackpoint-multi-tenant-operations.
    • Resolution-type semantics — the codes behave identically at MSP and org level and are documented once, in blumira-resolutions.

    Key Concepts

    MSP vs Org Paths

    FeatureOrg Path (/org/*)MSP Path (/msp/*)
    ScopeSingle organizationMultiple managed accounts
    FindingsOwn findings onlyAll accounts or per-account
    DevicesOwn devices onlyPer-account device lists
    UsersOwn users onlyPer-account user lists
    AuthOrg-level JWTMSP-level JWT

    Account Context

    MSP tools require an account_id parameter to target a specific client account. Use blumira_msp_accounts_list to enumerate available accounts.

    API Patterns

    List Managed Accounts

    blumira_msp_accounts_list
      page_size=100
    

    Get Account Details

    blumira_msp_accounts_get
      account_id=<UUID>
    

    Cross-Account Findings

    blumira_msp_findings_all
      status.eq=10
      severity.in=HIGH,CRITICAL
      order_by=-created
    

    Returns findings from ALL managed accounts with account context included.

    Per-Account Findings

    blumira_msp_findings_list
      account_id=<UUID>
      status.eq=10
    

    Get a Finding in Account Context

    blumira_msp_findings_get
      account_id=<UUID>
      finding_id=<UUID>
    

    Resolve an Account's Finding

    blumira_msp_findings_resolve
      account_id=<UUID>
      finding_id=<UUID>
      resolution_type=10
      notes="Confirmed and remediated."
    

    Assign a Finding

    blumira_msp_findings_assign
      account_id=<UUID>
      finding_id=<UUID>
      user_id=<UUID>
    

    Account Finding Comments

    blumira_msp_findings_comments_list
      account_id=<UUID>
      finding_id=<UUID>
    
    blumira_msp_findings_comments_add
      account_id=<UUID>
      finding_id=<UUID>
      comment="Investigation notes..."
    

    Per-Account Devices

    blumira_msp_devices_list
      account_id=<UUID>
      page_size=50
    
    blumira_msp_devices_get
      account_id=<UUID>
      device_id=<UUID>
    

    Per-Account Agent Keys

    blumira_msp_keys_list
      account_id=<UUID>
    
    blumira_msp_keys_get
      account_id=<UUID>
      key_id=<UUID>
    

    Per-Account Users

    blumira_msp_users_list
      account_id=<UUID>
    

    Common Workflows

    MSP Dashboard Overview

    1. blumira_msp_accounts_list to get all managed accounts
    2. blumira_msp_findings_all with status.eq=10 for open findings across all accounts
    3. Group findings by account to produce per-account open finding counts
    4. Highlight accounts with CRITICAL/HIGH severity findings

    Per-Account Triage

    1. blumira_msp_findings_list for the target account with status.eq=10
    2. Sort by severity to prioritize
    3. Investigate with blumira_msp_findings_get and comments
    4. Resolve with blumira_msp_findings_resolve

    Cross-Account Security Posture

    1. blumira_msp_accounts_list to enumerate accounts
    2. For each account, query open findings by severity
    3. Query device counts with blumira_msp_devices_list
    4. Compile into a posture report showing coverage and risk per account

    Agent Coverage Audit

    1. blumira_msp_accounts_list to get accounts
    2. For each account, blumira_msp_devices_list to count devices
    3. Compare against known device counts per client
    4. Identify coverage gaps

    Error Handling

    403 on MSP Endpoints

    Cause: JWT token is org-level, not MSP-level Solution: Generate an MSP-scoped JWT token from the Blumira portal.

    Account Not Found

    Cause: Invalid account ID or account not managed by this MSP Solution: Use blumira_msp_accounts_list to verify available accounts.

    Cross-Account Query Timeout

    Cause: Too many accounts or too broad a filter Solution: Narrow filters (date range, severity) or query accounts individually.

    Best Practices

    • Cache the account list at the start of MSP operations to avoid redundant calls
    • Use blumira_msp_findings_all for overview, then drill into specific accounts
    • Maintain consistent resolution standards across all managed accounts
    • Document per-account context in finding comments for compliance
    • Schedule regular cross-account posture reviews
    • Use severity filters on cross-account queries to focus on what matters

    Related Skills

    Frequently asked questions

    What to verify before installation and use

    What does the Blumira MSP source document cover?

    Blumira's MSP path group (`/msp/*`): managed-account enumeration, cross-account and per-account finding queries, per-account device, agent-key and user management, and how MSP paths differ from org paths.

    How do I install Blumira MSP?

    The source record exposes this install command: npx skills add https://github.com/WYRE-AI/msp-claude-plugins --skill "msp-claude-plugins/blumira/blumira/skills/msp". Inspect the command and pinned source before running it.

    Alternatives

    Compare before choosing

    Computed 10029,236

    garrytan/gbrain

    bulk-ingestion

    End-to-end discipline for turning any large data source (audio libraries, email takeouts, document corpora, chat exports, API dumps) into brain pages at scale. The lifecycle spine: SCHEMA → ACCESS → TRIAL → EVALUATE → IMPROVE → CODIFY → TEST → SKILLIFY → BULK → MONITOR. State is tracked in a durable JSON manifest (see MANIFEST-PATTERN.md) so any crash, session boundary, or subagent fan-out resumes from ground truth instead of memory.

    Computed 10025,136

    alirezarezvani/claude-skills

    app-store-optimization

    App Store Optimization (ASO) toolkit for researching keywords, analyzing competitor rankings, generating metadata suggestions, and improving app visibility on Apple App Store and Google Play Store. Use when the user asks about ASO, app store rankings, app metadata, app titles and descriptions, app store listings, app visibility, or mobile app marketing on iOS or Android. Supports keyword research and scoring, competitor keyword analysis, metadata optimization, A/B test planning, launch checklist

    Computed 1005,277

    dotnet/skills

    migrate-vstest-to-mtp

    Migrates .NET test projects from VSTest to Microsoft.Testing.Platform (MTP). Use when user asks to "migrate to MTP", "switch from VSTest", "enable Microsoft.Testing.Platform", "use MTP runner", set OutputType=Exe only for test projects in Directory.Build.props, or mentions EnableMSTestRunner, EnableNUnitRunner, or UseMicrosoftTestingPlatformRunner. USE FOR: MTP behavioral differences vs VSTest (exit code 8, zero tests discovered, --ignore-exit-code, TESTINGPLATFORM_EXITCODE_IGNORE); centralizing

    Computed 100147

    oaustegard/claude-skills

    featuring

    Generate hierarchical _FEATURES.md files that describe what a codebase DOES from a user/consumer perspective, anchored to source symbols via tree-sitting. Supports large complex codebases through feature-driven decomposition into sub-feature files. Uses a multi-pass synthesis: orientation → detail → overview rewrite. Use when someone says "what does this do", "document features", "feature inventory", "_FEATURES.md", or needs to understand a codebase's purpose before modifying it. Complements tre