Jev Office Gate

CommunityPopular

Pluviobyte

jev-office-gate

Add a Jev-powered decision and release gate after an office assistant generates a report, proposal, spreadsheet, document, or slide deck. Use for claim-to-evidence checks, narrow requirement decisions, risk triage, and human-review routing; do not use it to generate the deliverable or claim that Jev browsed or verified a URL.

Overview

Publisher	Pluviobyte
Repository	`rnskill`
Skill name	`jev-office-gate`
Stars	1.6K
Forks	192
Bundled files	4
Links	Skill source Repository

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.
4 bundled files
Scripts, templates, and references the model can read while it works. Files are read-only and never executed.
Open source
Published by Pluviobyte on GitHub. Read the source before you install it.

Installation

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

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.

Open the app and go to Plugins → Skills.
Choose "Install from GitHub".
Paste the skill folder URL below and confirm.
https://github.com/Pluviobyte/rnskill/tree/main/skills/jev-office-gate
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.

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/Pluviobyte/rnskill.git /tmp/rnskill
mkdir -p .claude/skills
cp -r /tmp/rnskill/skills/jev-office-gate .claude/skills/jev-office-gate

Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Jev Office Gate 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 Jev Office Gate 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 Jev Office Gate 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.

Jev Office Gate

Use Jev as a narrow judgment layer after an office assistant has produced a deliverable. Keep the producing assistant and Jev separate unless an actual product integration is verified.

Workflow

Identify the deliverable and its release criteria. Preserve the user's requested format and office tool.
Extract bounded review items. For citation review, each item needs a claim and an excerpt copied from the source. A URL alone is not evidence.
Run deterministic checks outside Jev when relevant: file opens, links resolve, quoted text exists, dates and numbers match, formulas calculate, required sections exist, and document layout renders in the target application.
Use Jev only for narrow questions with predefined choices. Prefer claim support, evidence disposition, contradiction/overclaim risk, requirement coverage, or routing priority.
Apply explicit thresholds and route uncertain or consequential items to a human. Never treat model probability as calibrated truth without task-specific evaluation.
Return a release table with the original item, deterministic findings, Jev probabilities, decision, reasons, and required human action. Keep the original generated file unchanged unless the user asked for edits.

Citation gate

Use scripts/jev_office_gate.py for repeatable claim-to-evidence review. Read references/input-schema.md when preparing its JSON input.

Default review questions:

Does the supplied excerpt support the full claim?
Is the supplied source suitable as a formal citation, supporting context, unusable, or in need of manual review?
Does the supplied claim/excerpt pair show an obvious semantic conflict or overclaim risk?

The default thresholds are starting points: support below 0.70, risk above 0.60, disposition confidence below 0.50, or any disposition other than formal_source routes the item to review. A selected contradiction or cannot_use result becomes an automatic rejection only when its option probability is at least 0.80. Calibrate these values on representative examples before automating release.

Other office decisions

For requirement coverage, row classification, or routing, read references/decision-patterns.md. Keep the state small and the answer space fixed. Split compound decisions into separate questions.

Boundaries

Jev does not fetch pages, test URL reachability, authenticate a source, or know whether an excerpt was copied correctly.
Do not call it a fact checker. Report that it judged the supplied state and choices.
Use code for exact arithmetic, dates, identifiers, string matching, link checks, file integrity, and spreadsheet formulas.
Avoid asking one question to combine relevance, freshness, authority, and factual support. Split these dimensions or handle deterministic parts in code.
Treat company statements as self-disclosure, not independent verification.
For legal, medical, financial, compliance, or externally binding decisions, Jev may prioritize review but must not be the final approver.
If Jev is unavailable or credentials are absent, preserve the same review table and mark the judgment columns for human review. Do not pretend the API ran.

Credentials

The helper reads TYPESAFE_API_KEY by default and also accepts JEV_API_KEY. Never place an API key in a document, prompt, source file, or saved review artifact.

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 Jev Office Gate AI skill do?

Why use Jev Office Gate on TypingMind?

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

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/Pluviobyte/rnskill/tree/main/skills/jev-office-gate. 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 Jev Office Gate?

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 Jev Office Gate?

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

Is the Jev Office Gate AI skill free?

It is published on GitHub by Pluviobyte. Check the repository for licensing terms. 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

Diffs

openclaw

OrganizationPopular

Use the diffs tool to produce real, shareable diffs (viewer URL, file artifact, or both) instead of manual edit summaries.

Feishu Doc

Feishu document read/write workflows. Activate when the user mentions Feishu docs, cloud docs, or docx links.

Feishu Drive

Feishu cloud-storage and comment workflows. Activate when the user mentions cloud space, folders, Drive files, or document comments.

Feishu Wiki

Feishu knowledge-base navigation workflows. Activate when the user mentions a knowledge base, wiki, or wiki link.

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

Jev Office Gate

Workflow

Citation gate

Other office decisions

Boundaries

Credentials

Bundled files

Frequently asked questions

Related AI Skills

Set up your own AI workspace now