skills.rest
gobifrost
gobifrostOFFICIAL
Explore all skills by this author →
GitHub

build

Build Bifrost automation artifacts across v1 and v2 workspace modes.

55|14|Updated Oct 12, 2025
Search Tags:#automation#agents#forms#workflows#tables#apps#bifrost
One-click install
npx skills add https://github.com/gobifrost/bifrost --skill build-gobifrost
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: build
Source: https://github.com/gobifrost/bifrost/tree/main/plugins/bifrost/skills/bifrost-build
Command: npx skills add https://github.com/gobifrost/bifrost --skill build-gobifrost

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Building automation on Bifrost requires navigating two distinct workspace paradigms—v1 global _repo and v2 Solution—each with different entity ownership models, CLI commands, and deployment workflows. Developers frequently encounter 409 conflicts from mutating deploy-owned entities, orphaned workflows from re-registering instead of replacing, and broken imports from mixing v1 and v2 SDK surfaces. This skill eliminates these failures by detecting the workspace mode, enforcing mode-specific guardrails, and routing users to the exact reference documentation needed for their context.

Core Features & Use Cases

  • Dual-Mode Workspace Detection: Automatically identifies whether the current directory is a Solution workspace (v2) or global _repo workspace (v1) and applies the correct entity lifecycle rules.
  • Entity Scaffolding with Access Control: Guides creation of workflows, forms, agents, apps, tables, and configs while enforcing org scoping, role-based access levels, and access-tuple consistency to prevent silent 403 errors.
  • MCP-Only Mode Operation: Supports building and modifying entities through MCP tools when no local source checkout is available, including cloud agent scenarios.
  • Use Case: An integration services developer can use this skill to scaffold a new customer onboarding solution, write Python workflows with proper decorators, configure role-restricted forms and agents, and deploy—all while the skill prevents common pitfalls like live-mutating deploy-owned records or using deprecated v1 import patterns in v2 apps.

Quick Start

Use this skill to build Bifrost workflows, forms, agents, and apps by first detecting your workspace mode and confirming the target organization and access level before creating any entities.

Frequently Asked Questions about build

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I scaffold Bifrost workflows without getting 409 conflicts on deploy-owned entities?▼

To scaffold Bifrost workflows without 409 conflicts, you need mode-aware entity lifecycle management that detects whether you are in a v1 global _repo or v2 Solution workspace and prevents mutating deploy-owned records. This skill applies those guardrails automatically.

Can I build Bifrost automation artifacts using MCP tools without a local source checkout?▼

Yes, you can build and modify Bifrost automation artifacts through MCP-only mode operation without local source checkouts. This skill supports cloud agent scenarios by routing developers to the correct reference documentation for MCP-only workflows.

How do I configure role-based access control for Bifrost forms and agents?▼

Configuring role-based access control for Bifrost forms and agents requires enforcing org scoping, access levels, and access-tuple consistency to prevent silent 403 errors. This skill guides entity creation while enforcing those access constraints.

What is the difference between v1 global _repo and v2 Solution workspace modes in Bifrost?▼

The difference between v1 global _repo and v2 Solution workspace modes lies in their entity ownership models, CLI commands, and deployment workflows. This skill detects the active mode and applies the correct lifecycle rules to prevent broken imports from mixing SDK surfaces.

Why do my Bifrost workflows become orphaned when re-registering entities?▼

Bifrost workflows become orphaned when re-registering entities instead of replacing them during updates. This skill eliminates this failure by enforcing mode-specific guardrails that ensure proper entity replacement and lifecycle management.

Does Bifrost integration service development require SDK-first workflows for v2 Solution apps?▼

Bifrost v2 Solution apps require avoiding deprecated v1 import patterns to prevent broken imports. This skill routes developers to the exact reference documentation needed for SDK-first or MCP-only workflows based on the detected workspace mode.

Related Skills

Explore More Software Engineering Skills→
greglambgreglamb
1

using-git-worktrees

Create an isolated Git worktree for feature development without disrupting the current workspace.

Community
Intermediate
sandgardenhqsandgardenhq
130

deployment

Deploy built artifacts with pre-deployment gates, rollback plans, and post-deployment health checks.

Official
Advanced
gobifrostgobifrost
55

migrate

Migrate legacy Bifrost v1 inline apps to standalone v2 Solutions.

Official
Advanced
tethertotetherto
395

setup

Execute predefined shell scripts to automate AI agent environment configuration.

Official
Basic