SkillOps Plugin

SkillOps is an IntelliJ IDEA plugin that creates repository-scoped skills for Codex, Claude Code, and Gemini CLI. It generates platform-specific skill directories, keeps SKILL.md focused, and writes supporting references, scripts, and assets. Codex, Claude, and Gemini runs can also be reviewed with local run insights.

SkillOps works locally and does not upload project files, prompts, session logs, credentials, or analytics.

SkillOps also reports Codex sessions that did not invoke a skill. These appear under No skill, while the Run dropdown provides the timestamped history for each separate session.

Useful links

• Product requirements
  • Defines the user workflow, generated skill structure, and out-of-scope product behavior.
• Architecture
  • Documents package boundaries between IntelliJ integration, generation, insights, and presentation.
• Development and publishing runbook
  • Describes local verification, packaging, release, signing, and Marketplace publication steps.
• SkillOps on JetBrains Marketplace
  • Install the latest public release and view compatibility information.

How to install

Install SkillOps directly from JetBrains Marketplace using the IDE preferences:

IntelliJ IDEA
→ Settings/Preferences
→ Plugins
→ Marketplace
→ Search for "SkillOps"
→ Install

You can also open the public SkillOps Marketplace page.

How to use

Create a skill from the IntelliJ project view:

Tools
→ SkillOps
→ Codex, Claude, or Gemini
→ Create Skill

The plugin creates the selected platform's project skill directory (.agents/skills/ for Codex, .claude/skills/ for Claude, or .gemini/skills/ for Gemini). A Codex skill contains:

.agents/
  skills/
    <skill-name>/
      SKILL.md
      references/
        instructions.md
        validation.md
        examples.md
      scripts/
      assets/
      agents/
        openai.yaml

Review token usage and efficiency after a Codex run:

Tools
→ SkillOps
→ Codex
→ Show Run Insights

Claude Code has the same action under:

Tools
→ SkillOps
→ Claude
→ Show Run Insights

Gemini CLI run insights are available under:

Tools
→ SkillOps
→ Gemini
→ Show Run Insights

Open the IntelliJ Tools menu and follow the nested SkillOps and Codex menus:

Run insights scan recent Codex JSONL sessions from the configured Codex home and show token totals, input/output split, cached-token percentage, reasoning-token percentage, repository/search activity, rate-limit status, and session-size warnings. Skill runs are grouped by skill name; ordinary project sessions remain available under No skill, with separate timestamped history entries.

Claude run insights scan ~/.claude/projects (or the configured Claude home), aggregate distinct assistant-call usage, merge subagent transcripts into their parent session, and show input, output, cache-read, cache-creation, tool, and search metrics. Reasoning-token and rate-limit fields are omitted because normal Claude transcripts do not expose them.

Gemini run insights scan ~/.gemini/tmp/<project>/chats, use .project_root for exact repository matching, and show recorded total, input, output, cached, thought, and tool tokens together with structured tool/search activity. Gemini's activate_skill tool provides explicit skill attribution when present.

Questions and Feedback?

Use GitHub Issues for bugs, workflow problems, and feature requests.

When reporting a problem, include:

• IntelliJ IDEA version
• SkillOps version
• operating system
• steps to reproduce
• expected and actual behavior

Contributing

See CONTRIBUTING.md for the development workflow and pull-request checklist. Before contributing, read:

• AGENTS.md
• Product requirements
• Architecture

Keep pull requests focused. Include what changed, why it changed, and how it was verified.

How to build

./gradlew buildPlugin

Note that the above won't run tests and checks. To do that too, run:

./gradlew check buildPlugin

For the complete list of tasks, see:

./gradlew tasks

How to run UI tests

This project does not currently include UI integration tests.

Manual IDE verification is done with:

./gradlew runIde

Then verify:

Tools → SkillOps → Codex → Create Skill
Tools → SkillOps → Claude → Create Skill
Tools → SkillOps → Claude → Show Run Insights
Tools → SkillOps → Gemini → Create Skill
Tools → SkillOps → Gemini → Show Run Insights
Tools → SkillOps → Codex → Show Run Insights

How to develop in IntelliJ

Import the project as a Gradle project using JDK 21.

Whenever you change a Gradle setting, for example build.gradle.kts, settings.gradle.kts, or gradle.properties, refresh all Gradle projects from the Gradle toolbar.

To run an IntelliJ instance with the plugin installed:

./gradlew runIde

Plugin Verification

The project uses the IntelliJ Platform Gradle Plugin verification tasks. To run local verification:

./gradlew check
./gradlew verifyPlugin

Release

The first public release is 0.1.0. Release steps, signing requirements, and Marketplace publication notes are maintained in docs/development/RUNBOOK.md.

License

Licensed under the Apache License, Version 2.0.