TypingMindTypingMindThe best frontend for AI
Ops Jdi logo

Ops Jdi

Organization
Lifecycle-Innovations-Limited
ops-jdi

OPS on-demand: This skill should be used when the user asks to "just do it", "install jdi", "keep going…

Overview

PublisherLifecycle-Innovations-Limited
Repositoryclaude-ops
Skill nameops-jdi
Stars
547
Forks
62
Bundled files
21
LicenseMIT
Links
Skill sourceRepositoryHomepage
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • 21 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

    Published by Lifecycle-Innovations-Limited on GitHub. Read the source before you install it.

Installation

Install the Ops Jdi AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/Lifecycle-Innovations-Limited/claude-ops/tree/main/claude-ops/skills/ops-jdi
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/Lifecycle-Innovations-Limited/claude-ops.git /tmp/claude-ops
mkdir -p .claude/skills
cp -r /tmp/claude-ops/claude-ops/skills/ops-jdi .claude/skills/ops-jdi
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Ops Jdi in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Ops Jdi on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Ops Jdi is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

OPS ► JDI — Just Do It

Load ops-rules before acting. Public repo (no personal data). Outbound: one draft → one approval → one send. If AskUserQuestion / Workflow are missing, follow Rule 10 in ops-rules (Hermes: numbered options / two-turn Telegram card; delegate_task).

Bundled Claude Code plugin (plugin/) that keeps an authorized task going until it is verified and delivered. It is opt-in: nothing here is registered in the ops hooks, so installing ops never adds a Stop gate by itself.

What it does

  • Native command hooks (SessionStart, UserPromptSubmit, PostToolUse, PostToolUseFailure, Stop) run plugin/hooks/bridge.py: a deterministic, model-free state machine. Every Stop costs zero model calls.
  • A contract (outcomes + definition of done) is accepted only with inspected evidence plus a delivery record that matches the real final message.
  • Pause/stop requests and approval waits always win. Failed tool calls become incidents; harmless ones (guard refusals, empty results, timeouts) are closed with waive-incident.
  • /just-do-it maintain diagnoses named Claude Code config files; maintain fix repairs only plugin-owned issues with backup, pre/post hashes and rollback. Anything outside the plugin folder is a proposal only. Security policy is never touched.
  • /just-do-it audit is an on-demand semantic check (one $.model.fork). It needs an interactive session; headless it returns nothing-to-fork at zero cost.

Full contract, state machine and known limitations: plugin/README.md.

Commands

ArgAction
status (default)claude plugin list entry for just-do-it@local-just-do-it
installbash ${CLAUDE_PLUGIN_ROOT}/skills/ops-jdi/install.sh install (copy owned files into a local marketplace, register it, then install the plugin at user scope; refuses an existing installation)
updatebash ${CLAUDE_PLUGIN_ROOT}/skills/ops-jdi/install.sh update (requires an owned, registered user installation; back up source, copy managed files, then update via the CLI; preserve unknown files and runtime)
uninstallbash ${CLAUDE_PLUGIN_ROOT}/skills/ops-jdi/install.sh uninstall (remove plugin and marketplace registrations; retain source, backups and runtime)
rollback BACKUPbash ${CLAUDE_PLUGIN_ROOT}/skills/ops-jdi/install.sh rollback "BACKUP" (restore managed source from a matching printed backup and update the installed plugin; refuse source conflicts and preserve current runtime)
testcd ${CLAUDE_PLUGIN_ROOT}/skills/ops-jdi/plugin && python3 -I -m unittest discover -s . -p 'test*.py'

Uninstall is not a full rollback: retained files and runtime remain. Rollback restores the previous managed source of an existing installation, not a complete historical filesystem or runtime snapshot. A first-install backup has no previous source tree and cannot be used with rollback.

maintain and audit are slash commands of the installed plugin (/just-do-it maintain, /just-do-it audit); tell the user to run them in their own session.

Rules

  1. Ask before install/update/uninstall/rollback: they change the user's installed plugins. Updates apply at the next session start or /reload-plugins.
  2. Never run plugin/smoke.py: it is a paid live test. Only with an explicit budget the user names.
  3. Never edit plugin/ and the installed copy in parallel; update the repo copy, then run install.sh update.
  4. Never weaken an acceptance gate or touch security policy to get green.

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Ops Jdi AI skill do?

OPS on-demand: This skill should be used when the user asks to "just do it", "install jdi", "keep going…

Why use Ops Jdi on TypingMind?

Because you install it once and use it with any model. Ops Jdi is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Ops Jdi in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/Lifecycle-Innovations-Limited/claude-ops/tree/main/claude-ops/skills/ops-jdi. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Ops Jdi?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Ops Jdi?

As many as you like. As long as a model supports skills, you can use Ops Jdi with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Ops Jdi AI skill free?

Yes. It is published on GitHub by Lifecycle-Innovations-Limited under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

Related AI Skills

View all
NousResearch logo

Stocks

NousResearch
OrganizationPopular

Stock quotes, history, search, compare, crypto via Yahoo.

53.5K
250.4K
1 files
View
NousResearch logo

Lambda Labs

NousResearch
OrganizationPopular

On-demand GPU cloud instances for ML training.

53.5K
250.4K
2 files
View
NousResearch logo

Modal

NousResearch
OrganizationPopular

Serverless GPU cloud for ML jobs and model APIs.

53.5K
250.4K
2 files
View
Shubhamsaboo logo

Advisor Orchestrator Worker

Shubhamsaboo
CommunityPopular

Use when a task is too large for one model pass, needs parallel research or generation across many subtasks (like researching a dozen competitors at once), or the user asks to orchestrate multiple…

20.4K
138.7K
4 files
View

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