oic-builder

Plugin oic-builder from marketplace public-agent-plugins in marat-ak/PublicAgentPlugins. Commands read from the repo's manifest — 2 days ago.

Skills (16)

• adapter-invokes

  Use when creating or editing an adapter invoke (REST, FTP, ERP Cloud, DB, collocated, OCI-fn) — per-adapter wizard page notes to apply while driving the generic wizard, the edit-over-recreate rule, and downstream payload references.

• adapter-wizard

  Use for creating or editing ANY adapter endpoint (stagefile, REST, FTP, DB, ERP, collocated, OCI-fn) — the generic CAF wizard (oic_wizard_*) is THE path; the old recipe tools are removed. Echo-delta loop, hasEvent, file upload, SAMPLE FIDELITY LAW, child pages, resume, cancel, session model.

• author-map

  Use when authoring a map (XSLT) from stated requirements — discover target/source shapes, find a catalog precedent (oic_catalog_examples), write the body, save with source registration, and check it landed. The production map flow (porting from another integration is the port-map skill).

• compare

  Use when asked what CHANGED / what DIFFERS between two integrations or two versions of one integration (review a new version, audit a copy, explain a regression) — the load-both → summary → drill-by-ref ladder over the local archive cache, and how to explain the result in designer terms.

• discovery

  Use for capability questions about the tenant across three shapes (catalog first: oic_catalog_search, counts/lists/reports via oic_catalog_sql) — FIND ("which integrations read email / talk to service Y / use adapter X?"), IMPACT ("what breaks if this connection changes?"), DIRECTION ("do we read or

• fix-placement

  Use when a defect's cause is understood and you are choosing WHERE in the flow to fix it — BEFORE proposing or applying any fix. Derive the location from the flow's chain of obligations (what each step guarantees to the steps after it), never from where the error surfaced or where the edit is smalle

• maps

  Use for ANY map (XSLT / TRANSFORMER node) configuration, and before writing ANY activity content that carries namespace prefixes (assignments, conditions, for-each, throw, notification, logger, stitch, variables, wizard expression fields) — THE PREFIX SOURCE LAW (all activities), THE NAMESPACE LAW,

• port-map

  Use when porting a map body from another integration or an .iar export ("make map mX equal to the map from integration Y / this .xsl file") — the prefix remap algorithm. A learning/benchmark aid; the production flow is the author-map skill.

• projects

  Use when working with OIC projects or making a copy of an integration — listing projects and their integrations; CLONING an integration (oic_clone_integration — a new version of the same integration, or a new integration under a NEW code/name: "clone X as Y", "copy X to a new integration", "duplicat

• run-analysis

  Use when analyzing or debugging WHY an integration RUN behaved as it did — why it failed / where it errored / why a ForEach looped N times / which node was slow / what a node emitted — or the same question over MANY runs (the last N executions, which run did X, how a value differed across runs). Blu

• schedule-to-rest

  Use when a SCHEDULED integration must be started by a REST call instead of its schedule — the user chooses an eligible REST connection, oic_convert_schedule_to_rest replaces the schedule trigger with a minimal default REST trigger, then the agent configures that endpoint with the wizard.

• source-material

  Use when a task says "replicate X from integration Y" or you must read an existing integration's artifacts — .iar exports (schemas, filenames, samples via the oic_iar_* tools), oic_describe_activity, live read-only blueprints, and jca configs.

• stage-files

  Use when creating, editing, or debugging Stage File nodes — operations, schema samples (repeating + namespace rules), consuming a BI Publisher report's output (reportBytes), the payload-boundary field drop, the upstream-build pattern, write-request reads, and payload references. Create/edit goes thr

• structural-nodes

  Use when adding or editing structural blueprint nodes — labels, assignments, routers+routes, foreach, scope/TRY, catchall, stop, note, throw, notification, publisher, STITCH, and node MOVE — plus expression authoring (XPath 1.0 core, fn: prefix for 2.0) and placement gotchas.

• verification

  Use before claiming ANY build result is verified — the levels-of-evidence ladder, the round-trip verification protocol for new/changed recipes (snapshot, delete, rebuild, compare), and recipe trust status.

• workspace

  Use when opening, committing, unlocking, verifying, or releasing an OIC integration workspace — oic_open_integration (the one-call default open) / oic_open_workspace / oic_commit / oic_unlock / oic_verify / oic_release_workspace, the lock rule (read vs edit), read-only and concurrent opens, the lock

Hooks (1)

• PreCompact

  ${CLAUDE_PLUGIN_ROOT}/hooks/pre-compact.sh

Similar plugins