Update to Effivity

{
  "description": "Interact with the Effivity compliance platform using its MCP tools. Use when users ask about Effivity form data, workflow masters, workflow-related forms, FAQ information, or support tickets.",
  "included_files": [
    {
      "relative_path": "references/tool-annotations.md",
      "size_in_bytes": 3695
    },
    {
      "relative_path": "references/tool-reference.md",
      "size_in_bytes": 2360
    },
    {
      "relative_path": "references/usage-guidelines.md",
      "size_in_bytes": 952
    }
  ],
  "name": "effivity-platform",
  "skill_md_contents": "---\nname: effivity-platform\ndescription: Interact with the Effivity compliance platform using its MCP tools. Use when users ask about Effivity form data, workflow masters, workflow-related forms, FAQ information, or support tickets.\n---\n\n# Effivity Platform\n\nUse the Effivity MCP tools only for operations supported by the Effivity platform.\n\n## Scope\n\nThis skill is limited to capabilities exposed by the Effivity MCP server. Do not infer capabilities that are not exposed by the available tools.\n\n## Tool Selection\n\n- `list_form_data` — retrieve existing form data.\n- `get_workflow_master` — retrieve workflow master information.\n- `list_workflow_masters` — list workflow master records.\n- `ask_faq` — answer questions using internal FAQ knowledge.\n- `get_workflow_forms` — retrieve workflow-related forms.\n- `create_support_ticket` — create a new support ticket.\n\n## Behavioral Rules\n\n- Use read-only tools only for retrieval and inspection.\n- Do not claim that a tool can create, update, or delete data unless its defined behavior explicitly supports that operation.\n- Do not claim that these tools provide arbitrary internet or external-system access.\n- Creating a support ticket is a write operation but is not destructive because it adds a new record rather than deleting or irreversibly altering existing data.\n- Do not claim that an existing ticket or record was modified unless the underlying tool actually performs that operation.\n\n## Detailed References\n\nSee [Tool Reference](references/tool-reference.md) for detailed tool behavior.\n\nSee [Tool Annotations](references/tool-annotations.md) for the reviewer-oriented annotation justifications.\n\nSee [Usage Guidelines](references/usage-guidelines.md) for detailed usage boundaries and expected behavior.\n"
}