acqai
v0.9.0Ask ACQ AI (Mozi) from Cowork or Claude Code with your own docs as the context: Claude writes the question, sends it through your own signed-in browser on your yes, refines the answer with follow-up questions, and brings the mechanics home with the edits they imply.
By Scott SoloLicense: MIT1 GitHub starsUpdated 2 hours ago
Directory evidence
- Runtimes
- Claude Code
- Parsed components
- 2 skill or MCP entries
- Source updated
- Oct 3, 2026
- Manifest status
- Canonical path parsed
The directory validates manifest shape and source location. It does not execute the plugin or provide a security endorsement. Review the indexing methodology →
Install acqai for Claude Code
claude plugin marketplace add IchenDEV/agent-plugin-mkt
claude plugin marketplace update agent-plugin-marketplace
claude plugin install acqai@agent-plugin-marketplacePaste and run these commands in a terminal with Claude Code. They add and refresh the PluginsMP catalog, then install this plugin.
The installer fetches third-party code from the source repository shown on this page. This directory validates manifest structure and source location, but does not perform a security audit; review the manifest, components, and source before installing.
Get the source manually
git clone https://github.com/scottsolowild/acqai-pluginClone the source repository, then follow its setup instructions to add the plugin to a compatible client. The plugin root is plugins/acqai/.
Plugin files
├── .claude-plugin/plugin.json├── skills/acq/SKILL.md└── .mcp.json
Included Skills1
Ask ACQ AI (Mozi) from Claude Code or Cowork with the person's own docs as the context: get ready first (sign in when the session is out; a question argument does not skip this), shape the question, show it, send it through the plugin's acqai tools on their yes, refine the answer with follow-up questions, and bring the mechanics home with the edits they imply. A bare "/acq" is the readiness check alone. Pass -y or --yes on /acq to treat that flag as the yes for the whole run: send without waiting in chat, then write the Adopt edits into files and record the outcome, with no further ask. Trigger on "/acq", "ask ACQ", "ask ACQ AI", "run this past ACQ", "what would ACQ say", "set up ACQ AI", "sign into ACQ AI", or a pasted ACQ AI reply to sort through.
MCP servers1
- command
- python3
- args
- ${CLAUDE_PLUGIN_ROOT}/scripts/acqai_mcp.py
MCP configuration uses runtime-provided plugin path placeholders such as ${PLUGIN_ROOT} or ${CLAUDE_PLUGIN_ROOT}. Review the manifest for the runtime-specific expansion rules.
Plugin manifests1
{
"$schema": "https://json.schemastore.org/claude-code-plugin-manifest.json",
"name": "acqai",
"displayName": "ACQ AI in Claude",
"version": "0.9.0",
"description": "Ask ACQ AI (Mozi) from Cowork or Claude Code with your own docs as the context: Claude writes the question, sends it through your own signed-in browser on your yes, refines the answer with follow-up questions, and brings the mechanics home with the edits they imply.",
"author": {
"name": "Scott Solo",
"url": "https://github.com/scottsolowild"
},
"homepage": "https://github.com/scottsolowild/acqai-plugin",
"repository": "https://github.com/scottsolowild/acqai-plugin",
"license": "MIT",
"keywords": [
"acq",
"acquisition.com",
"mozi",
"offers",
"workflow",
"cowork"
],
"userConfig": {
"mozi_company": {
"type": "string",
"title": "Your company on ACQ AI",
"description": "The company name ACQ AI shows on its sign-in list, when you belong to more than one. Claude passes it to the first sign-in, and it is saved for later runs. Leave it blank to click it yourself the first time, or set it later with: acqai.py setup --company \"Your Company\".",
"sensitive": false,
"required": false
}
}
}For maintainers
If you maintain this plugin, link to this source-backed listing from your README so users can review its manifest and indexed components.
[acqai on Agent Plugins Marketplace](https://pluginsmp.com/plugins/acqai)