# Agent Skills Curated skills that teach AI coding agents how to use Luciq the way an experienced mobile engineer would. Skills are instruction sets your agent can follow when you ask it to set up, debug, or migrate Luciq in your project. They live alongside your project rules (in Cursor, Claude Code, Codex, or any agent that supports the [Agent Skills](https://agentskills.io) format) and activate automatically when the conversation matches. ## Skills vs MCP Server vs AI Coding Agent Integration These three pieces work together but solve different problems: | Surface | What it gives the agent | When to use | | ------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------ | --------------------------------------------------------------------------------------------------------- | | [**Luciq MCP Server**](/product-guides-and-integrations/product-guides/ai-features/luciq-mcp-server.md) | **Tools.** Read access to your crashes, hangs, bugs, occurrences, and reviews. | The agent needs production data to investigate issues or answer questions. | | [**AI Coding Agent Integration**](/getting-started/luciq-ai-integration.md) | **End-to-end SDK setup workflow.** Pinned dependency, init, invocation, masking, MCP wiring, smoke build. | The user is integrating Luciq for the first time, or onboarding a new platform. | | **Agent Skills** *(this page)* | **Methodology.** The investigation patterns, decision points, and pitfalls that turn raw MCP data into a real fix. | The agent has tools and data but you want it to investigate the way an experienced mobile engineer would. | Tools without methodology produces drive-by API calls. Methodology without tools is theory. You want all three. ## Available Skills | Skill | Use it when | | ---------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | [**`luciq-debug`**](/product-guides-and-integrations/product-guides/ai-features/agent-skills/luciq-debug.md) | Investigating a Luciq crash, hang, or user-reported bug end to end. The agent pulls the right MCP context, maps it to your local code, and proposes a fix grounded in evidence. | | [**`luciq-setup`**](/product-guides-and-integrations/product-guides/ai-features/agent-skills/luciq-setup.md) | Adding Luciq to a new project for the first time. *(Wraps the existing AI Coding Agent integration flow.)* | | [**`luciq-migrate`**](/product-guides-and-integrations/product-guides/ai-features/agent-skills/luciq-migrate.md) | Moving a project from the legacy Instabug SDK to Luciq, or upgrading between Luciq SDK versions. *(Wraps the existing migration hub.)* | ## Install Add the Luciq marketplace and install all three skills in one step: ``` /plugin marketplace add git@github.com:luciqai/agent-skills.git /plugin install luciq-skills@luciq.ai ``` Works in **Claude Code** and **Cursor**. The plugin install also wires up the [Luciq MCP server](/product-guides-and-integrations/product-guides/ai-features/luciq-mcp-server.md), so the skills have production data from day one. After install, the skills become available as `/luciq-skills:luciq-setup`, `/luciq-skills:luciq-debug`, and `/luciq-skills:luciq-migrate`. For other agents, install via npm: ```bash npx luciq-skills install # project-local (.claude/skills/) npx luciq-skills install --global # all projects (~/.claude/skills/) ``` Or copy the [`SKILL.md` files](https://github.com/luciqai/agent-skills/tree/main/plugins/luciq-skills/skills) directly from the public repo. The full SKILL.md is also reproduced on each skill page below. ## Prerequisites * A Luciq account and at least one app token. * An AI coding agent that supports the [Agent Skills](https://agentskills.io) format. Claude Code, Cursor, Codex, or any other compatible client. * For `luciq-debug`: the [Luciq MCP Server](/product-guides-and-integrations/product-guides/ai-features/luciq-mcp-server.md) configured and authenticated. The `luciq-setup` skill wires this for you. ## How a skill activates Skills declare *when* they apply via their description and triggering phrases. You don't `/run` them; you describe what you want, and the agent picks the right skill on its own. For example, asking the agent *"why is this iOS crash happening, Luciq says it's only on iOS 18"* activates `luciq-debug`. Asking *"add Luciq to this project"* activates `luciq-setup`. The agent reads the skill, follows its methodology, and pulls in MCP data when the skill calls for it. ## Contributing & feedback The skills are maintained in the public [`luciqai/agent-skills`](https://github.com/luciqai/agent-skills) repo and reviewed by our SDK leads before they ship. Spotted something inaccurate, or have a workflow you'd like a skill for? Open an issue on the repo or reach out to your Luciq contact. We're shipping skills as we validate them. The bar is high on purpose: skills feed into agents that write code in your repo, so accuracy beats coverage. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.luciq.ai/product-guides-and-integrations/product-guides/ai-features/agent-skills.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.