Give your AI agent a lien deadline playbook: it asks for the facts that matter, gets each date
from LienDeadline, and cites the statute behind it.
Built for US construction material suppliers and their credit and finance teams. The skill works
with Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot and other agents that read
Agent Skills. When a date can't be confirmed, your agent says so and
explains why. It never guesses.
Install · Try asking · Coverage ·
Privacy · FAQ · liendeadline.com
Why it matters
Miss a preliminary notice or a lien filing deadline and a supplier can lose its lien rights on the
job, and with them its leverage to get paid. The deadlines depend on the state, the project type
and who hired you. They can also move when something happens on the job, such as the owner's
final payment or a notice of extension.
Ask a general-purpose AI assistant and it may answer from memory, with a confident date and no
source. This skill gives your agent a better routine: collect the facts, get the date from
LienDeadline's calculation, show the statute, and flag anything it can't confirm.
What the skill does
- Asks the right questions. It discovers support for the project's state, type and hiring
relationship, then asks the jurisdiction-specific questions with yes, no or unknown answers.
- Gets the dates from LienDeadline. It uses the LienDeadline tools when they're connected, or
calls LienDeadline's API directly. Supplier discovery and calculations require a dedicated
customer API key; completed calculations consume API plan allowance. State guides remain public.
- Shows its work. Every deadline comes with its status, the statute behind it, and any warnings
or assumptions. The agent reports a date only when LienDeadline's answer matches the facts it sent.
- Flags instead of guessing. A missing fact, an "unknown" answer or a case that isn't covered
yet comes back as "needs review" with the reason, never a made-up date.
- Points you to the rules. It links the state's lien guide so you and your counsel can check
the details.
In action
Install
Any agent, one command. Adds the skill to Claude Code, Codex, Cursor, Gemini CLI, GitHub
Copilot and other agents that read Agent Skills:
npx skills add LienDeadline/skills
Or install it for a specific agent:
Claude Code. The plugin adds the skill and connects LienDeadline's hosted tools. Nothing runs
on your computer.
claude plugin marketplace add LienDeadline/skills
claude plugin install liendeadline@liendeadline
Inside a Claude Code session, run /plugin marketplace add LienDeadline/skills, then
/plugin install liendeadline@liendeadline.
Codex. The plugin adds the skill and the LienDeadline tools.
codex plugin marketplace add LienDeadline/skills
codex plugin add liendeadline@liendeadline
Gemini CLI. The extension adds the skill and the LienDeadline tools.
gemini extensions install https://github.com/LienDeadline/skills
GitHub CLI. Adds the skill for GitHub Copilot and the other agents it supports.
gh skill install LienDeadline/skills liendeadline
Claude on the web, desktop or mobile. Nothing to install: add
LienDeadline from Claude's Connectors directory.
Any other MCP client. Connect https://mcp.liendeadline.com/mcp (Streamable HTTP). State guides need no key; supplier discovery and calculations require a dedicated caller key configured through the client's approved secret settings.
If your agent reads Agent Skills, add the skill with the first command above as well. Installing
the skill alone does not connect the tools or provision API access. For a customer key, use the
approved access process, then configure the credential through
your client's secret settings without pasting it into a conversation.
Try asking
- "We supplied a Florida commercial job for a subcontractor from Aug 3 to Sep 10, 2026. No final
payment, no termination. When are our notice and lien deadlines?"
- "Same job, but I don't know whether the owner made final payment. What changes?"
- "Can I still file a lien for my last delivery on a Kansas job?"
- "Which states have lien guides? Show me Ohio's rules for material suppliers."
If your agent needs a fact you haven't given, it asks. If you don't know the answer, say so: the
deadline that depends on it comes back as "needs review", with the reason.
What it covers
| Today |
|---|
Supplier deadlines (supplier-events-v3) | Jurisdiction-specific discovery checks current support for the exact state, project type and hiring relationship before collecting event facts. Coverage extends beyond Florida and Kansas; only the live response establishes eligibility for your scope. |
Legacy workflow (supplier-events-v2) | Florida and Kansas private-project baselines. This contract does not describe the full v3 coverage. |
| Conditional outcomes | Independently required notices, qualified planning targets and recurring notice records when returned for the scope. Planning targets and advisory checkpoints remain distinct from calculated statutory deadlines. |
| Everything else | "Needs review" with the reason: unsupported scopes, public projects, and any deadline that depends on a fact you don't know |
| Lien guides | All 50 states and DC, with statute citations |
Results are calculated baselines, not legal advice.
How it works
flowchart LR
agent["AI agent<br/>with the LienDeadline skill"]
ld["LienDeadline<br/>MCP tools or HTTPS API"]
result["Statute-cited<br/>deadlines"]
agent -->|delivery facts and event answers| ld
ld -->|dates with statutes or a review flag| result
The skill is plain-language instructions with no code of its own. Your agent follows them and
sends LienDeadline only the structured facts it needs.
- Claude Code plugin: uses LienDeadline's hosted server, so nothing runs on your computer.
- Codex, Cursor and Gemini CLI packages: start the open-source
LienDeadline MCP server (GitHub) on your computer with
npx, pinned to one exact release. This needs Node.js 22.22 or newer.
- The skill on its own: uses the LienDeadline tools if you've connected them, or calls the
API over HTTPS with the required caller credentials for supplier operations.
Privacy and safety
- No notices or filings. It never sends notices, files liens or makes payments. Completed supplier calculations consume API plan allowance.
- Caller-controlled access. State guides remain public. Supplier discovery and calculations through MCP or direct API require a dedicated customer key; discovery consumes no calculation unit. Never paste key values into agent prompts or tracked configuration.
- Only the facts it needs. State, delivery dates, project type, who hired you, and yes, no or
unknown answers, with an event's date when the answer is yes. LienDeadline uses them to calculate
your dates and doesn't keep them.
- Anonymous usage counts. LienDeadline may count usage in aggregate with PostHog: which tool or
API operation ran, the type of client, whether it worked and how long it took. When your agent
calls the API directly, the skill adds a fixed
X-LienDeadline-Client: skill header so those
calls count as skill use. The counts never include your project facts, results, IP address or
account details, and no user profiles are built. The local MCP server sends no telemetry of its own.
Server logs and retention are covered in LienDeadline's privacy policy.
FAQ
Is this legal advice?
No. LienDeadline calculates baselines from published state rules and shows the statute behind
each date. Statutes change and every project is different, so check critical deadlines with
qualified counsel before you rely on them. LienDeadline is not a law firm and files nothing for you.
Which states can it calculate?
The supplier-events-v3 workflow supports jurisdiction-specific scopes beyond Florida and
Kansas. Authenticated live discovery checks the exact state, project type and hiring relationship
before facts are collected. The older supplier-events-v2 contract remains limited to Florida and
Kansas private projects. Lien guides cover all 50 states and DC.
Do I need an account or API key?
Supplier discovery and calculations through MCP or direct API require a dedicated LienDeadline customer key; completed calculations consume API plan allowance. Configure it through your client's approved secret settings. Guides remain public. The Website separately offers its ordinary anonymous calculation allowance.
What if I don't know one of the answers?
Say "unknown". The deadline that depends on it comes back as "needs review" with the reason. The
other deadline can still be calculated.
Will it send notices or file liens for me?
No. It retrieves guides and calculates only; completed supplier calculations consume API plan allowance.
Links
For contributors: the repository layout, checks and manifest notes are in
CONTRIBUTING.md.
License
MIT
