# Truto Integration Build Planner

> Plan Truto integration creation or improvement from provider docs using truto integrations build with dry-run, strict validation, source-tier control, resources filters, plan/report artifacts, description refresh, and no automatic apply. Use for AI-assisted integration build planning.

- Skill: `yuvraj3335/truto-integration-build-planner` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add yuvraj3335/truto-integration-build-planner`
- Raw SKILL.md: https://api.skillmd.com/api/skills/yuvraj3335/truto-integration-build-planner/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Docs & Writing
- Author: yuvraj3335 (https://skillmd.com/u/yuvraj3335)
- Updated: 2026-09-22
- Page: https://skillmd.com/skills/yuvraj3335/truto-integration-build-planner

---


# Truto Integration Build Planner

## Mission

Use the CLI's AI build pipeline as a proposal engine, not an autopilot. Produce reviewable plan/report artifacts and a clear apply decision.

## Inputs

Collect docs source, target slug, profile, create-vs-improve intent, resource allow-list, source-tier hint, companion docs, category/label/base URL overrides, and whether the goal is full build, descriptions-only, bad-description cleanup, or audit.

## Preflight

```bash
truto whoami -p "$PROFILE" -o json --no-color
truto integrations build "$DOC_SOURCE" "$SLUG" --lookup-only -p "$PROFILE" -o json --no-color
```

If the slug is new, skip `--lookup-only` and use dry-run creation with explicit `--label`, `--category`, and `--base-url` when known.

## Recommended Plans

Full review:

```bash
truto integrations build "$DOC_SOURCE" "$SLUG" --dry-run --strict --plan-out --report-out -p "$PROFILE"
```

Focused resource pass:

```bash
truto integrations build "$DOC_SOURCE" "$SLUG" --resources "$RESOURCES" --dry-run --strict --plan-out --report-out -p "$PROFILE"
```

Higher-quality method generation:

```bash
truto integrations build "$DOC_SOURCE" "$SLUG" --feedback-loop --max-iterations 3 --dry-run --strict --plan-out --report-out -p "$PROFILE"
```

Descriptions-only:

```bash
truto integrations build "$DOC_SOURCE" "$SLUG" --descriptions-only --dry-run --plan-out --report-out -p "$PROFILE"
```

Bad-description cleanup:

```bash
truto integrations build "$DOC_SOURCE" "$SLUG" --rewrite-bad-descriptions --dry-run --plan-out --report-out -p "$PROFILE"
```

## Source Control Choices

- Pin `--source-tier` when auto discovery is wrong: `openapi-only`, `openapi-viewer`, `postman`, `llms-full`, `llms-index`, `mdtrick`, `md-sibling`, `firecrawl`, `graphql-introspection`, `graphql-sdl`, or `graphql-doc`.
- Add `--companion-docs "$URL"` when specs lack auth, rate-limit, errors, webhooks, or lifecycle prose.
- Use `--no-firecrawl` when crawling is disallowed or a structured source is enough.
- Use cache refresh flags only when the source changed or cached output is suspect.

## Review Gate

Before recommending apply, verify:

- No strict validation failures.
- Auth/base URL/category are correct.
- Resource grouping and method names are sane.
- Pagination paths are supported by examples.
- Query/body schemas are useful but not bloated.
- Docs will land in documentation rows unless `--keep-inline-docs` is intentionally required.
- Suppressed changes and report warnings are understood.

## Apply Policy

Never use `--yes` unless the user explicitly asks to apply. To apply later, rerun the same command with `--yes` and without `--dry-run`. If applying, pair this with `$truto-safe-admin-operator`.