Agent skill

Brief Compliance Check

Check a LaTeX coursework submission against the requirements in a supplied PDF assessment brief.

Install Brief Compliance Check

skills CLI

$ npx skills add flonat/flonat-research --skill brief-compliance-check -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install flonat/flonat-research brief-compliance-check --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/flonat/flonat-research.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/brief-compliance-check .claude/skills/brief-compliance-check && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "brief-compliance-check" agent skill from https://github.com/flonat/flonat-research/tree/main/skills/brief-compliance-check into .claude/skills/brief-compliance-check/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "brief-compliance-check", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/flonat/flonat-research/tree/main/skills/brief-compliance-check

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add flonat/flonat-research --skill brief-compliance-check -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install flonat/flonat-research brief-compliance-check --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/flonat/flonat-research.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/brief-compliance-check .agents/skills/brief-compliance-check && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "brief-compliance-check" agent skill from https://github.com/flonat/flonat-research/tree/main/skills/brief-compliance-check into .agents/skills/brief-compliance-check/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "brief-compliance-check", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add flonat/flonat-research --skill brief-compliance-check -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install flonat/flonat-research brief-compliance-check --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/flonat/flonat-research.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/brief-compliance-check .cursor/skills/brief-compliance-check && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "brief-compliance-check" agent skill from https://github.com/flonat/flonat-research/tree/main/skills/brief-compliance-check into .cursor/skills/brief-compliance-check/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "brief-compliance-check", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/flonat/flonat-research.git --path skills/brief-compliance-check

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add flonat/flonat-research --skill brief-compliance-check -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install flonat/flonat-research brief-compliance-check --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/flonat/flonat-research.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/brief-compliance-check .gemini/skills/brief-compliance-check && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "brief-compliance-check" agent skill from https://github.com/flonat/flonat-research/tree/main/skills/brief-compliance-check into .gemini/skills/brief-compliance-check/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "brief-compliance-check", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install flonat/flonat-research brief-compliance-check

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add flonat/flonat-research --skill brief-compliance-check -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/flonat/flonat-research.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/brief-compliance-check .github/skills/brief-compliance-check && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "brief-compliance-check" agent skill from https://github.com/flonat/flonat-research/tree/main/skills/brief-compliance-check into .github/skills/brief-compliance-check/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "brief-compliance-check", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add flonat/flonat-research --skill brief-compliance-check -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install flonat/flonat-research brief-compliance-check --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/flonat/flonat-research.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/brief-compliance-check .opencode/skills/brief-compliance-check && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "brief-compliance-check" agent skill from https://github.com/flonat/flonat-research/tree/main/skills/brief-compliance-check into .opencode/skills/brief-compliance-check/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "brief-compliance-check", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: brief-compliance-check
GitHub stars: 146
Token cost: ~1.7k tokens
SKILL.md length: 472 words
Files: 1
Skills in repo: 83
Repo updated: Sep 29, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

Check a LaTeX coursework submission against the requirements in a supplied PDF assessment brief.

Works in 4 steps: Read the Brief → Check Word Counts → Check File Deliverables → …
Verifying format
SKILL.md covers Output Path, When to Use, Defaults and Protocol, plus 3 more sections
Calls bash

What it does

Brief Compliance Check is an agent skill from flonat/flonat-research. Check a LaTeX coursework submission against the requirements in a supplied PDF assessment brief. Use when verifying format, required sections, word limits, or deliverables before submission. Not for general prose proofreading; use $proofread.

Its SKILL.md is about 1.7k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Documents & Office, covering Regulatory compliance, Copy editing and proofreading and LaTeX. It works with LaTeX. The repository describes itself as: Shareable Claude Code + Codex infrastructure for PhD researchers — skills, agents, hooks, and rules for academic workflows. The licence is MIT.

When your agent uses it

Verifying format
Required sections
Deliverables before submission

Example prompts

“/brief-compliance-check”

Requirements

Python 3
Pre-approved tools (allowed-tools): Read, Glob, Bash(uv:*), Bash(ls*)

Workflow steps

4 steps, taken from the step headings in SKILL.md.

Read the Brief
Check Word Counts
Check File Deliverables
Report

What it can do on your machine

Read from SKILL.md and the folder at commit da27600. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves these tools, so the agent can use them without asking each time:
- Read
- Glob
- Bash(uv:*)
- Bash(ls*)
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
- bash
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Brief Compliance Check loads about 1.7k tokens when it runs. Until then it costs about 66 tokens; SKILL.md has 472 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~66
When it runs · the whole SKILL.md, loaded when a task matches: ~1.7k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from flonat/flonat-research at commit da27600, republished under its MIT licence (© flonat). 472 words, ~1,736 tokens.

