AGENT SKILL

work-board-airtable-bridge

Use when a user wants to connect Airtable task records to the HivemindOS Work Board, import an Airtable board, mirror status back to Airtable, or keep one external stakeholder-facing Airtable board aligned with Queen Bee tasks. Do not use this as a replacement for the built-in Work Board.

License 许可
MIT
最近更新
2026-11-10
Stars
★ 13
Forks
4

01 前言 Front Matter

name
work-board-airtable-bridge
description
Use when a user wants to connect Airtable task records to the HivemindOS Work Board, import an Airtable board, mirror status back to Airtable, or keep one external stakeholder-facing Airtable board aligned with Queen Bee tasks. Do not use this as a replacement for the built-in Work Board.

02 资源文件 1

03 SKILL.md 正文

Work Board Airtable Bridge

Connect an Airtable task table to HivemindOS without making Airtable the source of truth for agent coordination.

Rule

HivemindOS already has built-in work tracking: the dashboard Work Board, /api/kanban, Queen Bee routing, scheduler/history views, and the shared vault folder Operations/Work Board/. Use that as the canonical board for agent work. Airtable is only an external intake, reporting, or stakeholder mirror unless the user explicitly says the Airtable base is the authority.

Use Cases

  • Import Airtable records into Work Board tasks.
  • Link an Airtable record to one Work Board card or Queen Bee run.
  • Mirror Work Board status, assignee, verification notes, and artifact URLs back to Airtable.
  • Create an Airtable-facing report for non-HivemindOS collaborators.
  • Reconcile drift between Airtable and Work Board.

Capability Map

  • Work Board: use existing HivemindOS Kanban APIs, dashboard task actions, Queen Bee routing, and shared vault storage.
  • Airtable: load the airtable skill if available, or use Airtable REST with credentials checked by key name only, such as AIRTABLE_API_KEY.
  • Memory: record durable board conventions only when the user confirms them as reusable, then use Shared Brain Memory rather than comments in Airtable.
  • Delivery: require receipts for external mutations, such as Airtable record IDs, Work Board task IDs, or API success responses.

Workflow

  1. Identify the direction: Airtable to Work Board, Work Board to Airtable, bidirectional sync, or one-time report.
  2. Confirm the table schema without printing secrets. Required fields usually include task title, body, status, assignee, priority, due date, source URL, and Work Board task ID.
  3. Map statuses explicitly. Prefer ready, working, review, done, and blocked on the HivemindOS side.
  4. For imports, create or update Work Board tasks idempotently using a stable Airtable record ID in source metadata.
  5. For exports, write only fields the user approved for Airtable. Do not leak private vault paths, local machine names, Tailnet URLs, raw logs, or secrets.
  6. Attach verification evidence before moving a mirrored record to review or done.
  7. Report both IDs: Work Board task ID and Airtable record ID.

Safety

  • Never run broad syncs until the user approves the table, field map, and direction.
  • Do not overwrite Airtable notes with local agent scratchpads.
  • Do not expose private Work Board details to Airtable if the table is shared outside the trusted team.
  • If conflicts appear, prefer a reconciliation report over silent last-write-wins updates.

Provenance

This is a HivemindOS-authored clean-room skill. It was prompted by a public Hyperagent skill catalog, but no unlicensed upstream text, JSON, or scripts are copied.

04 同仓库更多 Skills

LiamVisionary
LiamVisionary/hivemindos

tailscale-generation-skill-authoring

This skill should be used when the user asks to "create a Tailscale generation skill", "add a local generation skill", "document a generation endpoint", "add an image generation provider", "add a TTS provider", "add video generation", "add 3D generation", or needs guidance on where HivemindOS Tailscale or local generation providers belong in the shared skills shelf.

★ 13
LiamVisionary
LiamVisionary/hivemindos

localtts

This skill should be used when the user asks to "generate local TTS", "use local text to speech", "use remote TTS over Tailscale", "make speech audio", "add a TTS provider", "use Qwen3-TTS", or needs TTS endpoint setup through local or HivemindOS Tailscale routes.

★ 13
LiamVisionary
LiamVisionary/hivemindos

karpathy-guidelines

Behavioral guidelines to reduce common LLM coding mistakes. Use when writing, reviewing, or refactoring code to avoid overcomplication, make surgical changes, surface assumptions, and define verifiable success criteria.

★ 13
LiamVisionary
LiamVisionary/hivemindos

comfyui-image-generation

This skill should be used when the user asks to "generate images", "generate images with ComfyUI", "use local ComfyUI", "use remote ComfyUI", "use Z-Image", "add an image generation provider", or needs image-generation endpoint setup through local or HivemindOS Tailscale routes.

★ 13
LiamVisionary
LiamVisionary/hivemindos

wrangler

Cloudflare Workers CLI for deploying, developing, and managing Workers, KV, R2, D1, Vectorize, Hyperdrive, Workers AI, Containers, Queues, Workflows, Pipelines, and Secrets Store. Load before running wrangler commands to ensure correct syntax and best practices. Biases towards retrieval from Cloudflare docs over pre-trained knowledge.

★ 13
LiamVisionary
LiamVisionary/hivemindos

workers-best-practices

Reviews and authors Cloudflare Workers code against production best practices. Load when writing new Workers, reviewing Worker code, configuring wrangler.jsonc, or checking for common Workers anti-patterns (streaming, floating promises, global state, secrets, bindings, observability). Biases towards retrieval from Cloudflare docs over pre-trained knowledge.

★ 13