Add Nango function builder persona

[khaliqgant]

Summary

• Add the built-in nango-function-builder persona and sidecar AGENTS.md
• Wire intent nango-function-building through workload-router catalog, routing profile, schema, tests, and generated persona output
• Document the persona in repo and workload-router READMEs

Validation

• corepack pnpm --filter @agentworkforce/workload-router test

Notes

• corepack pnpm run check currently fails in the existing CLI package before this persona change, due missing/mismatched @agentworkforce/harness-kit exports and missing @relayburn/sdk types.
• Existing untracked .claude/ was left untouched.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: d37fc645-fb6a-4f95-beb5-1caeaac23a44

📥 Commits

Reviewing files that changed from the base of the PR and between 4d75260 and 98813dd.

⛔ Files ignored due to path filters (1)

• packages/workload-router/src/generated/personas.ts is excluded by !**/generated/**

📒 Files selected for processing (1)

• personas/nango-function-builder/AGENTS.md

---

📝 Walkthrough

Walkthrough

Adds a built-in persona "nango-function-builder" (persona spec + AGENTS.md), registers it in routing/schema and personaCatalog, updates generate/export wiring, expands tests for persona resolution, and updates README docs to list the new built-in personas.

Changes

Nango Function Builder Persona Addition

Layer / File(s)	Summary
Persona Definition & Guidance personas/nango-function-builder.json, personas/nango-function-builder/AGENTS.md	New persona config defines nango-function-building intent with best/best-value/minimum tiers, harness settings, and system prompts. AGENTS.md provides a checklist and local validation workflow for building Nango TypeScript actions/syncs.
Intent Routing Configuration packages/workload-router/routing-profiles/default.json, packages/workload-router/routing-profiles/schema.json	Adds nango-function-building to default.json with best-value tier and updates schema required intent keys and properties mapping.
Persona Registration & Wiring packages/workload-router/scripts/generate-personas.mjs, packages/workload-router/src/index.ts	Adds export map entry nango-function-builder → nangoFunctionBuilder, imports generated spec, extends BUILT_IN_PERSONA_INTENTS, and registers personaCatalog['nango-function-building'].
Test Coverage packages/workload-router/src/index.test.ts	Updates built-in persona ID expectations and adds tests asserting resolvePersona('nango-function-building') returns expected tier (best-value), harness (codex), skill (building-nango-functions-locally), agentsMdContent, and workspace network access.
Documentation README.md, packages/workload-router/README.md	Root and package READMEs updated to list persona-maker, persona-improver, and nango-function-builder as built-in internal personas and to clarify persona resolution/install guidance.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~25 minutes

Possibly related PRs

• AgentWorkforce/workforce#61: Also adds/registers built-in personas and updates workload-router wiring and tests.
• AgentWorkforce/workforce#46: Adds personas with AGENTS.md/agentsMd content and adjusts persona wiring and tests.
• AgentWorkforce/workforce#49: Related changes to personaCatalog/BUILT_IN_PERSONA_INTENTS and tests.

Poem

🐰 I hopped through specs and README lines,
Three personas now in tidy signs,
Nango builds with TypeScript cheer,
Checkpoints, dryruns, tests appear,
The workforce grows — a hop, no fears!

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%.	Write docstrings for the functions missing them to satisfy the coverage threshold.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title directly and clearly describes the main change: adding a new Nango function builder persona. It is concise, specific, and accurately reflects the primary objective of the changeset.
Description check	✅ Passed	The description provides relevant context about the changeset, detailing the addition of the persona, integration with workload-router systems, documentation updates, and validation steps.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch codex/nango-functions-persona

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[devin-ai-integration]

✅ Devin Review: No Issues Found

Devin Review analyzed this PR and found no potential bugs to report.

View in Devin Review to see 3 additional findings.

[khaliqgant]

Updated in 98813dd to make the Nango skill install behavior explicit:

• The persona now names the workload-router dry-run/session materializer command: npx -y skills add https://github.com/NangoHQ/skills --skill building-nango-functions-locally -y.
• It also includes the manual scratch-session equivalent requested here: npx skills add NangoHQ/skills -s building-nango-functions-locally.
• It keeps the repo convention that installers should not run against the repo root, and adds a reminder to discover Nango integrations/connections before choosing dryrun args.

Validation: corepack pnpm --filter @agentworkforce/workload-router test and git diff --check pass.

[willwashburn]

@khaliqgant I'm not sure this should be a built in workforce persona.

see https://github.com/AgentWorkforce/workforce/pull/43/changes for reference, but workforce has installable libraries we can leverage, this maybe is one? could be it's own package/repo as the nango set of personas?

[khaliqgant]

@khaliqgant I'm not sure this should be a built in workforce persona.

see https://github.com/AgentWorkforce/workforce/pull/43/changes for reference, but workforce has installable libraries we can leverage, this maybe is one? could be it's own package/repo as the nango set of personas?

I don't understand why not actually. This is a persona for building nango-integrations, in my mind a perfect use case for a persona with a specific set of skills and silo'ed directory. I'm misunderstanding personas, it seems?

[willwashburn]

@khaliqgant oh no it's a perfect persona I'm saying it shouldn't be in the workforce repo as a built in.

There are three different types of personas

• built-ins
• library
• repo

Built in's should be reserved for workforce related personas. A good example of a built in is the persona-builder. Related to personas directly, so everyone should have it when they install agentworkforce. This is probably a very small set of personas.

Library personas are generalized that can be extended to multiple code bases. This is where I see the nango personas. Can be used in many repos, sort of like a "super skill". You can install these with agentworkforce install [package-name]. A user could install those personas to their repo if they wanted their team to use them, or they install them to their home directory for personal use only. Uses the shadcn model of copy-and-own. An example at the library level is the agent-relay set of personas. https://github.com/AgentWorkforce/relay/tree/main/packages/personas

Then there is the repo persona that get installed to .agentworkforce/workforce/personas. This is where teams can codify personas specific to their codebase. Think very specific rules to how I want my specific codebase (or part of it) to work. Might extend a library persona with specific auth or conventions that are less common.

An example of this is one I just PR'd into the relay repo: AgentWorkforce/relay#839

I obviously need to write more docs about this, but lmk if that makes sense.

[khaliqgant]

@khaliqgant oh no it's a perfect persona I'm saying it shouldn't be in the workforce repo as a built in.

There are three different types of personas

• built-ins
• library
• repo

Built in's should be reserved for workforce related personas. A good example of a built in is the persona-builder. Related to personas directly, so everyone should have it when they install agentworkforce. This is probably a very small set of personas.

Library personas are generalized that can be extended to multiple code bases. This is where I see the nango personas. Can be used in many repos, sort of like a "super skill". You can install these with agentworkforce install [package-name]. A user could install those personas to their repo if they wanted their team to use them, or they install them to their home directory for personal use only. Uses the shadcn model of copy-and-own. An example at the library level is the agent-relay set of personas. https://github.com/AgentWorkforce/relay/tree/main/packages/personas

Then there is the repo persona that get installed to .agentworkforce/workforce/personas. This is where teams can codify personas specific to their codebase. Think very specific rules to how I want my specific codebase (or part of it) to work. Might extend a library persona with specific auth or conventions that are less common.

An example of this is one I just PR'd into the relay repo: AgentWorkforce/relay#839

I obviously need to write more docs about this, but lmk if that makes sense.

Ah yes, this makes perfect sense. Brilliant! (said with British accent)