Airtable

v0.1.0

Browse Airtable bases and tables, inspect records, and perform available Airtable actions such as creating records, comments, fields, or tables when supporte...

0· 28·0 current·0 all-time

Install

OpenClaw Prompt Flow

Install with OpenClaw

Best for remote or guided setup. Copy the exact prompt, then paste it into OpenClaw for hith3sh/airtable-records.

Previewing Install & Setup.
Prompt PreviewInstall & Setup
Install the skill "Airtable" (hith3sh/airtable-records) from ClawHub.
Skill page: https://clawhub.ai/hith3sh/airtable-records
Keep the work scoped to this skill only.
After install, inspect the skill metadata and help me finish setup.
Use only the metadata you can verify from ClawHub; do not invent missing requirements.
Ask before making any broader environment changes.

Command Line

CLI Commands

Use the direct CLI path if you want to install manually and keep every step visible.

OpenClaw CLI

Bare skill slug

openclaw skills install airtable-records

ClawHub CLI

Package manager switcher

npx clawhub@latest install airtable-records
Security Scan
Capability signals
Requires sensitive credentials
These labels describe what authority the skill may exercise. They are separate from suspicious or malicious moderation verdicts.
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
medium confidence
Purpose & Capability
The name/description (Airtable record browsing and basic writes) match the SKILL.md. The skill requests no binaries, env vars, or config paths—nothing appears unnecessary for the stated Airtable helper purpose.
Instruction Scope
SKILL.md stays on-scope: it instructs the agent to check connection state and available actions, prefer reads before writes, ask clarifying questions, and avoid fabricating capabilities. It explicitly forbids requesting tokens and unrelated local data. Note: actual behavior at runtime depends on the connected tool/integration the agent uses.
Install Mechanism
No install spec and no code files (instruction-only) — this is the lowest-risk install model; nothing will be written to disk by the skill itself.
Credentials
The skill declares no required environment variables, credentials, or config paths. It also instructs not to ask users to paste secrets, which is proportionate for an Airtable helper that should rely on existing integrations.
Persistence & Privilege
always:false and user-invocable:true (defaults). The skill does not request permanent presence or system-wide changes. Autonomous invocation is allowed by platform defaults but this skill does not elevate privilege by itself.
Assessment
This skill appears coherent and low-risk because it's instruction-only and asks for no extra credentials. Before enabling it, confirm the source/author if you care about provenance (registry owner ID is present but no homepage/source URL), verify any Airtable integration the agent will use has the minimal permissions needed, and always review and approve any write actions the agent proposes. Never paste API keys or session cookies into chat; if a connection is required, use the platform's official integration flow. If you need higher assurance, ask the maintainer for a homepage or repo you can audit.

Like a lobster shell, security has layers — review code before you run it.

latestvk979fqjx5pd4fgazjk50yb840s85pdvq
28downloads
0stars
1versions
Updated 6h ago
v0.1.0
MIT-0

Airtable

Work with Airtable from chat to browse bases and tables, inspect records, and perform available actions when they are supported by the connected integration.

Overview

Use this skill for common Airtable work such as:

  • listing available bases and tables
  • reading records from a table or view
  • retrieving a specific record
  • creating records in bulk when supported
  • creating or updating comments, fields, or tables when those actions are exposed and clearly requested

Keep responses practical, concrete, and grounded in what is actually available.

How to work

Use this workflow:

  1. Identify the Airtable task
  2. Check whether Airtable is connected
  3. Check which Airtable tools and actions are currently available
  4. Prefer read and inspection actions before writes when they reduce ambiguity
  5. If a write is requested, state clearly what will change before doing it
  6. If multiple bases, tables, or records may match, ask the user to disambiguate
  7. If the requested capability is not available, say so plainly

What this helps with

Examples:

  • list Airtable bases
  • show tables in a base
  • list records in a table or view
  • fetch a record by ID
  • create records in bulk
  • add or update a comment
  • create or update a field or table when supported
  • explain whether a requested Airtable action is currently available

Connection

Before doing Airtable work:

  • verify whether Airtable is connected
  • if it is not connected, guide the user through the available connection flow
  • do not ask the user to paste raw access tokens, session cookies, passwords, or private credentials into chat
  • do not use unofficial login or harvested browser-session flows

Treat the current connection state and live tool catalog as authoritative.

Safety

Operate with a narrow scope:

  • use only the minimum inputs needed for the requested Airtable task
  • do not access unrelated local files, secrets, environment variables, or configuration data
  • do not perform unrelated outbound calls
  • clearly disclose when an action will create, update, or delete Airtable data or schema
  • prefer the least risky action that still solves the request

Behavioral rules

Follow these rules every time:

  • use the live Airtable tool set as the source of truth
  • do not claim full Airtable coverage
  • do not fabricate unsupported bases, tables, fields, or actions
  • do not imply write support just because read support exists
  • ask clarifying questions when the intended base, table, or record is ambiguous
  • summarize risky or destructive changes before performing them

Example requests

  • List my Airtable bases
  • Show the tables in this Airtable base
  • List records in this Airtable table
  • Get this Airtable record
  • Create these Airtable records if supported
  • Add a comment to this Airtable record
  • Update this Airtable field if supported
  • Delete this Airtable record if supported and explicitly requested

Limits

Actual capability depends on:

  • whether the user's Airtable account is connected
  • which Airtable actions are currently exposed by the connected tool set
  • the permissions granted by the connected Airtable account

If an action is unavailable, say so plainly. Do not pretend the skill can do it anyway.

Response style

Be clear and operational:

  • say what was found
  • say what is supported
  • say when Airtable must be connected first
  • say when an action will write data
  • say when a capability is unavailable

Keep answers useful, direct, and easy to audit.

Resources

Comments

Loading comments...