More screenshots

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIDeepSeekDeepSeekMuseMuse+22 more

    Airtable Planner

    1

    Syncs AI agent implementation plans and coding progress to a live Airtable Kanban board for real-time project tracking.

    $10

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    Airtable Planner

    Airtable Planner

    Example session with this skill installed

    Plan a Jobber integration so our AI phone agent can book appointments and capture leads directly in a customer's Jobber account.

    • Read your context and instructions
    • Compiled the airtable planner

    Summary

    I've staged the plan in Airtable as a new Feature with 6 ordered tickets, all set to New. Nothing has been started yet. Say

    proceed when you're ready and I'll work them in order, updating the board as I go.

    Feature: Jobber integration: appointment booking + lead capture

    Status: New

    Goal: Let the AI agent book appointments and create leads/requests in a business's Jobber account during a call.
    Out of scope: Two-way sync of existing Jobber clients; invoicing.
    Approach: OAuth2 connection per business, a client wrapper over Jobber's GraphQL API, then expose booking and lead capture as agent tools.
    Risks / open questions: Jobber's GraphQL schema for availability needs confirming before we build on it (ticket 1 is a spike for exactly that).

    Tickets

    #TicketStatusRepo
    1Spike: confirm Jobber GraphQL schema for requests, notes, availabilityNewplatform
    2Backend: Jobber OAuth2 connect flowNewplatform
    3Backend: JobberClient + JobberIntegration (booking + lead capture)Newplatform
    4Backend: wire Jobber into agent tools (booking / callback capture)Newplatform
    5Frontend: Jobber card in Integrations tabNewapp
    6e2e: live Jobber booking/lead-capture scenario testNewplatform

    Each ticket's Description has what to do, key files, and acceptance criteria as a checklist. For example, ticket 2:

    What to do: add a Jobber OAuth2 connect/callback flow that stores tokens per business.
    Acceptance criteria

    • Connect button redirects to Jobber and returns to the Integrations tab
    • Tokens stored encrypted and refreshed automatically
    • Disconnect revokes and clears tokens
    • Feature tests cover connect, callback, refresh, and disconnect

    Next steps

    • Review the tickets on your Airtable board. You can edit, reorder, or delete any of them; I'll read the current state before starting.
    • Reply

    proceed to start. I'll move ticket 1 to In Progress, create feature/jobber-integration, record the branch URL on each ticket, and mark tickets Complete (with progress notes and PR links) as tests pass.

    • When all six are done the Feature goes to Pending Approval for your sign-off.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    Your coding agent's plan usually lives in the chat, where it scrolls away and gets lost between sessions. This skill has the agent write every implementation plan to Airtable as a Feature with ordered Tickets. It then keeps each ticket's status up to date while it works, so you get a live Kanban board of what the agent is doing, what's done, and what's blocked.

    What it does

    • Staged plans: When you ask for a plan, the agent breaks the work into ordered, individually shippable tickets, each with acceptance criteria and a repo. It stages them as New and waits for your go-ahead before writing any code.
    • Live status: Each ticket moves to In Progress before the agent starts it and to Complete once tests pass and the work is committed. Progress notes and PR links are appended as it goes.
    • Blockers surfaced: A ticket the agent can't finish goes to Blocked, with the reason and what's needed to unblock it. The agent doesn't quietly skip ahead.
    • You approve: When all tickets are done, the Feature moves to Pending Approval. Only you mark it Complete.
    • Backlog: You can drop bugs and ideas into a Backlogs table at any time. "Work the backlog" turns the oldest one into a staged plan.
    • Status reports: Ask "where are we?" and you get a short table of open features, ticket counts, and blockers.
    • Multi-repo: Each ticket is tagged with its repo. Branch names and GitHub branch URLs are recorded automatically.

    Setup

    1. Connect the Airtable MCP server to your agent (the README has the one-line command for Claude Code).
    2. Create an empty Airtable base for your project.
    3. Ask your agent to "set up the Airtable planner." It creates the Config, Features, Tickets and Backlogs tables, confirms your GitHub owner and repos, and writes a small pointer file (base ID only, no credentials) into your project.
    4. Add Kanban views grouped by Status, and watch the board.

    Why not just prompt for it?

    Without a fixed schema and status rules, agents improvise: they create new fields, lose track of multi-step plans across sessions, or report work as done when it's stuck. This skill gives the agent a fixed schema and a clear lifecycle, so the board stays trustworthy.

    Good for

    • Multi-session features where you want to pick up exactly where the agent left off
    • Multi-repo projects (for example, a backend platform plus a frontend app)
    • Founders and stakeholders who want to see progress without reading the agent's transcripts

    What's included

    SKILL.md, references/schema.md (the canonical Airtable schema), references/setup.md (setup and verification steps), and README.md.

    Notes

    • Requires an Airtable account (the free plan works) and the Airtable MCP server.
    • GitHub is optional; it's used for branch and PR links.
    • Built and used daily with Claude Code on real production projects.

    Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for Agents & Orchestration.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before buying a skill.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Money-back guarantee

    Doesn't do what its page promises? You get your money back.

    Trust & safety

    Security scan

    Security scan passed 25 days ago

    Accounts
    Airtable MCP
    Software
    Git

    Permissions

    Write Files
    Terminal / Shell
    Read Files
    Listed25 days ago

    What's inside

    Frequently Asked Questions

    This skill provides a structured bridge between an AI's internal reasoning and your project management workflow, preventing the agent from losing track of long-term goals during multi-step coding sessions.

    Yes, you will need an active Airtable account and the Airtable MCP server installed to facilitate the connection between the agent and your Kanban board.

    The skill includes a pre-configured schema guide; once your Airtable base is set up and the JSON pointer is initialized in your project directory, the agent will automatically begin syncing tasks.

    This skill is designed to work with any AI agent that supports the Model Context Protocol (MCP) and has access to your local filesystem for reading configuration files.

    While the agent autonomously moves tickets to 'In Progress' and 'Complete,' it is programmed to require explicit user confirmation before a high-level Feature is marked as fully finished.

    The skill automatically links GitHub branch names and Pull Request URLs to the specific Airtable tickets they satisfy, creating a clear audit trail between your code and your task board.

    New in Agents & Orchestration