OfficeX
WarnAudited by ClawScan on May 10, 2026.
Overview
This instruction-only OfficeX API skill is not malware, but it documents broad financial, account, and full-admin API access without clear guardrails, so it needs careful review before use.
Only use this skill with test or least-privileged OfficeX credentials unless you fully trust the source. Do not provide superadmin secrets casually. Confirm every action that changes billing, wallets, installs, app publication, keys, or account data before letting an agent make API calls.
Findings (5)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
If an agent used a superadmin secret, it could affect the entire OfficeX system rather than just the user's own account or app.
The skill documents a full-system admin credential, which is much broader than normal end-user or app-developer access and is not declared in the registry credential metadata.
Superadmin | `x-officex-admin-secret` | Full system (`/admin/*`)
Do not provide admin secrets unless you are an authorized OfficeX administrator. The skill should separate admin-only documentation from consumer/developer workflows and clearly declare required credentials and scopes.
An agent following this skill could spend or move credits, change installations, publish apps, or modify account state if given credentials and HTTP tooling.
The skill is intended to guide broad REST API calls, including financial and account-mutating actions, but the provided artifact does not show clear approval boundaries for those high-impact operations.
Use when: (1) Making HTTP calls to OfficeX cloud API, (2) Building or publishing apps on the platform, (3) Implementing billing (reserve/settle/sip/payout), (4) Managing users, installs, wallets
Use only with explicit user approval for each mutating or financial request. Prefer staging first, set spending limits, and use the least-privileged credential available.
Master keys and install secrets could allow account changes or billing actions if exposed or used incorrectly.
The skill requires handling account and billing credentials, while the registry metadata lists no required environment variables or primary credential.
Master Key | `x-officex-user-id` + `x-officex-master-key` | Profile, installs, wallets, vendor apps ... Install Secret | `x-officex-install-id` + `x-officex-install-secret` | Billing: reserve, settle, cancel, inbox
Store OfficeX credentials securely, rotate them if exposed, and avoid pasting broad master keys into chats unless absolutely necessary.
Stored context could shape later agent responses or actions, especially if it contains incorrect or hostile instructions.
The skill references stored agent context and context prompts, which are purpose-aligned for an AI integration but may influence future agent behavior if untrusted content is written or reused.
Integrating with the AI chat agent (agent_context, documentation, context_prompt) ... PATCH /users/me/installs/{id}/context { key: val | null } → { agent_context }Review any agent_context or context_prompt values before storing or reusing them, and avoid treating remote app-provided context as automatically trustworthy.
Users may not be able to easily verify that this OfficeX API guidance was published by an official or trusted source.
The skill has no code installation risk, but its provenance is unclear for a credentialed cloud API integration.
Source: unknown; Homepage: none
Confirm the skill publisher and OfficeX documentation independently before using real credentials or production accounts.