Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Tencent SkillHub ยท Productivity
AuditClaw Idp
Identity provider compliance checks for auditclaw-grc. 8 read-only checks across Google Workspace (MFA, admin audit, inactive users, passwords) and Okta (MFA...
skill openclawclawhub Free
Identity provider compliance checks for auditclaw-grc. 8 read-only checks across Google Workspace (MFA, admin audit, inactive users, passwords) and Okta (MFA...
โฌ 0 downloads โ
0 stars Unverified but indexed
Install for OpenClaw
Quick setup
- Download the package from Yavira.
- Extract the archive and review SKILL.md first.
- Import or place the package into your OpenClaw setup.
Package facts
- Download mode
- Yavira redirect
- Package format
- ZIP package
- Source platform
- Tencent SkillHub
- What's included
- README.md, scripts/requirements.txt, scripts/checks/google_mfa.py, scripts/checks/okta_inactive.py, scripts/checks/google_admins.py, scripts/checks/okta_mfa.py
Validation
- Use the Yavira download entry.
- Review SKILL.md after the package is downloaded.
- Confirm the extracted package contains the expected setup assets.
Install with your agent
Agent handoff
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
- Download the package from Yavira.
- Extract it into a folder your agent can access.
- Paste one of the prompts below and point your agent at the extracted folder.
New install
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Then review README.md for any prerequisites, environment setup, or post-install checks. Tell me what you changed and call out any manual steps you could not complete.
Upgrade existing
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Then review README.md for any prerequisites, environment setup, or post-install checks. Summarize what changed and any follow-up checks I should run.
Trust & source
Release facts
- Source
- Tencent SkillHub
- Verification
- Indexed source record
- Version
- 1.0.2
Provenance
- Publisher
- mailnike
- Source page
- View original listing
- Canonical URL
- Open canonical page
Documentation
AuditClaw IDP
Companion skill for auditclaw-grc. Collects compliance evidence from Google Workspace and Okta identity providers using read-only API calls. 8 checks | Read-only API access | Evidence stored in shared GRC database
Security Model
Read-only access: Google Workspace uses admin.directory.user.readonly scope only. Okta uses okta.users.read, okta.factors.read, okta.policies.read scopes only. No write/modify permissions. Credentials: Uses standard env vars for each provider. No credentials stored by this skill. Dependencies: Google API client + requests (all pinned in requirements.txt) Data flow: Check results stored as evidence in ~/.openclaw/grc/compliance.sqlite via auditclaw-grc
Prerequisites
Google Workspace: Service account JSON with domain-wide delegation, admin email for impersonation Okta: API token (SSWS) with read-only scopes pip install -r scripts/requirements.txt auditclaw-grc skill installed and initialized
Google Workspace (optional; skip if not configured)
GOOGLE_WORKSPACE_SA_KEY: Path to service account JSON file GOOGLE_WORKSPACE_ADMIN_EMAIL: Super admin email to impersonate
Okta (optional; skip if not configured)
OKTA_ORG_URL: Okta organization URL (e.g., https://mycompany.okta.com) OKTA_API_TOKEN: Okta API token
Commands
"Run IDP evidence sweep": Run all checks for configured providers "Check Google Workspace MFA": Run Google MFA check "Check Okta password policies": Run Okta password policy check "Show IDP integration health": Last sync, errors, evidence count
Usage
All evidence is stored in the shared GRC database at ~/.openclaw/grc/compliance.sqlite via the auditclaw-grc skill's db_query.py script. To run a full evidence sweep (all configured providers): python3 scripts/idp_evidence.py --db-path ~/.openclaw/grc/compliance.sqlite --all To run checks for a specific provider: python3 scripts/idp_evidence.py --db-path ~/.openclaw/grc/compliance.sqlite --provider google python3 scripts/idp_evidence.py --db-path ~/.openclaw/grc/compliance.sqlite --provider okta To run specific checks: python3 scripts/idp_evidence.py --db-path ~/.openclaw/grc/compliance.sqlite --checks google_mfa,okta_mfa
Check Categories (8)
CheckProviderWhat It Verifiesgoogle_mfaGoogle WorkspaceAll active users have 2SV enrolled + enforcedgoogle_adminsGoogle WorkspaceSuper admin count 2-4, all with 2SVgoogle_inactiveGoogle WorkspaceNo active users with lastLoginTime > 90 daysgoogle_passwordsGoogle WorkspaceAll users have passwordStrength == "STRONG"okta_mfaOktaAll active users have at least 1 MFA factor enrolledokta_passwordsOktaPassword policy: minLength>=12, history>=5, maxAttempts<=5, maxAge<=90okta_inactiveOktaNo active users with lastLogin > 90 daysokta_sessionsOktaMFA required, session lifetime <= 12h, idle <= 1h
Evidence Storage
Each check produces evidence items stored with: source: "idp" type: "automated" control_id: Mapped to relevant SOC2/ISO/NIST/HIPAA controls description: Human-readable finding summary file_content: JSON details of the check result
Setup Guide
AuditClaw supports two identity providers. Configure one or both.
Google Workspace Setup
Step 1: Enable Admin SDK API Go to Google Cloud Console โ APIs & Services โ Library โ Enable "Admin SDK API" Step 2: Create Service Account IAM & Admin โ Service Accounts โ Create. Enable domain-wide delegation. Step 3: Grant OAuth Scopes In Google Admin โ Security โ API controls โ Domain-wide delegation, add the service account with: https://www.googleapis.com/auth/admin.directory.user.readonly https://www.googleapis.com/auth/admin.reports.audit.readonly Step 4: Set Environment Variables GOOGLE_WORKSPACE_SA_KEY=/path/to/service-account.json GOOGLE_WORKSPACE_ADMIN_EMAIL=admin@yourdomain.com
Okta Setup
Step 1: Create API Token Okta Admin โ Security โ API โ Tokens โ Create Token. Name: auditclaw-scanner Step 2: Required Permissions The token inherits the creating admin's permissions. Needs read access to: users, factors, policies. Scopes: okta.users.read, okta.factors.read, okta.policies.read Step 3: Set Environment Variables OKTA_ORG_URL=https://mycompany.okta.com OKTA_API_TOKEN=your-token-here
Verify Connection
Run: python3 {baseDir}/scripts/idp_evidence.py --test-connection The exact permissions are documented in scripts/idp-permissions.json. Show with: python3 {baseDir}/../auditclaw-grc/scripts/db_query.py --action show-policy --provider idp
Category context
Workflow acceleration for inboxes, docs, calendars, planning, and execution loops.
Source: Tencent SkillHub
Largest current source with strong distribution and engagement signals.
Package contents
Included in package
4 Scripts1 Docs1 Files
- README.md
- scripts/checks/google_admins.py
- scripts/checks/google_mfa.py
- scripts/checks/okta_inactive.py
- scripts/checks/okta_mfa.py
- scripts/requirements.txt