@skene/database skills

Other Community

Skill notes

Setup flow

When a user wants to set up their database, follow these steps in order:

Step 1 — Ask what they're building

Present these presets and ask which one fits: Preset · What it includes CRM · contacts, companies, deals, pipeline stages, messaging, analytics Helpdesk · contacts, tickets, knowledge base, messaging, analytics Billing app · contacts, subscriptions, invoices, payments, orders, analytics

Step 1.5 — Set up AI tool configs (optional, for terminal users)

If the user is setting up from the terminal (not through an AI agent), suggest: This installs the package, detects AI coding tools in the project (Claude Code, Cursor, Windsurf, Copilot, Cline), and adds a reference to this skill in their configs. Future agent sessions will automatically discover the skill.

Step 2 — Find Supabase and apply the schema

Check your available tools for mcp__supabase__*. If you have Supabase MCP tools (preferred — zero config, no npm): Check what's already installed: mcp__supabase__list_tables({ schemas: ["public"] }) For each skill in dependency order, read its migration.sql from this package directory and apply it:

Step 3 — Show what they got (ALWAYS do this after applying schemas)

After the schema is applied, you MUST show the user their installed lifecycles. This is the confirmation that everything worked. Display a table like this, including only the lifecycles for the skills they installed: Lifecycle · Stages · Source skill Contact · lead → prospect → customer → partner · crm Deal · custom pipeline stages · pipeline Ticket · open → pending → resolved → closed · support

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
Other
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
94 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@SkeneTechnologies · MIT
Token usage
Lean
Setup complexity
Guided setup
External API key
Not required
Operating systems
macOS · Linux · Windows
Runtime requirements
No explicit requirements detected
Detected file/system behavior
  • Read-only
  • Write / modify
  • Shell exec
Network behavior
Local-only
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

01
Step 1 — Ask what they're building

Present these presets and ask which one fits: Preset · What it includes CRM · contacts, companies, deals, pipeline stages, messaging, analytics Helpdesk · contacts, tickets, knowledge base, messaging, analytics Billing app · contacts, subscriptions, invoices, payments, orders, analytics

02
Step 1.5 — Set up AI tool configs (optional, for terminal users)

If the user is setting up from the terminal (not through an AI agent), suggest: This installs the package, detects AI coding tools in the project (Claude Code, Cursor, Windsurf, Copilot, Cline), and adds a reference to this skill in their configs. Future agent sessions will automatically discover the skill.

03
Step 2 — Find Supabase and apply the schema

Check your available tools for `mcp__supabase__*`. If you have Supabase MCP tools (preferred — zero config, no npm): Check what's already installed: `mcp__supabase__list_tables({ schemas: ["public"] })` For each skill in dependency order, read its `migration.sql` from this package directory and apply it:

04
Step 3 — Show what they got (ALWAYS do this after applying schemas)

After the schema is applied, you MUST show the user their installed lifecycles. This is the confirmation that everything worked. Display a table like this, including only the lifecycles for the skills they installed: Lifecycle · Stages · Source skill Contact · lead → prospect → customer → partner · crm Deal · custom pipeline stages · pipeline Ticket · open → pending → resolved → closed · support

05
Step 4 — Next steps (ALWAYS show after the lifecycles)

After the lifecycle table, tell the user: Wire up Supabase Auth to auto-create users on signup (see the auth trigger at the bottom of this file) Visualize these lifecycles as a journey map → skene.ai

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.