cognitedata/builder-skills
25 skills22.9k installs100 starsGitHub
Install
npx skills add https://github.com/cognitedata/builder-skillsSkills in this repo
1Skill CreatorSkill Creator (as documented via the Post-hoc Analyzer role) is a meta agent skill for builders who treat SKILL.md files like products that need measurement. After a blind comparator picks a winner between two skill executions, this workflow reads the comparison JSON, both skills, and both transcripts to explain what the judge valued and where the loser fell short. It is aimed at Cognite-style builder teams and solo skill authors who run parallel agent runs and want qualitative root-cause notes—not just a score. The process emphasizes instruction specificity, tool usage patterns, example breadth, and edge cases, turning one-off wins into edits you can ship in the next skill revision. Use it in Build while crafting or refactoring skills, and again in Ship when you gate releases on regression comparisons. It pairs naturally with brainstorming and writing-plans when those skills exist in the same repo stack, but stands alone whenever you already have comparator artifacts on disk.1.4kinstalls2Code Qualitycode-quality is a Cognite Flows-focused review skill for solo builders and small teams who want an agent to behave like a disciplined reviewer instead of skimming diffs. The description mandates use whenever you care about maintainability—before a PR, after a feature lands, or when the user names code quality, clean code, linting, TypeScript strictness, DRY, or technical debt. Execution is ordered: automated lint and strict noEmit TypeScript first, then deeper passes for `any` elimination and structural smells across components and modules. It is opinionated about Flows conventions—pnpm scripts, injection patterns, and component sizing—so outputs are actionable for the same repo the agent can write to. Treat it as a pre-merge checklist companion: baseline tooling errors are non-negotiable, warnings get scrutiny, and narrative findings tie back to locations developers can open immediately. Pair it at the end of Build when a feature is “done” and again in Ship when you want merge confidence without a human reviewer on call.1kinstalls3DesignDesign (Cognite builder-skills) is an agent skill that turns Aura’s layout foundations into concrete page structure for solo and small-team builders shipping Cognite-style customer applications. It positions the agent as a layout implementer: Tailwind-based flex and grid, tokenized spacing, and sidebar patterns that match Storybook—not ad-hoc div soup. Builders should pull breakpoint, container query, column span, composition, sidebar-left, and card-grid stories from the linked Aura docs whenever they add or refactor screens. The skill does not replace brand exploration in idea phase; it enforces repeatable shells so multiple apps feel like one product family. Use when scaffolding dashboards, settings flows, or data-heavy views where deviating from approved patterns would break consistency audits.1kinstalls4Dependencies Auditdependencies-audit is a Fix-not-report workflow for Node-based Flows applications. When dependency drift, CVEs, deprecated packages, or license problems block a review, the skill starts by reading package.json—optionally scoped to a path you pass—and enumerating every production and dev dependency with pinned versions. It then walks npm metadata lookup and outdated package remediation, continuing through vulnerability and policy fixes implied by the full SKILL.md procedure. Allowed tools explicitly include Read, Glob, Grep, Shell, and Write so the agent can run node one-liners, audit commands, and patch manifests or lockfiles. The mandated output is review-packages.md, aligning with Cognite Flows app review gates. Solo builders shipping internal tools or customer-facing Flows apps benefit because one guided pass turns vague “fix dependencies” requests into concrete upgrades instead of a spreadsheet of warnings. Use it whenever audit output, Dependabot noise, or review checklists mention packages, CVEs, or licenses—not when you only need architecture brainstorming unrelated to package.json.1kinstalls5Integrate File ViewerThis is a React-based file viewer component that handles rendering multiple file formats like PDFs and images with built-in support for annotations and viewport optimization. Solo builders use it to quickly embed document viewing capabilities into their web applications without building file rendering from scratch. It matters because file viewing is a common feature requirement for SaaS products, content platforms, and applications that need to display user-uploaded or generated documents.1kinstalls6Integrate Todo Listintegrate-todo-list is a Cognite builder skill that gives solo developers copy-paste React primitives for a shared todo list: context provider, typed store, and row component with three lifecycle states. It targets Build → frontend when you want task visibility inside a dashboard or internal tool without designing list UX from zero. Status icons (pending, pulsing in-progress, completed) and activeForm copy for in-flight tasks make agent-generated UIs feel intentional rather than generic checkboxes. The skill is integration-shaped reference code—not a full PM methodology—so pair it with your own data fetching and persistence layer.1kinstalls7Reveal 3dreveal-3d is an agent skill that walks a solo builder through vendoring Cognite Reveal’s React integration into an application-local feature folder instead of importing from the skills path. It specifies where to copy files, which npm packages to install—including Three.js types for TypeScript—and how to compose the public API from `RevealProvider` through canvas and resource components. The bundle also exposes React Query–friendly hooks and types for CAD resources and viewer options, which matters when you are wiring plant or asset 3D models to instance data. Use it during product build when you already have a Cognite-backed data model and need a maintainable, app-owned 3D viewer layer rather than a one-off script.1kinstalls8Correctness And Error Handlingcorrectness-and-error-handling is a Cognite Flows-focused agent skill for solo builders and small teams who need reliability before users hit production data. It is invoked whenever you are fixing correctness and error-handling issues—not merely auditing them. The workflow starts by mapping data flows from entry points, shared hooks and contexts, and CDF SDK services, then asks what happens on failure, during load, and when lists are empty. Each step searches for problems and applies fixes directly; only unfixable issues get reported. That makes it a ship-phase hardening pass that still edits build artifacts. Use it after feature work when crashes, null access, missing error boundaries, or async cleanup bugs show up in Flows UIs tied to industrial data platforms. It pairs naturally with broader review skills but is narrower: runtime robustness and user-visible error states across the app tree you pass as $ARGUMENTS or the whole repo.1kinstalls9Integrate Atlas ChatIntegrate Atlas Chat is a Cognite builder skill that supplies the AtlasClient TypeScript integration layer for talking to Cognite AI agents from your application. Solo builders and small teams shipping on Cognite Data Fusion use it when they need dependable list/get/post chat flows instead of re-deriving URL shapes, API versions, and SSE parsing. The client is intentionally stateless: it wraps CogniteClient GET and POST routes under the project ai/agents namespace, handles byids lookup, and funnels chat payloads through one post method that branches on JSON versus event streams with optional streaming callbacks. Place it while you are building agent-facing features—dashboards, ops copilots, or field apps—not when you are only doing marketing or static docs. You should already have Cognite auth and project context configured in your app; this skill focuses on the chat transport contract and types, not full UI. After integration, you typically add session UX, tool routing, and error handling on top of the raw agent responses the client returns.1kinstalls10Setup Python ToolsSet Up Python Tools is a Cognite builder skill that adds client-side Python execution via Pyodide to Flows applications that already run Atlas chat. Solo builders and small teams use it when CDF-defined agents expose runPythonCode tools and the client must honor toolConfirmation and clientTool actions without brittle manual hook wiring. The skill installs Pyodide, sets up React hooks and loading UI, and connects pythonRuntime into useAtlasChat per library conventions. It assumes integrate-atlas-chat finished first so src/atlas-agent includes react.ts and TypeBox/Ajv peers. Allowed tooling includes read, edit, write, and bash for dependency and file work. On Prism it belongs on Build integrations as a phase-specific companion to Atlas agent stacks rather than a general Python tutorial.1kinstalls11Test CoverageTest Coverage Fix is an agent skill for Cognite Flows-style apps that treats missing coverage as a ship blocker. Solo builders invoke it when a gate fails or before submission: it confirms Vitest or Jest and v8 reporters, runs coverage, maps untested paths, and actively adds or reshapes tests for testability. The SKILL.md is explicit that reporting alone is out of scope—configuration, shell runs, and file writes are in scope. It fits indie teams shipping TypeScript/JavaScript services who need a repeatable path from sub-80% to passing without ad-hoc test sprawl. Use it in the ship phase whenever “fix coverage” or “coverage gate” appears, especially alongside CI that mirrors the same threshold.1kinstalls12Create Client Toolcreate-client-tool is a build-phase agent skill for Cognite Atlas apps that scaffolds client-side AtlasTools end to end. Solo builders adding capabilities to an embedded Atlas chat must use it instead of manually copying TypeBox schemas or hook code: the skill names the tool from your argument hint, implements execute() in the browser, and wires validation through the vendored atlas-agent React layer. It fits when the agent should fetch data, render UI, query local state, or trigger navigation on the user’s machine. Prerequisites are strict—integrate-atlas-chat must already be complete with @sinclair/typebox, ajv, and ajv-formats installed. The flow mirrors Atlas’s clientTool action: the model proposes a call, arguments validate, then your execute returns output and detail for the transcript.1kinstalls13SecuritySecurity is a Cognite builder-skills workflow for solo and indie developers shipping Flows applications who need agent-driven hardening instead of a static checklist PDF. The skill insists on sequential execution: map routes and auth gating, trace how CDF SDK and user input enter the app, then remediate issues in place with Read, Grep, Write, and Shell as needed. It is framed for moments when users ask for security fixes, hardening, or vulnerability work—skipping steps is explicitly out of scope. Frontend entry files and Vite dev configuration are first-class citizens because misconfigured proxies, headers, and dependency surfaces are common indie-ship failures. Treat it as a pre-ship gate whenever a feature handles credentials or external data, and as the primary tool when XSS or injection classes appear in conversation.1kinstalls14Use Topbaruse-topbar is an agent skill for solo builders standardizing app chrome with Cognite’s @aura/topbar shadcn registry component. It assumes you run the bundled interview first, then enforces a strict install path: detect the package manager, ensure components.json includes the @aura registry URL, and run pnpm dlx shadcn@latest add @aura/topbar—not plain npm install. The skill covers Tailwind dark-mode class configuration and dark-mode hook wiring so theme toggles work with the top bar. It is aimed at Next.js/React stacks already using shadcn and Tailwind, where a consistent header, navigation, and actions matter for SaaS dashboards or internal tools. Because installation is a hard gate, the workflow reduces drift from one-off custom headers and documents exactly what to fix when the registry add fails.1kinstalls15PerformancePerformance is a Cognite Builder Skills agent workflow for Flows apps that both diagnoses and repairs slowdowns instead of handing you a generic checklist. Solo and indie builders shipping React-based industrial or data-heavy UIs install it when interactions lag, tables choke on large asset lists, or CDF queries fan out without pagination. The skill opens with a hard rule: capture Lighthouse and React Profiler numbers on a production build before touching components, so every change has a defensible delta. It then walks the component tree from src/App.tsx, grep-driven pattern hunts for classic re-render triggers, and extends into query efficiency, list virtualization, debouncing, lazy loading, and bundle splitting. Triggers include explicit user language around optimize, re-render, bundle size, memory leak, and large lists. It pairs naturally with testing and review skills after fixes land, and assumes you can run pnpm build/preview locally.1kinstalls16Pull Changes Resolve ConflictsPull-changes-resolve-conflicts is a procedural agent skill for solo builders and small teams who must integrate upstream branches without silently discarding local work. It standardizes fetching and merging (or rebasing in scope), surfacing every conflict explicitly, and comparing sides using git diff, status, and stage-specific object views before proposing resolutions. The skill emphasizes presenting prioritized recommendations tied to chat and repository context, then waiting for explicit user direction before editing markers or completing the merge. That hard gate reduces the risk of wrong-side picks on shared codebases and Flows-style multi-contributor apps. It fits whenever triggers like pull main, merge origin, sync with main, UU status, or integrate feat branch appear—not as a one-off command cheat sheet but as a full merge ritual ending in a clear commit message that documents what was integrated and how conflicts were resolved.1kinstalls17Graph ViewerGraph Viewer is a Cognite builder-skills module that packages Reagraph-oriented defaults and TypeScript types so solo builders can render relationship graphs without reinventing theme tokens every sprint. It defines shared constants for node colors by type, icon resolution, path highlight green (#22c55e), label stroke, and edge opacity so agent-assisted UI work stays consistent across screens. Use it when you are wiring graph exploration into a SaaS console, agent tooling surface, or internal data product and need a single import surface for visual config rather than scattered magic numbers. The excerpt focuses on configuration primitives—not a full page scaffold—so you still own routing, data fetching, and layout. It pairs naturally with backend graph APIs and fits the Build → frontend phase for indie teams shipping graph-first features on a tight timeline.1kinstalls18Setup Flows Authsetup-flows-auth is an agent skill for solo and indie builders shipping React apps on Cognite Fusion. It runs when you migrate an existing React app to Flows or discover missing CDF authentication—symptoms include absent DuneAuthProvider, AppSdkAuthProvider, or connectToHostApp wiring. The skill reads app.json to choose the Classic Files API path versus the newer Apps API host flow, installs the correct @cognite packages, and patches src/main.tsx or index.tsx accordingly. If a valid provider tree is already present, it reports a no-op instead of duplicating config. That keeps agent sessions focused on one integration surface rather than guessing auth modes. Triggers align with migrate to Flows, Flows setup, Fusion iframe auth, and missing auth provider scenarios described in SKILL.md.1kinstalls19Dm Limits And Best Practicesdm-limits-and-best-practices is a Cognite builder reference skill that keeps solo developers from turning a straightforward CDF Data Modeling integration into a flaky client that trips 429s, deadlocks, or incomplete paginated reads. It tells agents to anchor on Cognite’s published limits page, treat apply/delete/query concurrency buckets separately, respect max page sizes on instances.list, and prefer batching plus a QueuedTaskRunner-style semaphore when fanning out parallel work—especially when transformations already consume much of the concurrency budget. Use it whenever you author or review code touching instances.search, instances.list, instances.query, or instances.upsert, or when error messages mention rate limits, cursors, or cdfTaskRunner. It is reference material, not a deployment skill: pair it with your tenant credentials policy and observability in Operate once traffic is live.1kinstalls20Migrate App To FlowsMigrate App to Flows is a Cognite builder skill that orchestrates the full jump from legacy Dune app hosting to Flows appsApi infrastructure for teams maintaining industrial data apps. The agent first audits app.json, package.json, Vite config, and optional manifest.json, prints a concise pass/fail summary, then applies only the missing changes—infra field, auth wiring via setup-flows-auth, manifest permissions, and CLI-based deploy scripts. It is intentionally sequential and idempotent: already-correct steps are skipped so reruns are safe during incremental PRs. Solo builders on Cognite stacks use it when product owners say migrate to Flows or move off Dune without hand-reading every platform doc. Intermediate familiarity with Cognite auth and deployment is assumed; it is not a generic Vercel migration helper.815installs21Integrate Fusion AgentIntegrate-fusion-agent is a builder skill for Cognite Fusion developers embedding the PAIA agent alongside Flows and Dune applications. Solo and small-team engineers use it when stakeholders expect an in-app copilot that can see selected assets and invoke app-defined actions instead of a disconnected chat window. The skill breaks integration into optional paths: surfacing the panel, pushing context on user events such as row selection, and registering an agent server that publishes state and callable tools. It insists on understanding the existing app entry and package manager before edits, which reduces broken installs in monorepos. Always prefer this skill over pasting partial snippets from forums, because Fusion’s host-app contract requires coordinated layout modes, message injection, and server registration. The result is an agent-aware industrial app that degrades cleanly when the panel is off or unavailable.813installs22Flows Code ReviewFlows Code Review is the technical certification step in Cognite’s Flows builder pipeline: after an app brief and implementation, it inventories source files, audits dependencies, and emits a scored report with Must Fix, Should Fix, and Nice Fix items. Solo and indie builders shipping Flows-compatible Node/TypeScript apps use it when they want a repeatable pre-submit gate instead of one-off agent opinions. The skill expects a git-backed project with package.json, creates or advances feedback-round folders under reviews/code-review/, and integrates explicitly with flows-app-brief upstream and flows-design-review plus flows-external-app-submit downstream. Re-run loops are first-class—you stay in code review until Must Fix count hits zero—so agents treat certification as a workflow, not a single pass. Tooling is read-heavy analysis plus writes for the three markdown deliverables.714installs23Flows Design Reviewflows-design-review is a semi-automated agent skill for Cognite Data Fusion Flows apps that implements the official design quality guidelines from docs.cognite.com. After flows-code-review reports zero Must Fix items, your agent runs concrete repository probes—grep patterns, lint, build—to propose draft scores on a 1–5 scale for each of ten questionnaire items, then pauses for you to confirm or override because navigation feel and clickability still demand a live walkthrough. The skill enforces automate-first, ask-second operating rules and persists a round-numbered markdown report under reviews/design-review with an overall average and ranked remediation list. Solo builders targeting external app certification use it to avoid shipping polished code with weak task UX. Successful rounds averaging at least 3.8 clear the path to invoke flows-external-app-submit. It is specialized to Flows on Cognite—not a generic UI audit for arbitrary web stacks.279installs24Flows External App Submitflows-external-app-submit is the final gate in Cognite's Flows app certification pipeline for builders shipping external Flows applications. It assumes you already completed flows-app-brief, implemented the app, and passed flows-code-review and flows-design-review with committed reports in predictable paths under reviews/. The skill verifies that App-Brief.md exists with required frontmatter, the latest code-review report shows zero open Must Fix items, and the latest design-review report meets the average score threshold, then invokes the Cognite CLI submit command. Solo and small-team builders use it when certification is the blocker between a polished repo and an external review queue—not when they still need to fix code or design findings. Because it is explicitly non-reviewing, it fits Prism's Ship launch shelf as a release-management workflow skill with hard preconditions rather than a generic deploy helper.278installs25Flows App BriefFlows App Brief is the opening skill in Cognite’s Flows app certification chain for builders shipping apps on Cognite. Run it immediately after `npx @cognite/cli apps create` when someone asks to start a brief, run the certification coach, or invoke flows-app-brief. The skill conducts a structured conversation—app name, value case, persona, problem, and design intent—and pushes back on hand-wavy answers like an examiner would. An optional preflight asks whether to pull the latest review skills from the CLI before questioning begins. The deliverable is a repo-root App-Brief.md that downstream build and flows-code-review / flows-design-review skills can trust. Solo and small-team builders benefit because the brief becomes the single source of truth before any UI or integration work lands.277installs