Menu
Connect to an Azure subscription, validate credentials, and discover what services are in use.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Deep code scan for AI security issues — prompt injection, PII in prompts, hardcoded keys, unguarded agents.
Run AI governance checks across cloud accounts and code repos — ISO 42001, EU AI Act, NIST AI RMF compliance.
Scan cloud accounts and GitHub repos to discover AI/ML services and build an AI system inventory.
Walk staged changes against the engineering principles checklist and report pass/fail per principle. Run before any non-trivial commit. Catches doc drift, stub functions, single-region defaults, missing framework mappings, and other regressions before they ship.
Generate a public-facing security trust page from scan data. Produces a single deployable index.html that shows compliance framework scores, security policies, infrastructure overview, and data protection posture. Deployable to S3, Vercel, Netlify, or GitHub Pages.
Paste a vendor's domain. Get a security risk assessment in 60 seconds.
| name | connect-azure |
| description | Connect to an Azure subscription, validate credentials, and discover what services are in use. |
| user-invocable | true |
You are helping a semi-technical founder connect Shasta to their Azure subscription for SOC 2 and ISO 27001 compliance scanning.
Shasta uses shasta.config.json in the project root for all settings. Before running any commands, check if this file has azure_subscription_id set. If not, you'll need to configure it.
Check if shasta.config.json is configured for Azure. Read the file. If azure_subscription_id is empty, ask the user:
az login? If not, tell them to run ! az login first.az account show to get their subscription ID, tenant ID, and current region.centralindia, eastus, westeurope)company_name is still empty, ask for it too.Update shasta.config.json with their answers — set azure_subscription_id, azure_tenant_id, and azure_region.
Also detect the correct Python command if python_cmd isn't set. Run python3 --version and python --version to find which works. Update python_cmd in the config.
Validate Azure credentials by running (substitute the correct python command):
<PYTHON_CMD> -c "
from shasta.config import get_azure_client
c = get_azure_client()
info = c.validate_credentials()
services = c.discover_services()
print(f'Azure Subscription: {info.subscription_name} ({info.subscription_id})')
print(f'Tenant: {info.tenant_id}')
print(f'Identity: {info.user_principal}')
print(f'Region: {info.region}')
print(f'Services detected: {services if services else \"none (empty subscription)\"}')
"
Initialize the Shasta database (if not already done):
<PYTHON_CMD> -c "from shasta.db.schema import ShastaDB; db = ShastaDB(); db.initialize(); print('Database initialized at data/shasta.db')"
Present results in a clear, friendly format and suggest running /scan next.
az login or service principal environment variables.<PYTHON_CMD> with whatever works on this machine (python3, python, or py -3.12).az login or az account set --subscription <ID>.