datasource
v1.0.0Guide AI to build NocoBase data models — tables, fields, relations, and seed data
⭐ 0· 161·0 current·0 all-time
byliu xiansen@alexander-lq
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
Name/description (NocoBase data modeling) match the runtime instructions: creating tables via SQL, registering collections, syncing fields, upgrading interfaces, creating relations, and seeding data. There are no unrelated required binaries, env vars, or install steps.
Instruction Scope
Instructions stay within the domain of NocoBase modeling, but they explicitly direct execution of arbitrary SQL (nb_execute_sql) and automated API actions (nb_setup_collection, nb_sync_fields, etc.). Executing SQL is expected for this purpose but has high-impact (DB write) effects — the instructions appropriately warn about dependency ordering and system fields.
Install Mechanism
Instruction-only skill with no install spec or bundled code. This is the lowest-risk install model and is appropriate for a guidance/tool-invocation skill.
Credentials
The skill declares no required environment variables or credentials. The actions reference platform tools (nb_execute_sql, nb_setup_collection, etc.), which implies the agent/tooling provides DB/API access; asking for no extra secrets is proportionate to the stated purpose.
Persistence & Privilege
always:false and default autonomous invocation are set. The skill does not request permanent presence or system configuration changes. Note: autonomous invocation is normal for skills; combine with the SQL-execution capability it means the agent could run DB-modifying flows when permitted by platform tooling.
Assessment
This skill is coherent for building NocoBase models, but it instructs the agent to run SQL and call collection-management APIs — operations that modify your database and NocoBase metadata. Before installing or enabling it: 1) Confirm what credentials/connection the platform tools (nb_execute_sql, nb_setup_collection, etc.) will use and ensure they have only the necessary DB privileges; 2) Test the workflow in a staging DB and back up production before running batch SQL; 3) Review any generated SQL and list of collections/fields before execution; 4) Be aware that while the skill itself doesn't request secrets, granting the agent the platform tools that it invokes is effectively granting DB/API write access. If you need stricter control, require manual approval before running nb_execute_sql or limit the agent to the manual (per-collection) path.Like a lobster shell, security has layers — review code before you run it.
latestvk975jcbezmz277ggb62cnk83mh83322x
License
MIT-0
Free to use, modify, and redistribute. No attribution required.