guidance

Fetches live backend reference data for icons, field types, and workflow node configuration via CLI.

Updated Jul 27, 2026
One-click install
npx skills add https://github.com/api-evangelist/frontline --skill guidance-api-evangelist
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: guidance
Source: https://github.com/api-evangelist/frontline/tree/main/skills/vendor/guidance
Command: npx skills add https://github.com/api-evangelist/frontline --skill guidance-api-evangelist

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Hard-coded lists of icon keys, colors, field types, and node types drift out of sync with what the API actually accepts, causing avoidable 400 errors. This Skill pulls authoritative reference data directly from the live backend so every value used in create/update calls is guaranteed current. ## Core Features & Use Cases - Icons & Colors: frontline guidance icons returns valid iconKeys, iconColors, optionColors, tagModes, and relationModes for objects, record types, and select options. - Field Type Reference: frontline guidance fields returns a markdown reference covering every creatable field type, its exact metadata shape, constraints, and best practices before running field create or field update. - Node Type Catalog: frontline guidance nodes lists every node type with validInFlow, validInAutomation, and allowsMultipleOutgoingHandles flags for building flow and automation graphs. - Per-Node Guidance: frontline guidance node <type> returns configuration guidance for a single node type such as TOOLS_AI or API. - Use Case: Before adding a CONDITIONAL_ROUTING node to a workflow, run frontline guidance nodes to confirm it is valid in that graph type, then frontline guidance node CONDITIONAL_ROUTING to learn how to configure its fields. ## Quick Start Ask the AI to run frontline guidance icons and use the returned values to set a valid emoji and icon color on a new object.

Frequently Asked Questions about guidance

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

FAQPage Schema
How do I find valid icon keys and colors for objects?▼

Run frontline guidance icons to get the live list of iconKeys, iconColors, and optionColors from the backend. Use an iconKey for the emoji field on objects and record types, and pass an iconColor name or hex value for icon_color.

How do I choose the right field type and metadata before creating a field?▼

Run frontline guidance fields --table to read the markdown reference covering every creatable field type, its exact metadata shape, and constraint rules. This prevents 400 errors from invalid type and metadata combinations in field create calls.

What is the difference between iconColors and optionColors?▼

iconColors apply to the icon_color field on objects, record types, and fields, while optionColors apply to the color on tag and select options. They are separate palettes and must not be mixed.

How do I know which node types are valid in a flow versus an automation?▼

Run frontline guidance nodes to see each node type with validInFlow and validInAutomation flags. A node with validInFlow false, such as DYNAMIC_TABLES, returns a 400 if added to a flow.

Why did adding a node to my flow return a 400 error?▼

The node type is likely not valid in that graph type, or the node exceeds its allowed outgoing edges. Check frontline guidance nodes for validInFlow, validInAutomation, and allowsMultipleOutgoingHandles before building the graph.

Can I get human-readable output instead of JSON from the guidance commands?▼

Yes, add the --table flag to any guidance command. For fields and node <type> this prints the raw markdown reference directly instead of a JSON-wrapped string.