omnimind-ai/viavera/native-tool-builder

原生工具制作

Create a structured JSON tool package rendered by OmniBot's built-in SwiftUI components. Before authoring, read references/package-format.md relative to this skill. Use only its supported components, expressions and actions; never invent native capabilities or generate HTML/JavaScript/Swift as the runnable tool.

Workflow

1. Read the package format and the relevant example in assets/. Call native_tool_capabilities to discover the current operation catalog before using device capabilities; see references/capabilities.md for composition and lifetime rules. Discover installed tools with native_tool_list when editing. Use native_tool_read to retrieve the existing UUID, revision and package; it intentionally excludes the user's runtime data.
2. Write the complete JSON source into a descriptive workspace path with file_write. Keep personal sample data fictional. Use empty collections and safe initial values for new tools.
3. Call native_tool_validate on that path. Correct reported errors before installation.
4. Call native_tool_install when creating or updating the tool requested by the user. For updates, pass the existing tool_id and expected_revision; preserve state keys/types. Re-read after a revision conflict. Installation preserves user data and retains the previous package version.
5. Return the tool's actual openURL as a Markdown link, so the user can open the native tool in OmniBot. State the implemented behavior and any requested capability that is unavailable. Do not claim visual or device verification from JSON validation.

Build TOTP with ordinary components and invoke actions, as in assets/totp.json. There is no supported all-in-one totp UI component. Buttons, account lists, import/backup pages and action order are package JSON. Swift implements the shared capability catalog: camera/photo scanning, file selection, clipboard and the OTP/Keychain service. Any Agent-created package declaring the relevant capabilities can invoke them. The preinstalled TOTP is the same editable/deletable JSON example, with no privileged interface or tool ID.

Use sessionState and sessionBinding for host results, imported text and passwords. They are transient and never included in Agent reads or saved tool data. Never ask for OTP secrets or QR codes in chat, embed real credentials in source, or implement cryptography with expressions. The runtime may display redacted account metadata/current codes returned by otp.snapshot; the Agent cannot read them.

The runtime supports local data, bounded expressions, collection actions, page navigation, foreground countdowns and the catalog's native capability operations. Network requests, shell commands, background jobs, arbitrary scripts and APIs absent from the catalog are unavailable. Explain the boundary when a request needs one; build only the useful supported portion with the user's agreement on a materially reduced scope.

References and starting points

• references/package-format.md: exact schema, component properties, expression syntax, action semantics and update rules.
• assets/checklist.json: a persistent checklist with add, complete and delete actions.
• assets/calculator.json: a live unit converter using typed inputs and expressions.
• assets/countdown.json: a foreground timer based on the device clock.
• references/capabilities.md: invocation syntax, transient results, permissions and reusable native operations.
• assets/totp.json: TOTP assembled entirely from ordinary UI nodes and capability calls.
• assets/qr-reader.json: an independent tool reusing the same camera and clipboard capabilities.