NV oOS Pro Toolkit Services & Approvals
The Pro Toolkit Services & Approvals system manages Service Components (a registry
of microservices, external APIs, and internal components with dependency tracking) and
Approval Requests (human-in-the-loop gates for workflow automation requiring
sign-off). All entities are CPT records accessed via toolkit_cpt.
WP-CLI Commands
Key mcp-ai WP-CLI commands for service and approval operations. Run via terminal:
| Command |
Use for |
wp mcp-ai service list |
List all registered service components with status |
wp mcp-ai service check |
Run health checks against all monitored service endpoints |
wp mcp-ai approval list |
List pending and completed approval requests |
wp mcp-ai approval resolve |
Resolve an approval request (approve/reject) by ID |
wp mcp-ai health |
Verify service registry integrity and approval queue health |
wp mcp-ai log |
View service health check and approval workflow logs |
When to use this skill
Trigger when ANY of the following is true:
- Registering a new service component or microservice in the toolkit.
- Listing or searching the service registry for existing components.
- Tracking service dependencies — which services depend on which others.
- Checking service health status or endpoint availability.
- Creating, reviewing, approving, or rejecting approval requests.
- Configuring approval gates in a Pro Workflow Builder DAG.
- Querying approval history for audit or compliance purposes.
- Managing version tracking for registered service components.
- Troubleshooting a workflow that is blocked on an approval gate.
- Setting up automated health checks for critical service endpoints.
Mental model — services and approvals
The Services & Approvals system has two independent but complementary domains:
SERVICE COMPONENT ──(registered in)──→ Service Registry
│
├── Service Type (microservice, api, internal, external)
├── Endpoint URL (health check + invocation)
├── Status (active, degraded, down, maintenance)
├── Version + Environment
├── Dependencies (references to other services)
└── Health Check Configuration
APPROVAL REQUEST ──(created by)──→ Workflow / User / System
│
├── Request Type (workflow_gate, content_review, access_request, deployment)
├── Requester (WP user ID or system identifier)
├── Status (pending → approved / rejected)
├── Approver (WP user ID who acted)
├── Workflow Context (DAG node ID, action reference)
└── Audit Trail (timestamps, rationale, metadata)
SERVICE DEPENDENCY GRAPH:
Service A ──depends_on──→ Service B ──depends_on──→ Service C
│ │
└──depends_on──→ Service D
Relationships:
- A Service Component (
mcp_ai_service) is a standalone registry entry with
type, endpoint, status, version, and _service_dependencies (array of post IDs).
The dependency graph must remain acyclic.
- An Approval Request (
mcp_ai_approval) is a time-bound decision record
created by a workflow node, user, or system event. It tracks requester, approver,
status, rationale, and timestamps. Workflow builder nodes read status to proceed.
- Service ↔ Approval is indirect: a deployment approval may reference a
service, and a health check failure may auto-create an approval.
Entity Types
All Services & Approvals entities are managed through the toolkit_cpt MCP tool.
Use the appropriate post_type slug for each entity:
| CPT Slug |
Label |
Supports |
Key Meta Fields |
mcp_ai_service |
Service Components |
title |
_service_type, _service_endpoint, _service_status, _service_version, _service_environment, _service_dependencies, _service_health_check_url, _service_health_interval, _service_owner, _service_description |
mcp_ai_approval |
Approval Requests |
title, custom-fields |
_approval_type, _approval_requester_id, _approval_status, _approval_approver_id, _approval_workflow_id, _approval_node_id, _approval_rationale, _approval_requested_at, _approval_resolved_at, _approval_priority, _approval_context |
Service Component Meta Fields (detailed)
| Field |
Type |
Description |
Example |
_service_type |
string |
Category of service |
"microservice", "external_api", "internal", "database", "queue" |
_service_endpoint |
string |
Primary invocation endpoint URL |
"https://api.example.com/v2" |
_service_status |
string |
Current operational status |
"active", "degraded", "down", "maintenance", "unknown" |
_service_version |
string |
Semantic version of the service |
"2.1.0" |
_service_environment |
string |
Deployment environment |
"production", "staging", "development" |
_service_dependencies |
array |
Post IDs of dependent services |
[15, 23, 42] |
_service_health_check_url |
string |
Health check endpoint URL |
"https://api.example.com/health" |
_service_health_interval |
string |
Health check interval in seconds |
"300" |
_service_owner |
string |
WP user ID of service owner |
"1" |
_service_description |
string |
Human-readable service description |
"Payment processing gateway - Stripe integration" |
Approval Request Meta Fields (detailed)
| Field |
Type |
Description |
Example |
_approval_type |
string |
Category of approval request |
"workflow_gate", "content_review", "access_request", "deployment", "config_change" |
_approval_requester_id |
string |
WP user ID or system identifier |
"5", "system:workflow-builder" |
_approval_status |
string |
Current approval state |
"pending", "approved", "rejected", "cancelled", "expired" |
_approval_approver_id |
string |
WP user ID of the approver (set on resolution) |
"1" |
_approval_workflow_id |
string |
Pro Workflow Builder workflow ID (if applicable) |
"wf_42" |
_approval_node_id |
string |
DAG node ID that created this approval |
"node_approval_deploy" |
_approval_rationale |
string |
Approver's reason for decision |
"Change approved after security review" |
_approval_requested_at |
string |
ISO 8601 timestamp of request creation |
"2026-08-12T09:00:00Z" |
_approval_resolved_at |
string |
ISO 8601 timestamp of resolution |
"2026-08-12T14:30:00Z" |
_approval_priority |
string |
Urgency level |
"low", "normal", "high", "critical" |
_approval_context |
object |
Arbitrary JSON context data |
{"deploy_target": "production", "change_summary": "..."} |
Available Tools
All Services & Approvals operations use the toolkit_cpt MCP tool. This is the
single interface for all service and approval CRUD operations.
Discovery
toolkit_cpt(action: "list_types") # Confirm CPTs
toolkit_cpt(action: "get_schema", post_type: "mcp_ai_service") # Service fields
toolkit_cpt(action: "get_schema", post_type: "mcp_ai_approval") # Approval fields
Reading records
// List all production services
{
"name": "toolkit_cpt",
"arguments": {
"action": "list_items",
"post_type": "mcp_ai_service",
"filters": [
{ "key": "_service_environment", "value": "production" }
],
"orderby": "title",
"order": "ASC",
"per_page": 20
}
}
// Search services by name or description
{
"name": "toolkit_cpt",
"arguments": {
"action": "list_items",
"post_type": "mcp_ai_service",
"search": "payment"
}
}
// Get a single service with all fields
{
"name": "toolkit_cpt",
"arguments": {
"action": "get_item",
"post_type": "mcp_ai_service",
"item_id": 10
}
}
// List all pending approval requests (highest priority first)
{
"name": "toolkit_cpt",
"arguments": {
"action": "list_items",
"post_type": "mcp_ai_approval",
"filters": [
{ "key": "_approval_status", "value": "pending" }
],
"orderby": "date",
"order": "DESC",
"per_page": 20
}
}
// Get a single approval request
{
"name": "toolkit_cpt",
"arguments": {
"action": "get_item",
"post_type": "mcp_ai_approval",
"item_id": 88
}
}
Creating records
// Register a new service component
{
"name": "toolkit_cpt",
"arguments": {
"action": "create_item",
"post_type": "mcp_ai_service",
"fields": {
"title": "Payment Gateway - Stripe",
"_service_type": "external_api",
"_service_endpoint": "https://api.stripe.com/v1",
"_service_status": "active",
"_service_version": "2024-06",
"_service_environment": "production",
"_service_health_check_url": "https://api.stripe.com/v1/balance",
"_service_health_interval": "300",
"_service_owner": "1",
"_service_description": "Stripe payment processing integration for WooCommerce orders",
"_service_dependencies": []
}
}
}
// Create an approval request for a deployment gate
{
"name": "toolkit_cpt",
"arguments": {
"action": "create_item",
"post_type": "mcp_ai_approval",
"fields": {
"title": "Deploy Payment Service v2.1.0 to Production",
"_approval_type": "deployment",
"_approval_requester_id": "5",
"_approval_status": "pending",
"_approval_workflow_id": "wf_42",
"_approval_node_id": "node_approval_deploy",
"_approval_priority": "high",
"_approval_context": {
"service_id": 10,
"version_from": "2.0.3",
"version_to": "2.1.0",
"change_summary": "Adds support for new payment methods; includes security patch for CVE-2026-1234"
}
}
}
}
Updating records
// Update service status after a health check
{
"name": "toolkit_cpt",
"arguments": {
"action": "update_item",
"post_type": "mcp_ai_service",
"item_id": 10,
"fields": {
"_service_status": "degraded",
"_service_version": "2024-08"
}
}
}
// Add a dependency to a service
{
"name": "toolkit_cpt",
"arguments": {
"action": "update_item",
"post_type": "mcp_ai_service",
"item_id": 10,
"fields": {
"_service_dependencies": [15, 23]
}
}
}
// Approve a pending request
{
"name": "toolkit_cpt",
"arguments": {
"action": "update_item",
"post_type": "mcp_ai_approval",
"item_id": 88,
"fields": {
"_approval_status": "approved",
"_approval_approver_id": "1",
"_approval_rationale": "Security patch validated. Deployment approved.",
"_approval_resolved_at": "2026-08-12T14:30:00Z"
}
}
}
// Reject: set _approval_status to "rejected" with _approval_rationale and _approval_resolved_at
Bulk & Delete operations
// Bulk register microservices
{
"name": "toolkit_cpt",
"arguments": {
"action": "bulk_create",
"post_type": "mcp_ai_service",
"items": [
{ "title": "Email Service - SendGrid", "_service_type": "external_api", "_service_status": "active", "_service_environment": "production" },
{ "title": "Search Service - Elasticsearch", "_service_type": "database", "_service_status": "active", "_service_environment": "production" }
]
}
}
// Delete a record (permanent — prefer status update to preserve history)
{ "name": "toolkit_cpt", "arguments": { "action": "delete_item", "post_type": "mcp_ai_service", "item_id": 99 } }
⚠️ Warning: Deleting a service removes it from the registry — any dependencies
become broken references. Use _service_status: "down" instead. Deleting an approval
removes the audit trail — use _approval_status: "cancelled" instead.
Common Workflows
Registering a new service component
1. Get schema: get_schema(mcp_ai_service) — verify available fields.
2. Identify type: Choose _service_type (microservice, external_api, internal, etc.).
3. Set endpoint: Provide the primary URL for invocation.
4. Add health check: Set _service_health_check_url and _service_health_interval.
5. Map dependencies: List IDs of services this component depends on.
6. Create record: create_item(mcp_ai_service, with all fields).
7. Verify: get_item(mcp_ai_service, item_id: <new_id>) to confirm.
Service health check audit
1. list_items(mcp_ai_service, filters: [{key: "_service_status", value: "active"}])
2. For each service, fetch _service_health_check_url and verify 200 OK.
3. On failure: update_item(mcp_ai_service, _service_status: "degraded")
4. If down >24h: update_item(mcp_ai_service, _service_status: "down")
→ Optionally create an approval request for maintenance action.
5. On recovery: update_item(mcp_ai_service, _service_status: "active")
Approval request lifecycle
1. create_item(mcp_ai_approval, _approval_status: "pending") → Workflow gate pauses.
2. Approver reviews: get_item(mcp_ai_approval, item_id: <id>) → Inspect context & priority.
3. Approver decides: update_item → _approval_status: "approved"|"rejected"
→ Always include _approval_rationale, _approval_resolved_at, _approval_approver_id.
4. Workflow resumes: "approved" → next node; "rejected" → rejection branch or halt.
5. Audit: list_items(mcp_ai_approval, filters by _approval_type) for compliance.
Dependency graph validation
1. list_items(mcp_ai_service, per_page: 100) — collect all services.
2. For each, inspect _service_dependencies array.
3. Flag cycles (A→B, B→A), orphans (non-existent IDs), unknowns (status: down/unknown).
4. Report broken references for manual remediation.
Triaging pending approvals
1. list_items(mcp_ai_approval, filters: [{key: "_approval_status", value: "pending"}])
→ Sort by _approval_priority: critical first.
2. Critical/high >4h stale → escalate to service owner.
3. Normal/low >24h stale → check if context is still relevant; cancel if not.
4. Cross-reference _approval_workflow_id with workflow builder to find blocked DAGs.
Critical Rules
- Always use
get_schema first before creating or updating a record to verify available field keys and types.
- Service dependencies must form a directed acyclic graph (DAG) — circular dependencies cause infinite health check loops and deployment deadlocks.
_service_dependencies is an array of post IDs — pass it as [15, 23], not "15, 23".
_approval_context is a JSON object — pass it as a native object in the JSON payload, not a string.
- Approval requests are immutable audit records once resolved — never change the status back from "approved" or "rejected" to "pending". Create a new request instead.
_approval_resolved_at must be set when resolving — always include the timestamp alongside _approval_status changes to "approved" or "rejected".
- Service status transitions should follow a defined path:
active → degraded → down or active → maintenance → active. Don't jump from active to down without a degraded intermediate step unless there's a hard outage.
_service_health_interval is a string in seconds — use "300" not 300.
- Approval priority drives SLA — critical: 1 hour, high: 4 hours, normal: 24 hours, low: 72 hours. Escalate when SLAs are breached.
- Never delete approval requests — use
_approval_status: "cancelled" to preserve the audit trail.
Common Mistakes
WRONG — creating a service with circular dependencies
Service A: _service_dependencies: [15] (depends on B)
Service B: _service_dependencies: [10] (depends on A)
// Creates a circular reference — health checks and deployments deadlock.
RIGHT — ensure the dependency graph is a DAG
Service A: _service_dependencies: [15] (depends on B)
Service B: _service_dependencies: [42] (depends on C)
// A → B → C is a valid acyclic chain.
WRONG — resolving an approval without rationale or timestamp
{ "action": "update_item", "post_type": "mcp_ai_approval", "item_id": 88,
"fields": { "_approval_status": "approved" } }
// Missing _approval_rationale and _approval_resolved_at — the audit trail is incomplete.
RIGHT — fully document the resolution
{ "action": "update_item", "post_type": "mcp_ai_approval", "item_id": 88,
"fields": { "_approval_status": "approved", "_approval_approver_id": "1",
"_approval_rationale": "Change validated. No regressions in staging.", "_approval_resolved_at": "2026-08-12T14:30:00Z" } }
WRONG — deleting an approval instead of cancelling
{ "action": "delete_item", "post_type": "mcp_ai_approval", "item_id": 88 }
// Permanent loss of the audit record. Compliance auditors cannot trace the decision.
RIGHT — cancel to preserve the record
{ "action": "update_item", "post_type": "mcp_ai_approval", "item_id": 88,
"fields": { "_approval_status": "cancelled", "_approval_rationale": "Deployment superseded by wf_99" } }
WRONG — passing _approval_context as a JSON string
{ "fields": { "_approval_context": "{\"key\": \"value\"}" } }
// The field parser expects a native object, not an escaped string.
RIGHT — pass _approval_context as a native object
{ "fields": { "_approval_context": { "key": "value" } } }
WRONG — setting a service dependency to a non-existent post ID
{ "fields": { "_service_dependencies": [99999] } }
// Post ID 99999 doesn't exist — the dependency graph has a dangling reference.
WRONG — jumping service status from "active" directly to "down"
{ "fields": { "_service_status": "down" } }
// Skips the "degraded" intermediate state, losing granularity for incident response.
Cross-References
- Run
design-pro-workflow-builder to create DAG workflows with approval nodes that reference mcp_ai_approval records.
- Run
design-pro-schedule-manager to schedule recurring service health checks and approval queue reviews.
- Run
design-ai-assistant-admin if an AI assistant triggers or resolves approval requests automatically.
- Run
design-crm if service components are linked to client accounts or deals.
- Run
design-project-management to track service-related tasks (deployments, migrations, incident response).
- Run
design-vault to securely store service API keys and endpoint credentials referenced in service configs.
- Run
design-document-generation to create deployment runbooks, incident reports, or approval summaries from service/approval data.
- Run
wp-security-audit on any endpoint exposed by registered services — the registry itself does not secure the endpoints.
What This Skill Does NOT Cover
- Actual service implementation (code, containers, infrastructure) — this skill manages the registry, not the services themselves.
- Workflow builder DAG design — use
design-pro-workflow-builder for node configuration and approval node placement.
- Health check execution engine — the Cron/Worker system performs checks; this skill covers the configuration and status interpretation.
- Service monitoring dashboards (Grafana, Datadog) — use external observability tools for real-time metrics.
- Approval notification delivery (email, SMS, Slack) — use
design-communications and design-email-marketing for notification channels.
- API key management for registered services — use
design-vault for credential storage.
- WordPress plugin/service discovery — use
get_update_status and nv_oos_console_agent_get_environment_status for plugin-level health.
References
- NV oOS Pro Toolkit Services admin page:
/wp-admin/admin.php?page=nvoos-pro-toolkit-services
- NV oOS Pro Toolkit Approvals admin page:
/wp-admin/admin.php?page=nvoos-pro-toolkit-approvals
toolkit_cpt MCP tool — the primary interface for all service and approval operations.
- Pro Workflow Builder approval node: uses
mcp_ai_approval records as gates.
- Semantic versioning specification: semver.org
1---2type: Skill3name: design-services4description: Manage service components and approval workflows in the NV oOS Pro Toolkit. Covers service component registration, dependency tracking, approval request lifecycle, and workflow approval gates. Use when registering service components, tracking service dependencies, managing approval requests, or configuring workflow approval nodes.5license: Proprietary. See LICENSE.txt6metadata:7 source: https://skillmd.com/skills/nvdigitalsolutions/design-services8 type: Skill9---1011# NV oOS Pro Toolkit Services & Approvals1213The Pro Toolkit Services & Approvals system manages **Service Components** (a registry14of microservices, external APIs, and internal components with dependency tracking) and15**Approval Requests** (human-in-the-loop gates for workflow automation requiring16sign-off). All entities are CPT records accessed via `toolkit_cpt`.1718## WP-CLI Commands1920Key `mcp-ai` WP-CLI commands for service and approval operations. Run via `terminal`:2122| Command | Use for |23|---|---|24| `wp mcp-ai service list` | List all registered service components with status |25| `wp mcp-ai service check` | Run health checks against all monitored service endpoints |26| `wp mcp-ai approval list` | List pending and completed approval requests |27| `wp mcp-ai approval resolve` | Resolve an approval request (approve/reject) by ID |28| `wp mcp-ai health` | Verify service registry integrity and approval queue health |29| `wp mcp-ai log` | View service health check and approval workflow logs |3031## When to use this skill3233Trigger when ANY of the following is true:3435- Registering a new service component or microservice in the toolkit.36- Listing or searching the service registry for existing components.37- Tracking service dependencies — which services depend on which others.38- Checking service health status or endpoint availability.39- Creating, reviewing, approving, or rejecting approval requests.40- Configuring approval gates in a Pro Workflow Builder DAG.41- Querying approval history for audit or compliance purposes.42- Managing version tracking for registered service components.43- Troubleshooting a workflow that is blocked on an approval gate.44- Setting up automated health checks for critical service endpoints.4546## Mental model — services and approvals4748The Services & Approvals system has two independent but complementary domains:4950```51SERVICE COMPONENT ──(registered in)──→ Service Registry52 │53 ├── Service Type (microservice, api, internal, external)54 ├── Endpoint URL (health check + invocation)55 ├── Status (active, degraded, down, maintenance)56 ├── Version + Environment57 ├── Dependencies (references to other services)58 └── Health Check Configuration5960APPROVAL REQUEST ──(created by)──→ Workflow / User / System61 │62 ├── Request Type (workflow_gate, content_review, access_request, deployment)63 ├── Requester (WP user ID or system identifier)64 ├── Status (pending → approved / rejected)65 ├── Approver (WP user ID who acted)66 ├── Workflow Context (DAG node ID, action reference)67 └── Audit Trail (timestamps, rationale, metadata)6869SERVICE DEPENDENCY GRAPH:70 Service A ──depends_on──→ Service B ──depends_on──→ Service C71 │ │72 └──depends_on──→ Service D73```7475**Relationships:**76- A **Service Component** (`mcp_ai_service`) is a standalone registry entry with77 type, endpoint, status, version, and `_service_dependencies` (array of post IDs).78 The dependency graph must remain acyclic.79- An **Approval Request** (`mcp_ai_approval`) is a time-bound decision record80 created by a workflow node, user, or system event. It tracks requester, approver,81 status, rationale, and timestamps. Workflow builder nodes read status to proceed.82- **Service ↔ Approval** is indirect: a deployment approval may reference a83 service, and a health check failure may auto-create an approval.8485## Entity Types8687All Services & Approvals entities are managed through the **`toolkit_cpt`** MCP tool.88Use the appropriate `post_type` slug for each entity:8990| CPT Slug | Label | Supports | Key Meta Fields |91|---|---|---|---|92| `mcp_ai_service` | Service Components | title | `_service_type`, `_service_endpoint`, `_service_status`, `_service_version`, `_service_environment`, `_service_dependencies`, `_service_health_check_url`, `_service_health_interval`, `_service_owner`, `_service_description` |93| `mcp_ai_approval` | Approval Requests | title, custom-fields | `_approval_type`, `_approval_requester_id`, `_approval_status`, `_approval_approver_id`, `_approval_workflow_id`, `_approval_node_id`, `_approval_rationale`, `_approval_requested_at`, `_approval_resolved_at`, `_approval_priority`, `_approval_context` |9495### Service Component Meta Fields (detailed)9697| Field | Type | Description | Example |98|---|---|---|---|99| `_service_type` | string | Category of service | `"microservice"`, `"external_api"`, `"internal"`, `"database"`, `"queue"` |100| `_service_endpoint` | string | Primary invocation endpoint URL | `"https://api.example.com/v2"` |101| `_service_status` | string | Current operational status | `"active"`, `"degraded"`, `"down"`, `"maintenance"`, `"unknown"` |102| `_service_version` | string | Semantic version of the service | `"2.1.0"` |103| `_service_environment` | string | Deployment environment | `"production"`, `"staging"`, `"development"` |104| `_service_dependencies` | array | Post IDs of dependent services | `[15, 23, 42]` |105| `_service_health_check_url` | string | Health check endpoint URL | `"https://api.example.com/health"` |106| `_service_health_interval` | string | Health check interval in seconds | `"300"` |107| `_service_owner` | string | WP user ID of service owner | `"1"` |108| `_service_description` | string | Human-readable service description | `"Payment processing gateway - Stripe integration"` |109110### Approval Request Meta Fields (detailed)111112| Field | Type | Description | Example |113|---|---|---|---|114| `_approval_type` | string | Category of approval request | `"workflow_gate"`, `"content_review"`, `"access_request"`, `"deployment"`, `"config_change"` |115| `_approval_requester_id` | string | WP user ID or system identifier | `"5"`, `"system:workflow-builder"` |116| `_approval_status` | string | Current approval state | `"pending"`, `"approved"`, `"rejected"`, `"cancelled"`, `"expired"` |117| `_approval_approver_id` | string | WP user ID of the approver (set on resolution) | `"1"` |118| `_approval_workflow_id` | string | Pro Workflow Builder workflow ID (if applicable) | `"wf_42"` |119| `_approval_node_id` | string | DAG node ID that created this approval | `"node_approval_deploy"` |120| `_approval_rationale` | string | Approver's reason for decision | `"Change approved after security review"` |121| `_approval_requested_at` | string | ISO 8601 timestamp of request creation | `"2026-08-12T09:00:00Z"` |122| `_approval_resolved_at` | string | ISO 8601 timestamp of resolution | `"2026-08-12T14:30:00Z"` |123| `_approval_priority` | string | Urgency level | `"low"`, `"normal"`, `"high"`, `"critical"` |124| `_approval_context` | object | Arbitrary JSON context data | `{"deploy_target": "production", "change_summary": "..."}` |125126## Available Tools127128All Services & Approvals operations use the **`toolkit_cpt`** MCP tool. This is the129single interface for all service and approval CRUD operations.130131### Discovery132133```134toolkit_cpt(action: "list_types") # Confirm CPTs135toolkit_cpt(action: "get_schema", post_type: "mcp_ai_service") # Service fields136toolkit_cpt(action: "get_schema", post_type: "mcp_ai_approval") # Approval fields137```138139### Reading records140141```json142// List all production services143{144 "name": "toolkit_cpt",145 "arguments": {146 "action": "list_items",147 "post_type": "mcp_ai_service",148 "filters": [149 { "key": "_service_environment", "value": "production" }150 ],151 "orderby": "title",152 "order": "ASC",153 "per_page": 20154 }155}156157// Search services by name or description158{159 "name": "toolkit_cpt",160 "arguments": {161 "action": "list_items",162 "post_type": "mcp_ai_service",163 "search": "payment"164 }165}166167// Get a single service with all fields168{169 "name": "toolkit_cpt",170 "arguments": {171 "action": "get_item",172 "post_type": "mcp_ai_service",173 "item_id": 10174 }175}176177// List all pending approval requests (highest priority first)178{179 "name": "toolkit_cpt",180 "arguments": {181 "action": "list_items",182 "post_type": "mcp_ai_approval",183 "filters": [184 { "key": "_approval_status", "value": "pending" }185 ],186 "orderby": "date",187 "order": "DESC",188 "per_page": 20189 }190}191192// Get a single approval request193{194 "name": "toolkit_cpt",195 "arguments": {196 "action": "get_item",197 "post_type": "mcp_ai_approval",198 "item_id": 88199 }200}201```202203### Creating records204205```json206// Register a new service component207{208 "name": "toolkit_cpt",209 "arguments": {210 "action": "create_item",211 "post_type": "mcp_ai_service",212 "fields": {213 "title": "Payment Gateway - Stripe",214 "_service_type": "external_api",215 "_service_endpoint": "https://api.stripe.com/v1",216 "_service_status": "active",217 "_service_version": "2024-06",218 "_service_environment": "production",219 "_service_health_check_url": "https://api.stripe.com/v1/balance",220 "_service_health_interval": "300",221 "_service_owner": "1",222 "_service_description": "Stripe payment processing integration for WooCommerce orders",223 "_service_dependencies": []224 }225 }226}227228// Create an approval request for a deployment gate229{230 "name": "toolkit_cpt",231 "arguments": {232 "action": "create_item",233 "post_type": "mcp_ai_approval",234 "fields": {235 "title": "Deploy Payment Service v2.1.0 to Production",236 "_approval_type": "deployment",237 "_approval_requester_id": "5",238 "_approval_status": "pending",239 "_approval_workflow_id": "wf_42",240 "_approval_node_id": "node_approval_deploy",241 "_approval_priority": "high",242 "_approval_context": {243 "service_id": 10,244 "version_from": "2.0.3",245 "version_to": "2.1.0",246 "change_summary": "Adds support for new payment methods; includes security patch for CVE-2026-1234"247 }248 }249 }250}251```252253### Updating records254255```json256// Update service status after a health check257{258 "name": "toolkit_cpt",259 "arguments": {260 "action": "update_item",261 "post_type": "mcp_ai_service",262 "item_id": 10,263 "fields": {264 "_service_status": "degraded",265 "_service_version": "2024-08"266 }267 }268}269270// Add a dependency to a service271{272 "name": "toolkit_cpt",273 "arguments": {274 "action": "update_item",275 "post_type": "mcp_ai_service",276 "item_id": 10,277 "fields": {278 "_service_dependencies": [15, 23]279 }280 }281}282283// Approve a pending request284{285 "name": "toolkit_cpt",286 "arguments": {287 "action": "update_item",288 "post_type": "mcp_ai_approval",289 "item_id": 88,290 "fields": {291 "_approval_status": "approved",292 "_approval_approver_id": "1",293 "_approval_rationale": "Security patch validated. Deployment approved.",294 "_approval_resolved_at": "2026-08-12T14:30:00Z"295 }296 }297}298299// Reject: set _approval_status to "rejected" with _approval_rationale and _approval_resolved_at300```301302### Bulk & Delete operations303304```json305// Bulk register microservices306{307 "name": "toolkit_cpt",308 "arguments": {309 "action": "bulk_create",310 "post_type": "mcp_ai_service",311 "items": [312 { "title": "Email Service - SendGrid", "_service_type": "external_api", "_service_status": "active", "_service_environment": "production" },313 { "title": "Search Service - Elasticsearch", "_service_type": "database", "_service_status": "active", "_service_environment": "production" }314 ]315 }316}317318// Delete a record (permanent — prefer status update to preserve history)319{ "name": "toolkit_cpt", "arguments": { "action": "delete_item", "post_type": "mcp_ai_service", "item_id": 99 } }320```321322**⚠️ Warning:** Deleting a service removes it from the registry — any dependencies323become broken references. Use `_service_status: "down"` instead. Deleting an approval324removes the audit trail — use `_approval_status: "cancelled"` instead.325326## Common Workflows327328### Registering a new service component329330```3311. Get schema: get_schema(mcp_ai_service) — verify available fields.3322. Identify type: Choose _service_type (microservice, external_api, internal, etc.).3333. Set endpoint: Provide the primary URL for invocation.3344. Add health check: Set _service_health_check_url and _service_health_interval.3355. Map dependencies: List IDs of services this component depends on.3366. Create record: create_item(mcp_ai_service, with all fields).3377. Verify: get_item(mcp_ai_service, item_id: <new_id>) to confirm.338```339340### Service health check audit341342```3431. list_items(mcp_ai_service, filters: [{key: "_service_status", value: "active"}])3442. For each service, fetch _service_health_check_url and verify 200 OK.3453. On failure: update_item(mcp_ai_service, _service_status: "degraded")3464. If down >24h: update_item(mcp_ai_service, _service_status: "down")347 → Optionally create an approval request for maintenance action.3485. On recovery: update_item(mcp_ai_service, _service_status: "active")349```350351### Approval request lifecycle352353```3541. create_item(mcp_ai_approval, _approval_status: "pending") → Workflow gate pauses.3552. Approver reviews: get_item(mcp_ai_approval, item_id: <id>) → Inspect context & priority.3563. Approver decides: update_item → _approval_status: "approved"|"rejected"357 → Always include _approval_rationale, _approval_resolved_at, _approval_approver_id.3584. Workflow resumes: "approved" → next node; "rejected" → rejection branch or halt.3595. Audit: list_items(mcp_ai_approval, filters by _approval_type) for compliance.360```361362### Dependency graph validation363364```3651. list_items(mcp_ai_service, per_page: 100) — collect all services.3662. For each, inspect _service_dependencies array.3673. Flag cycles (A→B, B→A), orphans (non-existent IDs), unknowns (status: down/unknown).3684. Report broken references for manual remediation.369```370371### Triaging pending approvals372373```3741. list_items(mcp_ai_approval, filters: [{key: "_approval_status", value: "pending"}])375 → Sort by _approval_priority: critical first.3762. Critical/high >4h stale → escalate to service owner.3773. Normal/low >24h stale → check if context is still relevant; cancel if not.3784. Cross-reference _approval_workflow_id with workflow builder to find blocked DAGs.379```380381## Critical Rules382383- **Always use `get_schema` first** before creating or updating a record to verify available field keys and types.384- **Service dependencies must form a directed acyclic graph (DAG)** — circular dependencies cause infinite health check loops and deployment deadlocks.385- **`_service_dependencies` is an array of post IDs** — pass it as `[15, 23]`, not `"15, 23"`.386- **`_approval_context` is a JSON object** — pass it as a native object in the JSON payload, not a string.387- **Approval requests are immutable audit records once resolved** — never change the status back from "approved" or "rejected" to "pending". Create a new request instead.388- **`_approval_resolved_at` must be set when resolving** — always include the timestamp alongside `_approval_status` changes to "approved" or "rejected".389- **Service status transitions should follow a defined path**: `active → degraded → down` or `active → maintenance → active`. Don't jump from `active` to `down` without a `degraded` intermediate step unless there's a hard outage.390- **`_service_health_interval` is a string in seconds** — use `"300"` not `300`.391- **Approval priority drives SLA** — critical: 1 hour, high: 4 hours, normal: 24 hours, low: 72 hours. Escalate when SLAs are breached.392- **Never delete approval requests** — use `_approval_status: "cancelled"` to preserve the audit trail.393394## Common Mistakes395396```397WRONG — creating a service with circular dependencies398Service A: _service_dependencies: [15] (depends on B)399Service B: _service_dependencies: [10] (depends on A)400// Creates a circular reference — health checks and deployments deadlock.401402RIGHT — ensure the dependency graph is a DAG403Service A: _service_dependencies: [15] (depends on B)404Service B: _service_dependencies: [42] (depends on C)405// A → B → C is a valid acyclic chain.406407WRONG — resolving an approval without rationale or timestamp408{ "action": "update_item", "post_type": "mcp_ai_approval", "item_id": 88,409 "fields": { "_approval_status": "approved" } }410// Missing _approval_rationale and _approval_resolved_at — the audit trail is incomplete.411412RIGHT — fully document the resolution413{ "action": "update_item", "post_type": "mcp_ai_approval", "item_id": 88,414 "fields": { "_approval_status": "approved", "_approval_approver_id": "1",415 "_approval_rationale": "Change validated. No regressions in staging.", "_approval_resolved_at": "2026-08-12T14:30:00Z" } }416417WRONG — deleting an approval instead of cancelling418{ "action": "delete_item", "post_type": "mcp_ai_approval", "item_id": 88 }419// Permanent loss of the audit record. Compliance auditors cannot trace the decision.420421RIGHT — cancel to preserve the record422{ "action": "update_item", "post_type": "mcp_ai_approval", "item_id": 88,423 "fields": { "_approval_status": "cancelled", "_approval_rationale": "Deployment superseded by wf_99" } }424425WRONG — passing _approval_context as a JSON string426{ "fields": { "_approval_context": "{\"key\": \"value\"}" } }427// The field parser expects a native object, not an escaped string.428429RIGHT — pass _approval_context as a native object430{ "fields": { "_approval_context": { "key": "value" } } }431432WRONG — setting a service dependency to a non-existent post ID433{ "fields": { "_service_dependencies": [99999] } }434// Post ID 99999 doesn't exist — the dependency graph has a dangling reference.435436WRONG — jumping service status from "active" directly to "down"437{ "fields": { "_service_status": "down" } }438// Skips the "degraded" intermediate state, losing granularity for incident response.439```440441## Cross-References442443- Run `design-pro-workflow-builder` to create DAG workflows with approval nodes that reference `mcp_ai_approval` records.444- Run `design-pro-schedule-manager` to schedule recurring service health checks and approval queue reviews.445- Run `design-ai-assistant-admin` if an AI assistant triggers or resolves approval requests automatically.446- Run `design-crm` if service components are linked to client accounts or deals.447- Run `design-project-management` to track service-related tasks (deployments, migrations, incident response).448- Run `design-vault` to securely store service API keys and endpoint credentials referenced in service configs.449- Run `design-document-generation` to create deployment runbooks, incident reports, or approval summaries from service/approval data.450- Run `wp-security-audit` on any endpoint exposed by registered services — the registry itself does not secure the endpoints.451452## What This Skill Does NOT Cover453454- Actual service implementation (code, containers, infrastructure) — this skill manages the *registry*, not the services themselves.455- Workflow builder DAG design — use `design-pro-workflow-builder` for node configuration and approval node placement.456- Health check execution engine — the Cron/Worker system performs checks; this skill covers the configuration and status interpretation.457- Service monitoring dashboards (Grafana, Datadog) — use external observability tools for real-time metrics.458- Approval notification delivery (email, SMS, Slack) — use `design-communications` and `design-email-marketing` for notification channels.459- API key management for registered services — use `design-vault` for credential storage.460- WordPress plugin/service discovery — use `get_update_status` and `nv_oos_console_agent_get_environment_status` for plugin-level health.461462## References463464- NV oOS Pro Toolkit Services admin page: `/wp-admin/admin.php?page=nvoos-pro-toolkit-services`465- NV oOS Pro Toolkit Approvals admin page: `/wp-admin/admin.php?page=nvoos-pro-toolkit-approvals`466- `toolkit_cpt` MCP tool — the primary interface for all service and approval operations.467- Pro Workflow Builder approval node: uses `mcp_ai_approval` records as gates.468- Semantic versioning specification: [semver.org](https://semver.org)