Map Tribunal Review Deadlines L0cka logo

Map Tribunal Review Deadlines L0cka

Organization
ThomasMoreAI
map-tribunal-review-deadlines-l0cka

Map and compute candidate merits-review and tribunal deadlines for Australian administrative and civil decisions, with computed coverage staged to the ART, NCAT, QCAT and VCAT and identify-only output for other tribunals, using the bundled deterministic script — never model arithmetic. Every migration-review output carries a mandatory non-extendable and jurisdictional-deadline warning with a specialist-review flag. Use when a practitioner needs candidate review or internal-appeal deadlines after a government or tribunal decision. Do not use for criminal matters, to conclude that a period has expired or been extended, or when the notification date is contested — those fail closed to the responsible lawyer.

Overview

PublisherThomasMoreAI
Repositorylegal-skills-open
Skill namemap-tribunal-review-deadlines-l0cka
Stars
97
Forks
13
Bundled files
1
LicenseMIT
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.

  • 1 bundled files

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

  • Open source

    Published by ThomasMoreAI on GitHub. Read the source before you install it.

Installation

Install the Map Tribunal Review Deadlines L0cka 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/ThomasMoreAI/legal-skills-open/tree/main/au/criminal/skills/map-tribunal-review-deadlines-l0cka
  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/ThomasMoreAI/legal-skills-open.git /tmp/legal-skills-open
mkdir -p .claude/skills
cp -r /tmp/legal-skills-open/au/criminal/skills/map-tribunal-review-deadlines-l0cka .claude/skills/map-tribunal-review-deadlines-l0cka
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Map Tribunal Review Deadlines L0cka 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 Map Tribunal Review Deadlines L0cka 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 Map Tribunal Review Deadlines L0cka 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.

Map Tribunal Review Deadlines

Map candidate review deadlines from the tribunal computation-rule tables and compute only through the bundled script. The enabling enactment frequently fixes its own period — the general tribunal layer is a candidate, never a conclusion.

Read the source and control method, use an approved profile per the deadline profile schema, and run compute_deadline.py against the computation-rule tables.

Workflow

  1. Fix the decision and the inputs.
    • Record the decision, the decision-maker, the tribunal, and the lawyer-supplied notification date as an assumption. A contested or unknown notification date is NOT READY.
  2. Locate every candidate period.
    • Take the general tribunal-layer candidate from the tribunal's table (art, ncat, qcat), and flag that the Act conferring the decision may fix a different period (for QCAT, s 6(7) of the QCAT Act says so expressly). Verify the conferring Act through $check-commonwealth-legislation or the applicable state checker.
    • For VCAT no general default period exists — the enabling enactment always fixes the period (see the vcat table note); identify the conferring provision and route its verification before any candidate is stated.
    • For tribunals without a table, produce identify-only output naming the enabling Act.
  3. Compute through the script only.
    • Run the script per candidate. Report computed and identify_only results faithfully, with every warning.
    • For any migration matter, always include the warning that migration time limits are non-extendable or jurisdictional and have changed repeatedly, and flag specialist review before reliance. Never conclude that a migration period has expired or that an extension is available.
  4. Set the human decision gate.
    • Name the confirmer who must confirm each candidate, resolve the conferring-Act period and enter dates in the diary system of record.

Result contract

Lead with READY FOR HUMAN REVIEW, READY WITH QUALIFICATIONS, NOT READY or OUTSIDE SCOPE.

text
Decision: <decision; decision-maker; tribunal; notification date assumption>
Candidates: <period; basis; script result (candidate date | identify-only);
  evidence state>
Conferring-Act check: <provision verified or routed; evidence state>
Migration warning: <present on every migration matter; specialist review>
Human decision gate: <confirmer; decisions required; diary entry pending>
Limitations: <every candidate provisional until confirmed; enabling
  enactment may differ; not a diary system>

Fail closed

Return NOT READY when the decision, tribunal or notification date cannot be established. Never compute around a script refusal, never conclude a period has expired or been extended, never omit the migration warning from a migration matter, and route criminal matters OUTSIDE SCOPE.

Other plugins

This skill names skills from other Legal Skills plugins. Install a required plugin alongside this one; install a hand-off plugin when the matter needs that depth.

  • australian-legal-research (required): check-commonwealth-legislation. Verifies the Commonwealth and state legislation behind limitation periods and deadline rules.

If a named skill is not available in this session, say so and name the plugin to install. Treat the step it would have performed as not done: record the affected proposition as not verified, or the hand-off as not made. Never perform that step from memory or substitute a different skill.

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 Map Tribunal Review Deadlines L0cka AI skill do?

Map and compute candidate merits-review and tribunal deadlines for Australian administrative and civil decisions, with computed coverage staged to the ART, NCAT, QCAT and VCAT and identify-only output for other tribunals, using the bundled deterministic script — never model arithmetic. Every migration-review output carries a mandatory non-extendable and jurisdictional-deadline warning with a specialist-review flag. Use when a practitioner needs candidate review or internal-appeal deadlines after a government or tribunal decision. Do not use for criminal matters, to conclude that a period ha...

Why use Map Tribunal Review Deadlines L0cka on TypingMind?

Because you install it once and use it with any model. Map Tribunal Review Deadlines L0cka 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 Map Tribunal Review Deadlines L0cka in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/ThomasMoreAI/legal-skills-open/tree/main/au/criminal/skills/map-tribunal-review-deadlines-l0cka. 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 Map Tribunal Review Deadlines L0cka?

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 Map Tribunal Review Deadlines L0cka?

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

Is the Map Tribunal Review Deadlines L0cka AI skill free?

Yes. It is published on GitHub by ThomasMoreAI 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.

View all

Set up your own AI workspace now

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