Download SKILL.mdSave it as .claude/skills/brief-compliance-check/SKILL.md (or your agent's skills folder).

name: brief-compliance-check
description: Check a LaTeX coursework submission against the requirements in a supplied PDF assessment brief. Use when verifying format, required sections, word limits, or deliverables before submission. Not for general prose proofreading; use $proofread.
allowed-tools: Read, Glob, Bash(uv:*), Bash(ls*)

Brief Compliance Check

Given a PDF brief and a LaTeX submission, report exactly what is met, missing, or over-limit. Report-only — never modifies files.

Output Path

Per rules/review-artefact-routing.md (auto-loads in research projects (path-scoped to paper-*/ and paper/)):

Source slug: brief-compliance-check
Write reports to: reviews/<paper-slug>/brief-compliance-check/<YYYY-MM-DD-HHMM>.md inside the project, where <paper-slug> is the paper directory name (e.g., paper-jtp, paper-philtech). Path is relative to the research project root, not the Task-Management repo.
Never at project root (./CRITIC-REPORT.md-style filenames are forbidden — pre-rule layout).
Idempotency: if today's file exists, append a same-day descriptor ({date}-revision.md, {date}-r2.md, {date}-pre-submission.md) — never overwrite.
Index update: if reviews/INDEX.md exists, write a one-line entry under "Latest per source" pointing at the new file. Otherwise review-recap will rebuild the index next time it runs.
Infrastructure repos (Task-Management, atlas-workspace, etc.): this section does not apply — the path-scoped rule won't load there.

When to Use

"Do we meet the requirements of the brief?"
"Check my submission before I submit"
Any coursework or report with per-task deliverables and word limits
Argument: [brief.pdf] [submission/] or auto-detect from context

Defaults

Setting	Default
Brief path	Prompt if not found automatically
Submission dir	CWD or `submission/` subdirectory
LaTeX file	`main.tex` in submission dir
Word counting	Strips `lstlisting`, `tikzpicture`, `tabular`/`tabularx`, LaTeX commands

Protocol

Step 1: Read the Brief

Read the full brief PDF. Extract for each task/section:

Deliverables — what files or content must be present
Word limits — any "maximum N words" constraints
Required files — non-LaTeX files (YAML specs, workflow files, code, etc.)
Total marks — note the rubric criteria for context

Present a one-paragraph summary: how many tasks, total marks, submission format.

Step 2: Check Word Counts

For any task with a word limit, count words in the corresponding LaTeX section using this script:

python

import re

with open('main.tex', 'r') as f:
    tex = f.read()

# Map section headings to task labels and limits
# (fill from brief before running)
sections = {
    'Task X': (r'\section{Heading}', r'\section{Next Heading}', limit),
}

for task, (start, end, limit) in sections.items():
    s = tex.find(start)
    e = tex.find(end) if end else len(tex)
    chunk = tex[s:e]
    # Strip non-prose environments
    chunk = re.sub(r'\\begin\{lstlisting\}.*?\\end\{lstlisting\}', '', chunk, flags=re.DOTALL)
    chunk = re.sub(r'\\begin\{tikzpicture\}.*?\\end\{tikzpicture\}', '', chunk, flags=re.DOTALL)
    chunk = re.sub(r'\\begin\{tabular[x]?\}.*?\\end\{tabular[x]?\}', '', chunk, flags=re.DOTALL)
    # Strip LaTeX commands but keep their text arguments
    chunk = re.sub(r'\\[a-zA-Z]+\*?\{([^}]*)\}', r' \1 ', chunk)
    chunk = re.sub(r'\\[a-zA-Z]+\*?', ' ', chunk)
    chunk = re.sub(r'[{}\$~^%]', ' ', chunk)
    count = len(chunk.split())
    status = 'OK' if count <= limit else f'OVER by {count - limit}'
    print(f'{task}: ~{count} words (limit {limit}) [{status}]')

Adapt section headings and limits from the brief before running.

Show full SKILL.md (181 more words)Show less

Step 3: Check File Deliverables

For each required non-LaTeX file, verify existence:

bash

ls submission/          # check submitted PDF and LaTeX
ls openapi/             # check YAML specs if required
ls .github/workflows/   # check CI workflow if required
ls services/*/          # check service implementations if required

Report each as ✅ present / ❌ missing.

Step 4: Report

Produce a compliance table per task. Then summarise overall status.

Output Format

## Brief Compliance Report — [Module/Assessment Name]

### Overview
[1-para summary: N tasks, N marks, submission format]

### Per-Task Compliance

| Task | Requirement | Status |
|------|-------------|--------|
| A    | Architecture diagram | ✅ |
| A    | Written explanation ≤600 words | ✅ ~540 words |
| B    | Security requirements ≤800 words | ✅ ~416 words |
| C    | Five OpenAPI YAML files | ✅ |
| C    | Linting output in PDF | ✅ |
| D    | Test logs | ✅ |
| D    | Written analysis ≤600 words | ❌ ~764 words (OVER by 164) |
| E    | GitHub Actions workflow file | ✅ |
| F    | Reflection ≤700 words | ✅ ~645 words |

### File Deliverables

| File/Directory | Required | Status |
|----------------|----------|--------|
| main.pdf | Yes | ✅ |
| openapi/*.yaml (5 files) | Yes | ✅ |
| .github/workflows/ci.yml | Yes | ✅ |
| services/*/Dockerfile (5) | Yes | ✅ |

### Summary

- ✅ N requirements met
- ❌ N gaps or violations
- ⚠️ N warnings (approaching limit, optional items)

[Action items for any ❌ or ⚠️]

Never Do These

Never modify the submission to fix issues — report only
Never count words from lstlisting, tikzpicture, or table body content — these are not prose
Never guess word limits — read them from the brief before counting
Never report "approximately compliant" — every requirement is either met or not
Never skip file existence checks — a missing deliverable is a hard gap

Log to REVIEW-STATE.md (final step)

Write the brief-compliance report to reviews/<paper-slug>/brief-compliance-check/<YYYY-MM-DD-HHMM>.md (where <paper-slug> is extracted from the paper directory, e.g. paper-jtp; create mkdir -p reviews/<paper-slug>/brief-compliance-check/ first). Then append a row to the project's REVIEW-STATE.md:

bash

bash <skills-root>/_shared/review-state-log.sh \
  --check brief-compliance-check \
  --paper "<paper-{venue} dir>" \
  --verdict "<PASS|PARTIAL|FAIL>" \
  --score "<met-count>/<total-criteria>" \
  --open-issues "<gap-count>/<total-criteria>" \
  --report "reviews/<paper-slug>/brief-compliance-check/<YYYY-MM-DD-HHMM>.md" \
  --notes "<one-line: e.g. 'over word limit by 250; missing appendix C'>" \
  [--trigger "pre-submission-report|review-cluster"]

Verdict: PASS if every criterion met; PARTIAL if some met; FAIL if any hard gap (missing deliverable, over hard word limit).
Score: criteria met / total criteria (e.g. 8/10).
Open issues: total gaps at run time / total criteria.
Trigger: pass orchestrator name only if invoked as a sub-agent. Otherwise omit.

Schema: the installed shared resource shared/review-state-schema.md.

Files

Just SKILL.md in skills/brief-compliance-check of flonat/flonat-research.

Open the folder on GitHubat commit da27600

Compare with similar skills

Brief Compliance Check next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Brief Compliance Check compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Brief Compliance Check this skillflonat/flonat-research	146	—	~1.7k	Automated safety check: Pass	MIT	11 days ago
Paper2patent7toCR/paper2patent	654	—	~2.5k	Automated safety check: Pass	MIT	yesterday
PaperjurySpark-To-Paper-Skills/paperjury-codex	223	—	~4.4k	Automated safety check: Pass	MIT	2 mo ago
Review RevisionM1n-n9/paper-lifecycle	693	—	~2.3k	Automated safety check: Pass	None	3 mo ago
Evidence Ledgerwanshuiyin/Anti-Autoresearch	160	—	~11k	Automated safety check: Notes	MIT	4 days ago
PDFzai-org/ZCode	7.7k	—	~18k	Automated safety check: Notes	Proprietary	yesterday

Similar skills

Paper2patent
7toCR/paper2patent
Turn an academic paper (PDF, LaTeX, pasted text, thesis chapter or technical disclosure) into a Chinese invention patent application draft — 说明书摘要、摘要附图、权利要求书、说明书、说明书附图 — delivered as DOCX/PDF with…
654 GitHub stars~2.5k tokensUpdated yesterday
Documents & OfficeAuto-check passed
Paperjury
Spark-To-Paper-Skills/paperjury-codex
Pre-submission CS-conference LaTeX paper editing and adversarial review.
223 GitHub stars~4.4k tokensUpdated 2 mo ago
Documents & OfficeAuto-check passed
Review Revision
M1n-n9/paper-lifecycle
Review and revise academic papers with a senior-reviewer workflow.
693 GitHub stars~2.3k tokensUpdated 3 mo ago
Documents & OfficeAuto-check passed
Evidence Ledger
wanshuiyin/Anti-Autoresearch
Build the deterministic evidence ledger (artifactmanifest.json + claims.json) that every other Anti-Autoresearch auditor reads.
160 GitHub stars~11k tokensUpdated 4 days ago
Documents & OfficeAuto-check: notes
PDF
zai-org/ZCode
Professional PDF toolkit covering four production workflows: reports, creative visuals, academic LaTeX, and existing PDF processing.
7.7k GitHub stars~18k tokensUpdated yesterday
Documents & OfficeAuto-check: notes
Beamer
Noi1r/beamer-skill
Beamer LaTeX slide workflow: create, compile, review, and polish academic presentations.
364 GitHub stars~13k tokensUpdated 2 mo ago
Documents & OfficeAuto-check: notes

More from flonat/flonat-research

All 83 skills in this repo

Latex Posters
flonat/flonat-research
Create a large-format academic poster in LaTeX using beamerposter, tikzposter, or baposter.
146 GitHub stars~1.5k tokensUpdated 11 days ago
Auto-check: notes
Skill Creator
flonat/flonat-research
Create, revise, and evaluate reusable AI workflow skills, including trigger-quality tests.
146 GitHub stars~4.4k tokensUpdated 11 days ago
Auto-check passed
DOCX
flonat/flonat-research
Create, read, edit, or convert Microsoft Word documents while preserving professional document structure.
146 GitHub stars~1.2k tokensUpdated 11 days ago
Auto-check passed
PDF
flonat/flonat-research
Read, create, combine, split, rotate, OCR, watermark, secure, or extract content from PDF files.
146 GitHub stars~488 tokensUpdated 11 days ago
Auto-check passed
Init Project Orchestration
flonat/flonat-research
Create or migrate project-level agents, repeatable project workflows, and planning state from one client-neutral contract, then render repository-scoped adapters for both Claude Code and Codex.
146 GitHub stars~1.6k tokensUpdated 11 days ago
Auto-check passed
Pre Commit Audit
flonat/flonat-research
Deliver a fast pre-commit safety scan: file size, anonymity (author / affiliation strings in tex/bib), hardcoded secrets, and invisible-Unicode carriers.
146 GitHub stars~2.8k tokensUpdated 11 days ago
Auto-check: notes

Works with

LaTeX

Questions about Brief Compliance Check

What does Brief Compliance Check do?

Check a LaTeX coursework submission against the requirements in a supplied PDF assessment brief. Brief Compliance Check is an agent skill from flonat/flonat-research. Check a LaTeX coursework submission against the requirements in a supplied PDF assessment brief.

When should I use Brief Compliance Check?

Brief Compliance Check fits situations like: verifying format; required sections; deliverables before submission.

How do I install Brief Compliance Check in Claude Code?

Run `npx skills add flonat/flonat-research --skill brief-compliance-check -a claude-code`. Or copy the skill folder (skills/brief-compliance-check in flonat/flonat-research) into .claude/skills/brief-compliance-check in your project. Claude Code loads it when a task matches its description.

How do I install Brief Compliance Check in Codex?

Run `npx skills add flonat/flonat-research --skill brief-compliance-check -a codex`. Or copy the skill folder (skills/brief-compliance-check in flonat/flonat-research) into .agents/skills/brief-compliance-check in your project. Codex loads it when a task matches its description.

Can I use Brief Compliance Check in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add flonat/flonat-research --skill brief-compliance-check -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/brief-compliance-check, .gemini/skills/brief-compliance-check, .github/skills/brief-compliance-check and .opencode/skills/brief-compliance-check in your project.

What does Brief Compliance Check need to run?

Going by SKILL.md and its folder, Brief Compliance Check needs the command-line tools its instructions call (bash). Our summary lists: Python 3. Its frontmatter pre-approves these tools: Read, Glob, Bash(uv:*), Bash(ls*).

Does Brief Compliance Check access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Brief Compliance Check safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Brief Compliance Check use?

Brief Compliance Check is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Brief Compliance Check use?

About 1.7k tokens (SKILL.md is roughly 6.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Brief Compliance Check?

Skills that share tags, products or a category with Brief Compliance Check: Paper2patent (7toCR/paper2patent, 654 stars), Paperjury (Spark-To-Paper-Skills/paperjury-codex, 223 stars), Review Revision (M1n-n9/paper-lifecycle, 693 stars) and Evidence Ledger (wanshuiyin/Anti-Autoresearch, 160 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Brief Compliance Check?

flonat (a GitHub user) maintains it in flonat/flonat-research, which has 146 GitHub stars. The repository holds 83 skills in this directory. The repository was last updated on September 29, 2026.

Source: flonat/flonat-research on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Brief Compliance Check

Facts

At a glance

What it does

When your agent uses it

Example prompts

Requirements

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Brief Compliance Check

Output Path

When to Use

Defaults

Protocol

Step 1: Read the Brief

Step 2: Check Word Counts

Step 3: Check File Deliverables

Step 4: Report

Output Format

Never Do These

Log to REVIEW-STATE.md (final step)

Files

Compare with similar skills

Similar skills

More from flonat/flonat-research

Related

Questions about Brief Compliance Check