Loading
Use when the user explicitly chooses iPollo Onto or starts an Onto workbench task. Build and maintain business systems directly in its connected tables, relationships and documents, saving useful resu
The skill file stays in the publisher's repository.
Paste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add Devin-AXIS/iPolloWork --skill ipollo-onto -a cursor -y
Use when the user explicitly chooses iPollo Onto or starts an Onto workbench task. Build and maintain business systems directly in its connected tables, relationships and documents, saving useful results progressively. A generic CRM, search or writing request alone does not activate this workflow.
Use when the user explicitly chooses iPollo Onto or starts an Onto workbench task. Build and maintain business systems directly in its connected tables, relationships and documents, saving useful results progressively. A generic CRM, search or writing request alone does not activate this workflow.
iPollo Onto is an independent business data workspace. All AI reasoning and model access belong to iPolloWork. Use the connected project's real MCP tools; this package does not run a database or configure a model provider.
workbench routing parameter when supported so the committed structure appears automatically. For a read-only question, stay read-only: do not create a project, table, document or research log automatically.records_import accepts structured rows directly: its legacy name does not require CSV, a finished list or a separate import phase. Do not call a write tool for every token or re-output the whole table in chat.record_update with the read version when refining an existing record that a person may be editing; resolve conflicts instead of silently overwriting.Read the chosen project's schema and reuse its customer records. Preview/apply only missing customer, contact, opportunity and activity structures and their relationships. Open the resulting customer table before searching all 100 prospects. Research using the host's available tools; save the first supported companies, continue in bounded batches, then enrich the same rows with contacts and follow-up information. Use returned record IDs for links. Read back the saved result before reporting the actual count and any gaps. Do not produce an intermediate spreadsheet unless asked.
ipollo-onto, UI resource workbench). Open right pane + → iPollo Onto, or Extensions → iPollo Onto → open app. Use the host's UI action discovery/control tools when available; do not substitute a browser URL or claim that a browser tab is the plugin workbench.ipollowork_workspace_app_list_tools (or its engine's equivalent). onto_status returns the connection, current relative route, conversation binding and optional workbench. onto_bind binds an existing project to this conversation. onto_navigate takes a relative href and confirms navigation after the UI acknowledges it. Use project/table MCP for data queries and writes.workbench follows the committed destination while following is enabled; use explicit navigation only when requested, or as a fallback for an older service whose tool schemas omit workbench. If the host exposes no UI control, state the exact manual entry above. Never invent a tool name or say a page opened without confirmation.business_catalog and follow its pagination; fetch query_context for the selected tables when field details are needed. Use data_context before schema changes. Older versions may expose only data_context / relation_graph; use the actual tool list. Tool names may be prefixed by the host. Use returned stable IDs and schemas, never guessed names or SQL.table_presets first and use table_preset_preview / table_preset_apply when available. These share the UI's recipes and return stable table and field IDs. Bind existing users/products with their actual table IDs and current versions; omitted order bindings create those tables along with orders. Each order links directly to one user and one product and stores quantity, unit price and total; no item table is created. Multi-product orders need a custom schema. Preserve existing multi-product orders and their item records. Never guess bindings from names alone. Use the same request ID and body for preview/apply/retry, and pass the current workbench when supported. These are editable schema presets, not an authentication, payment, price calculation or order workflow service; do not report such actions as implemented. Extra fields use field_create; custom structures still use the schema tools below.schema_preview before schema_apply. Inspect the actual preview, then apply within the user's authorized scope. Reuse the same request ID and body when retrying an uncertain idempotent operation. Do not duplicate a project after a timeout.field_create / field_update for existing tables; field_configure remains compatible for API fields. Preset fields follow the same rules as ordinary fields. Only the primary record-name field must keep its text type and cannot be deleted; its name is editable. Required fields are not deletion-locked. For an authorized deletion, read field_delete_preview, explain any paired relation fields or saved values affected, then use field_delete with its current tableVersion and relatedTableVersion. Resolve blockers through the user's intended change, never by silently removing dependent API fields, views, document references or automations. Read the resulting structure after changes.business_info after installing the independent business package. Bind roles to real field IDs and state meanings to existing options using business_bind with current table/binding versions. Bind users and products before orders. Optional roles can remain unmapped; do not add fields merely to satisfy optional mappings.business_call using the discovered action JSON Schema. Write actions require a stable UUID requestId; exact retries preserve all inputs and identity. Resolve 409 conflicts before proceeding. Use the chosen business action rather than bypassing amount/state checks with ordinary record edits.navigation.href at useful milestones. Do not store hidden reasoning or create permanent edges for each reasoning step. Explain the supporting records, missing evidence and uncertainty in the answer; persist a decision or document only when the task authorizes it.records_find (title prefix) or structured records_list filters; read record_get when evidence needs more detail. Call relation_explore with the required relationship IDs, table IDs, direction and depth. Start with one hop, expand up to three only when useful. The server defaults to 100 nodes and 200 edges and returns limited if a cap was reached. Search truncation is separate: follow catalog pages and narrow to a table when tablesLimited / hasMore is true.navigation.href replays the exact bounded query in the relations view. Pass it to the active workbench's onto_navigate when the user wants to see the graph. Without an active workbench, present it as an optional link against the user's real Onto address. The query reruns current data; observedAt is the read time, not proof that an external API value is fresh. The relations view must be enabled to display, while querying through MCP does not. Current project/table selection is shared with the host; selected record contents are not automatically sent to AI.relation_graph, explore one hop at a time and track visited IDs, with at most three hops and 100 nodes by default.records_list / record_get read saved values. Call records_refresh only when refreshing external values is part of the task; it can access external services and save a latest-value snapshot. Identify stale or failed values and distinguish missing information from zero.onto_status. binding is this conversation's default business project; workbench.id is only a UI routing identifier, never data authorization.onto_bind with its real project ID. If creating a new project through an available authorized project-create tool, bind immediately after creation. Never invent a project or create one merely to bind a read-only question. If a binding exists, reuse it; changing it requires the user to change the task scope. Browsing another project alone does not change the binding.workbench object returned by onto_status as an optional top-level parameter on Onto MCP/operation calls. Successful operations then reveal the real table, affected records, document or relation query in this conversation's workbench. Do not separately navigate after every write; this would override a user's paused-follow preference. Use onto_navigate only for an explicit navigation request or older service without following support.onto_status again. When no workbench is available, use the already authorized data scope normally and do not claim automatic visual following or automatic context injection into every Agent turn.dataTable references to embed live table data instead of copying a second dataset into prose.Complete with a concise result: what changed or was found, the supporting records, and any conflict, missing data, or remaining setup. Do not claim successful writes without a tool receipt and a verification read. Never include database passwords or API credentials in model context or output.
When the user chooses a questionnaire task, discover survey_get, survey_preview, and survey_save. If absent, check whether the Onto questionnaire view extension is enabled. Read actual field/page IDs and the current version before editing. Put rules in the questionnaire config, not in global field definitions. Use structured all/any groups and supported show/hide/require/optional/jump/jump-question actions, with optional additionalActions and otherwise branches; never generate executable scripts. Conditions refer to earlier questions, while page jumps may use answers on that page and question jumps may use their source answer. Conditions may select a matrix row, multiinput item, date range endpoint, count or ranking position through subject, or compare compatible earlier answers through compareTo. Global required fields cannot be hidden, skipped or made optional. Preserve unrelated questions, pages, settings and rules.
Preview the proposed config with relevant synthetic answer cases, including a match, a non-match, missing answers and changed earlier answers. Explain the returned trace and any errors; do not treat one successful scenario as proof of all possible paths. The preview tool writes neither configuration nor records. Save with the read version once the requested rules pass; a 409 requires rereading and resolving differences. Use survey_submit only when asked to save a real answer, never for rule testing.
For questionnaire analytics, discover survey_results and reuse its structured start / end (exclusive), timezone, source, device, region, ip, fieldId, crossFieldId, and bounded page inputs. It returns actual submissions, retained answers, visit sessions, session conversion, duration, IP counts, daily trends, metadata dimensions and question/cross statistics from the same service as the dashboard. Respect the metric denominators, multi-choice semantics and result caps. Missing historic telemetry remains unknown; a missing region lookup is not evidence of a respondent's location. Do not claim the deterministic dashboard summary is an AI-generated report or write analytical conclusions into records unless the user requests it.