Teable
PassAudited by ClawScan on May 10, 2026.
Overview
The skill appears to do what it says—manage Teable through its API—but it can use your Teable token to read, change, share, export, and delete Teable data.
Install this only if you want an agent to manage Teable resources. Use a least-privilege TEABLE_API_KEY, set TEABLE_URL only to a trusted HTTPS Teable instance, and require explicit confirmation before deletes, trash reset/permanent delete, bulk updates, collaborator changes, or invitation-link creation.
Findings (3)
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.
A mistaken or overly broad agent instruction could delete or permanently remove Teable data.
The skill exposes destructive Teable operations, including permanent deletion from trash. This is purpose-aligned and disclosed, but high-impact commands should be user-confirmed.
`teable_trash.py` | Trash management + restore + permanent delete
Use least-privilege Teable tokens where possible, confirm resource IDs before destructive commands, and require explicit approval for delete, trash reset, and bulk record operations.
The token can authorize significant account actions, including changing who can access Teable resources.
The scripts use the user's Teable API token and include operations that can grant or change access to bases through collaborators and invitation links.
"Authorization": f"Bearer {self.api_key}" ... def add_collaborator(... role: str) ... def create_invitation_link(... role: strUse a token scoped only to the needed Teable resources and review any collaborator, role, or invitation-link action before running it.
Dependency installation will rely on the package index and the version resolved at install time.
The skill depends on the external requests package with a lower-bound version and no lockfile/hash pin in the provided artifacts. This is common and purpose-aligned, but not fully reproducible.
requests>=2.28.0
Install dependencies from trusted package indexes and consider pinning or reviewing the resolved requests version in controlled environments.