القائمة
Step 1 of building a generic Falcon connector. Checks StackOne's provider index via MCP, detects CLI availability, and either pulls an existing connector base config or scaffolds a new one.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Step 4 of building a generic Falcon connector. Generates YAML action configurations for all confirmed actions using actionType custom, writes partial files per resource, and updates the main connector YAML with $ref links.
Step 2 of building a generic Falcon connector. Asks which authentication type the provider uses, generates the correct YAML auth block from patterns, and writes it into the connector config file.
Interactive wizard for building a generic Falcon connector. Guides builders through provider setup, authentication, action discovery (scoped or maximal), YAML config generation, validation, and live testing with cleanup. Auto-triggers when someone asks to build a new connector, add a new provider, or create a Falcon config.
Step 5 of building a generic Falcon connector. Validates the generated YAML config using the StackOne CLI (or a manual checklist if CLI is unavailable), interprets and fixes common errors, then confirms the connector is ready for live testing.
Step 2 of building a unified connector. Checks if the StackOne CLI is available, looks up whether the connector already exists in the StackOne index, and either pulls it down or scaffolds a new one based on auth type.
Step 4 of building a unified connector. Guides the builder through mapping provider API fields to their schema using fieldConfigs. Writes or updates the connector YAML partial files for each resource.
| name | setup-connector |
| description | Step 1 of building a generic Falcon connector. Checks StackOne's provider index via MCP, detects CLI availability, and either pulls an existing connector base config or scaffolds a new one. |
| invoke | setup-connector |
Step 1 of the generic connector build process.
Read .connector-build-session.json. If provider is already set:
"Resuming — provider already set to
{{provider}}. Run/configure-authto continue."
Ask:
"What provider are you building a connector for? (e.g.,
workday,bamboohr,rippling)"
Save as provider (lowercase, hyphenated).
map_provider_key("{{provider}}")
If a key is returned, save as provider_key in session.
get_provider_actions("{{provider_key}}")
If indexed actions exist:
"Found
{{provider}}in the StackOne index with {{N}} known actions. I'll use this as a reference."
If not found:
"
{{provider}}isn't indexed yet — we'll discover actions from scratch in Step 3."
npx @stackone/cli --version
Save cli_available: true or false to session.
If unavailable:
"StackOne CLI isn't available. I'll guide manual scaffolding instead."
If CLI available, first check if a pullable connector exists:
npx @stackone/cli list | grep -ix "{{provider}}"
Use -x for full-line matching to avoid false positives from substring or hyphenated-name matches. If found in the CLI list, pull it:
npx @stackone/cli pull {{provider}}
Verify connectors/{{provider}}/ was created. Save connector_exists: true.
Note: A provider may have indexed actions (from Step 2) but no pullable connector config. Always check the CLI list before attempting pull.
If not in index or scaffolding fresh:
npx @stackone/cli scaffold {{provider}}
Or if CLI unavailable, create connectors/{{provider}}/{{provider}}.connector.s1.yaml manually:
name: {{provider}}
version: "1.0"
authentication: {} # configured in next step
baseUrl: "" # set in next step
actions: []
Save connector_exists: false.
Save connector_path: "connectors/{{provider}}" to session.
"Setup complete. ✓ Connector at
connectors/{{provider}}/Next: configure authentication. Run
/configure-authto continue."
Update session_step to "configure-auth".