Devcodex Workspace logo

Devcodex Workspace

Organization
devcodex-labs
devcodex-workspace

Retired compatibility fixture for the former project-local Grok bridge; current workspace installs use grok/plugins/devcodex-workspace.

Overview

Publisherdevcodex-labs
Repositorydevcodex
Skill namedevcodex-workspace
Stars
433
Forks
44
Bundled files
Instructions only
LicenseAGPL-3.0
Links
  • 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.

  • Self-contained

    Everything the model needs lives in the instructions — no extra files to sync.

  • Open source

    Published by devcodex-labs on GitHub. Read the source before you install it.

Installation

Install the Devcodex Workspace 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/devcodex-labs/devcodex/tree/main/grok/skills/devcodex-workspace
  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/devcodex-labs/devcodex.git /tmp/devcodex
mkdir -p .claude/skills
cp -r /tmp/devcodex/grok/skills/devcodex-workspace .claude/skills/devcodex-workspace
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Devcodex Workspace 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 Devcodex Workspace 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 Devcodex Workspace 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.

DevCodex Workspace Resolver(retired compatibility fixture)

lifecycleStatus: retired-compatibility-fixture deploymentStatus: MUST NOT be deployed by current workspace descriptors

This file is retained only so historical packages and migration evidence remain readable. Current workspace-namespace installs use the workspace-owned plugin under grok/plugins/devcodex-workspace; child projects must not receive this Skill or a project bridge.

For forensic replay of an old project bridge, the historical resolver contract was:

  1. Preserve the semantic intent seed already formed from the user message and conversation continuity.
  2. Walk upward from the current project directory to the nearest unique parent containing .devcodex/layout.json whose mode is workspace-namespace. That parent is <workspace-root>. Do not search above the first valid marker.
  3. Read <workspace-root>/AGENTS.md as the controlling shared kernel. Treat the project bridge and this Skill only as discovery adapters; they must not override the shared kernel.
  4. Resolve the project namespace as the project-root path relative to <workspace-root>. Bind runtime state to <workspace-root>/.devcodex/<project-namespace>/; use <workspace-root>/.devcodex/workspace/ only for an explicitly workspace-wide task.
  5. Apply the kernel's intent-first context gate. Load only the parent Skill files selected by the final route from <workspace-root>/.agents/skills/<skill-id>/SKILL.md, then load only the Profile or memory sections named by the resulting context plan.
  6. Read <workspace-root>/.agents/devcodex/instructions.full.md only for the kernel's explicit fail-closed fallback conditions. Never use it as the normal startup path.
  7. Before substantive output, satisfy the parent kernel's visible entry-check contract and all applicable confirmation, validation, memory, report, and governance gates.

Fail closed when any of these are ambiguous or missing: workspace marker, shared kernel, project namespace, selected Skill, Profile source, or active-root binding. Report the precise missing path or conflicting candidates; do not invent or silently substitute rules.

Frequently asked questions

What does the Devcodex Workspace AI skill do?

Retired compatibility fixture for the former project-local Grok bridge; current workspace installs use grok/plugins/devcodex-workspace.

Why use Devcodex Workspace on TypingMind?

Because you install it once and use it with any model. Devcodex Workspace 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 Devcodex Workspace in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/devcodex-labs/devcodex/tree/main/grok/skills/devcodex-workspace. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Devcodex Workspace?

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 Devcodex Workspace?

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

Is the Devcodex Workspace AI skill free?

Yes. It is published on GitHub by devcodex-labs under the AGPL-3.0 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.

View all

Set up your own AI workspace now

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