AgentStack
SKILL verified MIT Self-run

Shopify Admin Staff Account Audit

skill-40rty-ai-shopify-admin-skills-shopify-admin-staff-account-audit · by 40RTY-ai

Read-only: reviews staff accounts for stale logins, inactive status, and overpermissioned roles to surface security and access hygiene issues.

No reviews yet
0 installs
0 views
view→install

Install

$ agentstack add skill-40rty-ai-shopify-admin-skills-shopify-admin-staff-account-audit

✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • Prompt-injection patterns
  • Secret / credential exfiltration
  • Dangerous shell & filesystem operations
  • Untrusted network calls
  • Known-malicious package signatures
Are you the author of Shopify Admin Staff Account Audit? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.

About

Purpose

Audits all staff member accounts on the store to surface security and access-hygiene risks. Flags accounts that have not logged in for more than stale_days days, accounts that are inactive but still provisioned, and accounts with full / shop-owner-equivalent permissions. Read-only — no mutations. Provides the data foundation for a follow-up access review or deprovisioning workflow.

Prerequisites

  • Authenticated Shopify CLI session: shopify store auth --store --scopes read_users
  • API scopes: read_users
  • Caller must be Shop Owner or have staff-management permissions to query staff data

Parameters

| Parameter | Type | Required | Default | Description | |-----------|------|----------|---------|-------------| | store | string | yes | — | Store domain (e.g., mystore.myshopify.com) | | staledays | integer | no | 90 | Flag accounts with no login activity in this many days | | includeinactive | bool | no | true | Include accounts where active: false in the audit output | | include_owner | bool | no | false | Include the shop owner row in flagged-account counts | | format | string | no | human | Output format: human or json |

Safety

> ℹ️ Read-only skill — no mutations are executed. Safe to run at any time. No staff accounts are deactivated or modified by this skill.

Workflow Steps

  1. OPERATION: staffMembers — query

Inputs: first: 250, select id, name, email, active, isShopOwner, accountType, locale, lastSeen, pagination cursor Expected output: All staff members with status and last-login data; paginate until hasNextPage: false

  1. Compute days_since_last_seen per member. Flag any member with days_since_last_seen > stale_days as stale.
  1. Flag any member with active: false (or accountType: SUSPENDED) as inactive but provisioned.
  1. Flag any member with isShopOwner: true or accountType: COLLABORATOR with full permissions as high privilege for review.
  1. Cross-tabulate: produce per-account record with all flags joined (stale, inactive, high_privilege).

GraphQL Operations

# staffMembers:query — validated against api_version 2025-01
query StaffAccountAudit($after: String) {
  staffMembers(first: 250, after: $after) {
    edges {
      node {
        id
        name
        email
        active
        isShopOwner
        accountType
        locale
        exists
        phone
        avatar {
          url
        }
        privateData {
          accountSettingsUrl
          createdAt
        }
      }
    }
    pageInfo {
      hasNextPage
      endCursor
    }
  }
}

Session Tracking

Claude MUST emit the following output at each stage. This is mandatory.

On start, emit:

╔══════════════════════════════════════════════╗
║  SKILL: Staff Account Audit                  ║
║  Store:                        ║
║  Started:              ║
╚══════════════════════════════════════════════╝

After each step, emit:

[N/TOTAL]   
          → Params: 
          → Result: 

On completion, emit:

For format: human (default):

══════════════════════════════════════════════
STAFF ACCOUNT AUDIT  (stale threshold:  days)
  Total staff accounts:   
  Active:                 
  Inactive (provisioned): 
  Stale logins (>Nd):       (%)
  High-privilege roles:   

  Flagged accounts (top by risk):
    ""   last_seen:   flags: 
  Output: staff_audit_.csv
══════════════════════════════════════════════

For format: json, emit:

{
  "skill": "staff-account-audit",
  "store": "",
  "stale_days_threshold": 90,
  "total_accounts": 0,
  "active_accounts": 0,
  "inactive_accounts": 0,
  "stale_accounts": 0,
  "high_privilege_accounts": 0,
  "output_file": "staff_audit_.csv"
}

Output Format

CSV file staff_audit_.csv with columns: staff_id, name, email, account_type, is_shop_owner, active, last_seen, days_since_last_seen, is_stale, is_inactive, is_high_privilege, flags

Error Handling

| Error | Cause | Recovery | |-------|-------|----------| | THROTTLED | API rate limit exceeded | Wait 2 seconds, retry up to 3 times | | ACCESS_DENIED on staffMembers | Caller lacks read_users or staff-mgmt permission | Re-auth as Shop Owner / staff-admin | | lastSeen: null on a staff member | Account never logged in | Treat as days_since_last_seen = days_since_account_created; flag as stale | | Empty staff list | Single-operator store (owner only) | Exit with 1 row (the owner); skill is still useful for record-keeping |

Best Practices

  • Run quarterly (90-day cadence) as part of routine access reviews. Pair with the offboarding checklist — every former employee should be revoked, not merely deactivated.
  • Use stale_days: 30 for high-risk stores (high-volume, large staff) and stale_days: 180 for very small teams where seasonal access is normal.
  • Sort the CSV by days_since_last_seen descending to prioritize the longest-stale accounts first.
  • High-privilege accounts (Shop Owner, full-permission collaborators) should have unique strong credentials and 2FA — treat any stale high-privilege account as a P0 review item.
  • Export the CSV into your access-review tracker; do not deactivate accounts blindly — confirm with the account holder's manager first.
  • Cross-reference flagged stale accounts with recent staffMember-scoped audit log events before deprovisioning to ensure there is no in-flight work.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet — be the first.

Versions

  • v0.1.0 Imported from the upstream source.