
ae-metadata
AE metadata capability-gateway CLI: list, inspect, create, update, delete and download metadata data tables; bind an existing dimension table to a property or create and bind a CSV dimension table. Local file upload and event/property discovery are separate prerequisite capabilities.
- Installs
- 821
- Last 24h
- —
- Trending rank
- —
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/thinkingaiagenticengine/ae-cli --skill ae-metadata- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads ae-metadata automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
ae-metadata
CLI domain metadata routes to the analysis capability gateway (/api/cli/analysis/v1/...), using auth header cli-token.
Use this skill for gateway-backed data-table and property dimension-table operations.
Capability contract
- Responsibilities: data-table management and dimension-table bindings through the commands below.
- Inputs: verified project, table/property identifiers and operation-specific parameters; local CSV workflows need a valid uploaded input-file identifier and purpose.
- Outputs: table/binding operation results, resource identifiers, or download run/artifact status. A submitted asynchronous download is not yet a completed file.
- Boundaries: local input-file upload, event/property detail and discovery, metric CRUD, virtual metadata, batch metadata, project configuration and tracking plans are separate capabilities.
- Completion: the requested table or binding result is verified, or pending/blocked work and its remaining requirements are reported.
Cross-skill collaboration
When remaining work is outside this skill's scope, or a necessary prerequisite needs another capability, follow the collaboration protocol. Choose from the skills available in this run by capability, preserve verified context, and continue the remaining task. Reuse this protocol if already loaded.
Global AE CLI Rules
| Parameter | Description |
|---|---|
--format <json|table> | Output format. Default JSON. |
--jq <expr> | jq filter on JSON output. |
--host <url> | Override active AE host, e.g. ae-cli metadata data-table list --host <url> .... |
--validate | Optional: fix params only (/validate). Alone while iterating complex qp / payload — then run. Do not stack with --dry-run. |
--dry-run | Optional: confirm ready to run (/dry-run). Alone for risk/output preview. Do not stack with --validate. |
Output and errors:
- Success: JSON envelope (default). May include optional
_notice.host_compat. - Failure:
{ "ok": false, "error": { "type", "message", "hint" } }, non-zero exit. - CRITICAL — Host compat (do this first): After each
ae-clirun, check stderr and_notice.host_compat. If either is present, open the user reply with a short ⚠️ version warning and quote thenpm i -g/npx skills add(or update-cluster) lines verbatim, then present the business result. Soft tip;ok: truecan still carry the notice.
Safety:
- Read-only commands can run directly after IDs/names are verified.
- Ordinary writes (
data-table *-write,property-bindings-update, dimension-table bind/create) execute without--yes. Delete commands arehigh-risk-write: dry-run first, summarize impact, wait for explicit confirmation, then execute with--yes. - Before any command, read the matching
references/<name>.md(filename = command with spaces → underscores, e.g.metadata data-table list→metadata_data_table_list.md). - Never invent
project_id, event/property names,input_file_id, ordata_table_id. Reuse verified names or discover a metadata lookup capability; find data table IDs viametadata data-table list. metadata data-table downloadis an async artifact command: plain invocation submits,--waitwaits, and--output <file>waits then streams atomically. Resume withanalysis run wait; local interruption never cancels the remote run.- The member's natural-day quota counts every Gateway capability
executecall eligible for usage statistics (an identifiable user and statistics enabled), including metadata-only reads, previews, table/binding writes, asset exports, and downloads that submit work. It does not depend on database engine or business purpose. Cache hits, repeated calls, reused runs, and failures withinexecutecount, including schema errors, permission denials, and unknown capability IDs. Gateway capability discovery (list/inspect), validate/dry-run, and separate run-status/artifact-download HTTP endpoints do not count; pagination and cancellation through capability execution do count. OnQUERY_DAILY_LIMIT_EXCEEDED(HTTP 429), wait until reset or contact an administrator;QUERY_QUOTA_UNAVAILABLEfails explicitly. Do not switch identities to bypass these errors. Omit download--timeout-secondsto use the server default; inspect the selected capability for its current policy.
When to Use
Use this skill when the user needs:
- Metadata data-table list/get/create/update/delete/download
- For local uploads, first obtain an input-file identifier through an available upload capability with the required purpose, then continue the table operation.
- Bind an existing data table to a property, or create a CSV dimension table and bind it
For out-of-scope work, discover an available capability using the collaboration protocol.
Command Format
ae-cli metadata <resource> <action> [options]
ae-cli metadata property <dimension-table-action> [options]
- Commands and flags use kebab-case:
data-table,dimension-table,--project-id,--data-table-id. - Gateway
inputbody fields remain snake_case (project_id,event_name, …); ae-cli maps flags automatically.
PROJECT_ID_GATE
Reuse verified project context in one conversation; otherwise discover a project lookup capability to resolve project_id. Ask the user only when the returned projects leave a real ambiguity.
Commands (10)
| User command | Capability id | Reference |
|---|---|---|
metadata data-table list | metadata.data_table.list | metadata_data_table_list.md |
metadata data-table get | metadata.data_table.get | metadata_data_table_get.md |
metadata data-table csv-write | metadata.data_table.csv_write | metadata_data_table_csv_write.md |
metadata data-table sql-write | metadata.data_table.sql_write | metadata_data_table_sql_write.md |
metadata data-table csv-delete | metadata.data_table.csv_delete | metadata_data_table_csv_delete.md |
metadata data-table sql-delete | metadata.data_table.sql_delete | metadata_data_table_sql_delete.md |
metadata data-table download | metadata.data_table.download | metadata_data_table_download.md |
metadata data-table property-bindings-update | metadata.data_table.property_bindings_update | metadata_data_table_property_bindings_update.md |
metadata property bind-existing-dimension-table | metadata.property.bind_existing_dimension_table | metadata_property_dimension_table_bind_existing.md |
metadata property create-and-bind-csv-dimension-table | metadata.property.create_and_bind_csv_dimension_table | metadata_property_dimension_table_create_and_bind_csv.md |
Quick Verification
ae-cli metadata --help
ae-cli metadata data-table list --help
ae-cli metadata data-table list --project-id 1 --dry-run
ae-cli analysis input-file purpose list --project-id 1
FAQ
What does the ae-metadata skill do?
AE metadata capability-gateway CLI: list, inspect, create, update, delete and download metadata data tables; bind an existing dimension table to a property or create and bind a CSV dimension table. Local file upload and event/property discovery are separate prerequisite capabilities.
How do I install ae-metadata?
Run npx skills add https://github.com/thinkingaiagenticengine/ae-cli --skill ae-metadata in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/ae-metadata/ (personal) or .claude/skills/ae-metadata/ (project).
Which AI agents can use ae-metadata?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is ae-metadata safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains ae-metadata?
It is published by thinkingaiagenticengine in thinkingaiagenticengine/ae-cli. It has 821 recorded installs.
More from thinkingaiagenticengine/ae-cli
ae-analysis
thinkingaiagenticengine/ae-cli
Use ae-cli for AE analysis-side data questions, asset operations, and asset governance: reports, analysis boards, BI dashboards, ad-hoc models, drilldown, detail data, alerts, clusters, tags, metrics, metadata discovery, project configuration, tracking plans, local input-file upload, governance asset lists/rules/lineage/impact/dependency, batch asset operations, projects, and resource links. Use when the user asks to query data, explain a change, export evidence, inspect/create/update/govern analysis assets, recommend project assets for certification/authentication, review asset-certification recommendations, review metric recommendations, or build/update/refresh/sync a project semantic knowledge base from a governed asset package.
ae-engage
thinkingaiagenticengine/ae-cli
AE Engage capability gateway: config center, flows, push/config channels, strategies, templates, task management, operation activities, and query lifecycle. Trigger words: config center, scene config, push channel, config channel, operation strategy, operation task, operation activity, query lifecycle, template, config item, Engage, Hermes, engage-scene, engage-setting, engage-flow, engage-task, engage-activity, engage-query.
ae-dataops
thinkingaiagenticengine/ae-cli
Use ae-cli for DataOps warehouse tables/views and fields, recycling, workflow configuration and release, execution troubleshooting, backfill, SQL queries, and data integration.
ae-community
thinkingaiagenticengine/ae-cli
AE community analysis and data reporting for posts, comments, topics, livestreams, customer-service chats, WeCom after-sales groups, and in-game chat. Use for community content insight, sentiment, intent, evidence drill-down, community data ingestion/import/submission, and WeCom chat data integration (社区数据上报、导入、提交社区数据、企微聊天数据接入).
ae-agent
thinkingaiagenticengine/ae-cli
AE Agent platform CLI for Agent, resource package import and export, notification, approval, archived conversation, model, MCP, Skill, attachment, and user-memory work. Use when managing these resources, browsing Agent markets, handling approval requests and tasks, restoring archived conversations, persisting user memory, or answering from user preferences, background, stable workflows, or historical conventions.
ae-kb
thinkingaiagenticengine/ae-cli
AE knowledge base CLI manual for creating, importing read-only compiled snapshots, querying, LLM-powered ask, listing accessible knowledge bases and their sources, deterministic index/grep/read retrieval, checking status, ZIP source upload and directory management, raw child-file reading, revision-checked child updates and deletion, compiling, schema generation, URL sources, source deletion, ordinary text source creation, full reads and revision-checked editing, file/ZIP source draft replacement and restoration, and knowledge base deletion. Use when the user asks to manage AE (Agentic Engine) knowledge bases, import a compiled Markdown ZIP snapshot, upload documents or URLs to a knowledge base, query knowledge, ask knowledge bases with an LLM, list accessible knowledge bases or source metadata, inspect knowledge base indexes, search knowledge base pages, read a specific knowledge base page, check knowledge base status, generate schemas, compile knowledge, remove sources, create or edit
Popular data & databases skills
supabase-postgres-best-practices
supabase/agent-skills
Postgres best practices maintained by Supabase, for Postgres running anywhere. Load this skill BEFORE writing or changing anything that lives in a Postgres database: creating or altering tables and columns (including choosing column types), schema design, migrations and declarative schema files, RLS policies and the tests that verify them, indexes, triggers, database functions, queues and scheduled jobs (pgcron, pgmq), vector/semantic search (pgvector), and restoring dumps (pgrestore) or importing data. Also load it when diagnosing slow queries, high CPU, timeouts, EXPLAIN plans, connection exhaustion, locking, bloat, or rows visible to the wrong user or tenant. This is not just a performance guide — schema, migration, security, and SQL authoring tasks need these rules too, even for a one-column change or a single query.
prisma-client-api
prisma/skills
Prisma Client API reference covering model queries, filters, operators, and client methods. Use when writing database queries, using CRUD operations, filtering data, or configuring Prisma Client. Triggers on "prisma query", "findMany", "create", "update", "delete", "$transaction".
prisma-database-setup
prisma/skills
Deprecated compatibility name for prisma-orm-setup. Use only when a user or existing integration explicitly invokes prisma-database-setup; otherwise select prisma-orm-setup.
prisma-cli
prisma/skills
Prisma ORM 7 CLI reference for existing Prisma 7 applications or explicitly selected Prisma 7 workflows. Covers prisma init, generate, migrate, db, dev, studio, and mcp. For setup, connection repair, or Prisma 8, use prisma-orm-setup; not the Prisma Platform CLI.
prisma-postgres
prisma/skills
Deprecated compatibility name for prisma-postgres-setup. Use only when a user or existing integration explicitly invokes prisma-postgres; otherwise select prisma-postgres-setup.
prisma-driver-adapter-implementation
prisma/skills
Required reference for Prisma ORM 7 SQL driver adapter work. Use when implementing or modifying adapters, adding database drivers, or touching SqlDriverAdapter, Transaction, savepoint, result mapping, or DriverAdapterError behavior. Covers current transaction lifecycle, optional savepoint hooks, original database-error preservation, and verification.