Loading...
Loading...
Found 60 Skills
Gate 5: Data structures document - defines entities, relationships, and ownership before database technology selection. Large Track only.
Clean Architecture, Data Models, Tech Stack, Error Handling & Platform Channels
Design a FHIR R4 data model for a healthcare application by mapping clinical concepts to resources, terminology, and implementation-ready relationships.
Defines Steedos object data models using YAML. Objects represent database tables with fields, permissions, list views, and behaviors. Use this skill to create and configure objects, define fields, set up relationships, configure feature flags, and establish naming conventions. Modern format uses separate .field.yml, .listview.yml, .permission.yml, .button.yml files in subfolders.
Orchestrates the full journey from zero to a running Neo4j application. Executes 8 named stages in order: prerequisites → context → provision → model → load → explore → query → build. Each stage has its own reference file in references/ that the agent reads and follows when entering that stage. Supports both HITL and fully autonomous operation. Time budget: ≤15 min after DB is running (autonomous), ≤90 min total (HITL).
Overview of LookML field types (Dimension, Measure, Filter, Parameter) and the role of the `sql` parameter in each. Use this skill to choose the right field type for your data modeling needs.
Guide to using LookML sets for grouping fields, controlling visibility, and managing drill paths.
Deep dive into LookML includes, refinements (layering), and project structure best practices. Essential for mastering Looker's object-oriented capabilities.
Use this skill when you need to create or modify a LookML Model file (.model.lkml). This includes defining connections, includes, and configuring model-level settings.
Use this skill when you need to create or modify a LookML Explore. This includes defining the Explore, joins, access grants, and basic configuration.
Create and edit Omni Analytics semantic model definitions — views, topics, dimensions, measures, relationships, and query views — using YAML through the Omni CLI. Use this skill whenever someone wants to add a field, create a new dimension or measure, define a topic, set up joins between tables, modify the data model, build a new view, add a calculated field, create a relationship, edit YAML, work on a branch, promote model changes, or any variant of "model this data", "add this metric", "create a view for", or "set up a join between". Also use for migrating modeling patterns since Omni's YAML is conceptually similar to other semantic layer definitions.
Design and implement collaborative data schemas using the Jazz framework. Use this skill when building or working with Jazz apps to define data structures using CoValues. This skill focuses exclusively on schema definition and data modeling logic.