Vercel Edge Config 監査

# Vercel Edge Config Audit

Inventory Vercel Edge Config data and remote-cache status without exposing secret values.

## Required Aident Actions

- <action-tag>composio:vercel_tools:vercel_list_edge_configs</action-tag> (required inputs: inspect the current schema): Tool to retrieve all Edge Configs for an account or team. Use when you need to list all Edge Config definitions.
- <action-tag>composio:vercel_tools:vercel_list_edge_config_items</action-tag> (required inputs: edgeConfigId): Tool to retrieve all items from a specific Edge Config. Use when you need to inspect all key-value pairs stored in an Edge Config.
- <action-tag>composio:vercel_tools:vercel_get_cache_status</action-tag> (required inputs: inspect the current schema): Tool to get the status of Remote Caching for the principal. Use when you need to check if Remote Caching is enabled, disabled, over limit, or paused.

Use Aident Loadout to read the current Action schema before constructing inputs. Check the required integration connection in Aident Vault. If an Action is billable or mutating, run Aident preflight, show the affected target and quoted cost or risk, and wait for explicit user confirmation before execution.

## Workflow

1. Confirm the requested outcome, source material, destination, audience, constraints, and acceptance criteria.
2. Apply the source-derived guidance below to create a concrete plan. Resolve ambiguity before invoking an Action.
3. Select only the Aident Actions whose documented effect directly advances the requested outcome. Do not invoke every listed Action by default.
4. Inspect the current schema and prepare the minimum valid input for each selected Action.
5. Preflight each selected Action. Execute it only after any required confirmation, in dependency order, and carry returned IDs or asset URLs into later steps.
6. Verify the returned IDs, URLs, statuses, or artifacts against the acceptance criteria. Report partial completion precisely and do not repeat paid or mutating calls blindly.

## Source-Derived Guidance

- Confirm team scope and Edge Config ID before listing items.
- Report keys, metadata, and cache state while redacting values that may be sensitive.

## Execution Boundaries

- Treat upstream provider-specific commands as background knowledge only. Execute the workflow through the exact Aident Actions above.
- Never request raw credentials in chat. Use Aident Vault connection flows for required accounts.
- Preserve user-provided wording, brand constraints, rights restrictions, and target identifiers. Do not invent authorization.
- Read current state before a mutation, state the exact target, and include a rollback or recovery step in the result.
- Stop when a required integration is disconnected, preflight rejects the input, the target is ambiguous, or the user declines a required confirmation.

## Output

Return the execution plan, selected Action names, confirmed targets, Aident result identifiers or asset URLs, verification evidence, and any remaining blocked step.

## Attribution

This Skill adapts the reviewed upstream workflow. See [UPSTREAM.md](UPSTREAM.md) for the pinned source and [LICENSE.txt](LICENSE.txt) for the preserved license.