Home · Skills · Owner Approval Routing
Back to all skills

Owner Approval Routing

The plumbing for every gated action. Takes a pending `ApprovalRequest` and routes it to the correct approvers per the approval matrix row and org overlay, tracks SLA, and records the outcome to the approval audit log. Invoked by any workflow that opens an approval request. Never decides on behalf of humans; composes and routes.

What this skill does

Owner Approval Routing is an A.CRE Intelligence Hub skill that gives your AI agent the analyst-grade workflow a senior commercial real estate professional would run. The plumbing for every gated action. Takes a pending `ApprovalRequest` and routes it to the correct approvers per the approval matrix row and org overlay, tracks SLA, and records the outcome to the approval audit log. Invoked by any workflow that opens an approval request. Never decides on behalf of humans; composes and routes. The plumbing for every gated action. Takes a pending ApprovalRequest and routes it to the correct approvers per the approval matrix row and org overlay, tracks SLA, and records the outcome to the approval audit log. Invoked by any workflow that opens an approval request. Activate it inside ChatGPT, Claude, Manus, or OpenClaw by saying something like "Use the Owner Approval Routing skill" — the Hub routes the request to this skill and the underlying primary-source CRE data feeds backends automatically.

How you'll use it

"Use the Owner Approval Routing skill"

Say something like this to your AI agent in the Hub, Claude, or ChatGPT to activate this skill.

Skill activation rules

Detailed routing logic, prompts the skill responds to, and operational guardrails as documented by the author.

The plumbing for every gated action. Takes a pending `ApprovalRequest` and routes it to the correct approvers per the approval matrix row and org overlay, tracks SLA, and records the outcome to the approval audit log. Invoked by any workflow that opens an approval request. Never decides on behalf of humans; composes and routes.

What's inside

Owner Approval Routing

Workflow purpose

Deliver approval requests to the right approvers, in the right order, with the right package, and with an enforced SLA. Produce a complete audit trail. Every gated action in the subsystem depends on this workflow; its job is to make…

Show full previewShow less

Owner Approval Routing

Workflow purpose

Deliver approval requests to the right approvers, in the right order, with the right package, and with an enforced SLA. Produce a complete audit trail. Every gated action in the subsystem depends on this workflow; its job is to make approvals a simple, reliable plumbing layer.

Trigger conditions

  • Explicit: "route this approval", "open approval request for X", "approval status update".
  • Implicit: any workflow writes an ApprovalRequest record.
  • Recurring: continuous; SLA screen runs daily.

Inputs (required / optional)

Input Type Required Notes
ApprovalRequest record record required includes matrix row, subject, actor, proposed action
Approval routing policy overlay yaml required per-org overrides to matrix defaults
Approver roster yaml required org contacts per role
Related artifacts package required memos, drafts, estimates

Outputs

Full instructions and any reference files ship in the .skill bundle.

Bundle structure
owner-approval-routing/
└── SKILL.md             # Required: instructions + metadata

Who built it

With contributions from Avi Hacker.

How to run it

Not in the Hub? Download the .skill bundle above and follow the A.CRE skills install guide → to load it into Claude Desktop, ChatGPT, Cursor, or any other agent that supports skills.

Already in the Hub. If you're an AI.Edge Pro or A.CRE Accelerator member, this skill is bundled into the A.CRE Intelligence Hub direct connector (MCP server) — just ask your agent.

About this skill

Third-Party skill. This skill is redistributed under the Apache-2.0 license and is not authored or endorsed by Adventures in CRE. Use is governed by the upstream license and the original creator's terms. Original attribution: Mario Urquia (link) and contributors (Avi Hacker).