{
  "markdown": "# Blog Post Pro Editor\n\nA repository containing custom editorial skills and commands for AI coding agents to improve the quality, tone, and correctness of technical blog posts and prose.\n\n## AI Agent Installation Guide: Skills & Custom Commands\n\nThis guide explains how to install, configure, and use the custom editorial skills and commands contained in this repository across various common coding agents and AI IDEs.\n\n---\n\n## 1. Gemini CLI / Antigravity CLI\n\nGemini CLI supports custom plugins and skills using the configuration directory structure.\n\n### Installing Skills\n\n1. Copy the skill directories from `/skills` into your Gemini config plugins directory (typically located at `~/.gemini/config/plugins/` or your project plugin directory).\n2. Ensure each skill folder contains a valid `SKILL.md` specifying the behavior constraints.\n\n### Installing Custom Commands\n\n1. Gemini CLI registers custom commands defined via TOML configuration files.\n2. Copy the command definitions from the `/commands` directory into your active project configuration folder or configuration mapping.\n\n---\n\n## 2. GitHub Copilot\n\nGitHub Copilot respects workspace-level instructions through a specialized markdown file.\n\n### Installing Custom Instructions\n\n1. Create a directory named `.github` in the root of your workspace if it doesn't already exist.\n2. Create or append to a file named `.github/copilot-instructions.md`.\n3. Include references to the editorial guidelines from `/skills` directly in `.github/copilot-instructions.md`. For example:\n\n   ```markdown\n   # Editorial Standards\n   Refer to the rules in the following workspace files to review and edit prose:\n   - [Active Voice Rules](./skills/active-voice-reviewer/SKILL.md)\n   - [Conciseness Rules](./skills/conciseness-reviewer/SKILL.md)\n   ```\n\n---\n\n## 3. Claude (Claude Desktop & Claude.ai Projects)\n\n### Claude.ai Projects (Web)\n\nIf you are using Claude.ai Pro/Team Projects:\n\n1. Open your project on Claude.ai.\n2. In the right panel, click **Set Custom Instructions**.\n3. Copy and paste the core prompt instructions from the relevant `SKILL.md` files (such as `active-voice-reviewer` or `technical-accuracy-reviewer`) directly into the project instructions text box.\n4. Upload the files in the `skills` and `commands` directories to the **Project Knowledge** section so Claude can reference them directly.\n\n### Claude Desktop (Local)\n\nFor Claude Desktop, you can configure custom MCP (Model Context Protocol) servers to expose skills or commands, or point it to workspace directories:\n\n1. Expose the directories containing instructions by adding directory path parameters to your workspace reader MCP server in `~/Library/Application Support/Claude/claude_desktop_config.json`.\n\n---\n\n## 4. Cursor / Kiro IDE\n\nMany modern AI-first IDEs (like Cursor and Kiro IDE) utilize workspace-level rule files.\n\n### Using `.cursorrules` (Cursor & Kiro IDE)\n\n1. Create a `.cursorrules` file in the root of your project.\n2. Add instructions pointing the agent to respect the workspace skills and configuration:\n\n   ```markdown\n   Always adhere to the specific review rules defined in the `./skills` directory before completing any writing, editing, or code-documenting tasks:\n   - Use `./skills/active-voice-reviewer/SKILL.md` to check writing style.\n   - Use `./skills/technical-accuracy-reviewer/SKILL.md` to ensure correct terminology.\n   ```\n\n3. For custom commands, list them in the `.cursorrules` under a `# Custom Workflows` section to instruct the agent on when to emulate them (e.g., executing the logic defined in `commands/blog-review.toml`).\n",
  "bytes": 3595,
  "sha": "392a06dc85b36b6c109f154fba829cb169c520608658b660fa046ec81912837f",
  "repo_slug": "railsstudent/blog-post-pro-editor",
  "fonte": "repo",
  "truncated": false,
  "api": "https://agentalog.com/api/listings/plg_railsstudent_blog_post_pro_editor_aff06e4a/readme"
}