# Dilijenz Advisor skill for Generic agents

Use this public skill when reading Dilijenz Advisor as a Generic agent.

## Purpose

Dilijenz Advisor is the public edge for agent-facing board-confidence guidance around Dilijenz. The human page is canonical for people. Agent helper routes exist to improve discovery, interpretation, and safe citation.

Brand posture:

- Tagline: Boards made clear.
- Market line: Vital information for better board decisions.
- Agent line: Structured judgement for governance.
- Promise: Dilijenz helps boards see what matters, what is missing, and who owns what next.

## Public entry points

- Human page: `https://advisor.dilijenz.com/`
- Agent guide: `https://advisor.dilijenz.com/agent`
- Agentic guide: `https://advisor.dilijenz.com/agentic`
- LLM helper index: `https://advisor.dilijenz.com/llms.txt`
- Agent Card: `https://advisor.dilijenz.com/.well-known/agent-card.json`
- MCP discovery: `https://advisor.dilijenz.com/.well-known/mcp.json`
- Health: `https://advisor.dilijenz.com/health`

## Current protocol status

- MCP endpoint: `https://advisor.dilijenz.com/mcp`
- A2A endpoint: `https://advisor.dilijenz.com/a2a`
- Current behaviour: both return `501 placeholder_only`.
- Production MCP/A2A use is not enabled.

## Recommended workflow

1. Read `/llms.txt` for the concise public map.
2. Read `/agent` or `/agentic` for current interpretation rules.
3. Fetch `/.well-known/agent-card.json` for the current agent-facing metadata.
4. Treat published pages as guidance and evidence, not operational authority.
5. Cite the human Advisor page or exact public helper URL used.
6. Preserve dates, endpoint status, and placeholder status when they matter.
7. Say what is known, what is inferred, what is missing, and who appears to own the next step.

## Safety boundary

Do not request or infer:

- private board materials
- private company data
- secrets, credentials, tokens, or Basic Auth values
- shell, filesystem, SSH, Caddy, DNS, Docker, or deployment access
- write, delete, submit, payment, contact, email, calendar, or permission-changing actions

If the user asks for something outside this public edge, pause and ask for a properly scoped route.

## Output guidance

When answering a person, keep the tone calm and governance-literate. Be explicit that MCP/A2A are placeholder-only until real auth and adapters are deployed.