From altertable
Manages Altertable discovery approval workflow: lists/filter pending discoveries by status, reviews for accuracy/duplicates/actionability/timing, handles approve/reject states, processes user feedback.
npx claudepluginhub altertable-ai/skills --plugin altertableThis skill uses the workspace's default tool permissions.
To manage discoveries:
Guides Payload CMS config (payload.config.ts), collections, fields, hooks, access control, APIs. Debugs validation errors, security, relationships, queries, transactions, hook behavior.
Builds production-ready Apache Airflow DAGs with patterns for operators, sensors, testing, and deployment. For data pipelines, workflow orchestration, and batch jobs.
Share bugs, ideas, or general feedback.
To manage discoveries:
Use the Altertable MCP server to retrieve and act on discoveries:
Available statuses for filtering: pending, approved, rejected.
When you need to review a discovery, follow these steps in order:
For batch reviews, sort by priority first, then group by topic, and apply the same five-step check to each.
Discoveries flow through these states:
pending --> approved | rejected
| State | Description | Transitions |
|---|---|---|
pending | Awaiting review | approve → approved; reject → rejected |
approved | Approved | reject → rejected |
rejected | Rejected | approve → approved |
Both approve and reject are reversible: an approved discovery can later be rejected, and a rejected one can later be approved.
Feedback on a discovery has two fields: a reaction (approved or rejected) and an optional reason (free-text, max 1000 chars).
When processing feedback:
When feedback includes free-text comments, parse them for:
approved/rejected reaction alone carries little information; the reason text is where the actionable signal usually lives.