automation-pilot-content-management-via-api
Skill1 starsChanged 4 months agoMITView on GitHub
Manage SAP Automation Pilot content (commands, catalogs, inputs) via Content API. Use when importing or exporting commands, listing catalogs, or managing automation content programmatically.
- Sends data out
In this repository413 other files it gives its agents.
- .agents/AGENTS.mdAGENTS.md
- AGENTS.mdAGENTS.md
- .codex/AGENTS.mdAGENTS.md
- .cursor/AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- sap-router-skillCopilot instructions
- .cursor/rules/sap-router.mdcCursor rule
- abap-cloud-migrationSkill
- abap-cloudSkill
- abap-code-patternsSkill
- abap-code-reviewSkill
- abap-docs-referenceSkill
- abapgitSkill
- abapSkill
- abap-snippetSkill
- abap-sql-amdpSkill
- abap-system-infoSkill
- abap-unit-testingSkill
- arc-1-skillsSkill
- atc-cloudificationSkill
- authorization-iamSkill
- automation-pilot-catalog-explorerSkill
- automation-pilot-command-generationSkill
- automation-pilot-command-reviewSkill
- automation-pilot-debuggerSkill
- automation-pilot-executions-apiSkill
- automation-pilot-executor-executescriptSkill
- automation-pilot-executor-httprequestSkill
- automation-pilot-mcp-server-generationSkill
- automation-pilot-scheduled-executions-apiSkill
- badi-enhancementSkill
- btp-abap-environmentSkill
- btp-best-practicesSkill
- btp-build-work-zoneSkill
- btp-business-application-studioSkill
- btp-ciasSkill
- btp-cloud-foundrySkill
- btp-cloud-identitySkill
- btp-cloud-loggingSkill
- btp-cloud-platformSkill
- btp-cloud-transport-managementSkill
- btp-connectivitySkill
- btp-developer-guideSkill
- btp-diagram-generatorSkill
- btp-integration-suiteSkill
- btp-job-schedulingSkill
- btp-master-data-integrationSkill
- btp-service-managerSkill
- cap-add-remote-serviceSkill
- cap-developerSkill
- cap-triviaSkill
- capture-answerSkill
- cap-upgradeSkill
- cds-view-entitiesSkill
- claude-abap-skillsSkill
- claude-memSkill
- clean-abapSkill
- context-modeSkill
- cpi-iflow-developmentSkill
- engine-cap-developmentSkill
- The first 60 shown.
The file
Show its rules and text
We split this skill into the rules it gives an agent
13 rules. About 0 are common, 5 are distinctive, and 8 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
Distinctive · estimate
This author's own choices. Worth a look.
8
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 42
Ensure curl is available in your environment.
- Very specific: line 48
When creating or updating inputs via the API, every entry in values and defaultValue must be a JSON string, regardless of the declared type …
- Distinctive: line 340
Update only specific values without replacing the entire input:
- Very specific: line 512
Separate inputs by environment: - Create distinct inputs for dev/staging/prod
- Very specific: line 513
Mark sensitive values: - Always set "sensitive": true for passwords, tokens, and keys
- Distinctive: line 613
Always check the response for error messages:
- Distinctive: line 653
Check if the command already exists by reading its ID from the file and doing a GET
- Very specific: line 654
If it exists: PUT to /api/v1/commands/$COMMAND_ID.
- Very specific: line 679
Solution: Verify AUTOPI_USERNAME and AUTOPI_PASSWORD are correct for the target hostname.
- Very specific: line 683
Solution: Check the Required Permissions table — everything needs Write.
- Distinctive: line 687
Solution: Use the Upsert Pattern — GET first to check existence, then PUT if found or POST if not.
- Distinctive: line 691
Solution: Check the response body for the specific field that failed.
- Very specific: line 695
Solution: Verify the ID format is catalog:name:version and that the catalog and command exist.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
SAP Automation Pilot Content API Management
This skill manages catalogs, commands, and inputs in SAP Automation Pilot using the Content API.
Command Release Policy
⚠️ Commands deploy in DRAFT state. Never release automatically — only when the user explicitly requests it and the command has been tested. See ../automation-pilot-command-generation/SKILL.md for the full policy.
Naming Conventions
| Type | Convention | Example |
| Commands | PascalCase | RestartCfApp, GetHanaInstance |
| Inputs | PascalCase | BtpCredentials, JiraConfig |
| Catalogs | kebab-case | my-automations-xxx |
Names must not contain spaces (causes API failures with URL encoding).
Prerequisites
- Set the following required environment variables:
export AUTOPI_HOSTNAME="emea.autopilot.cloud.sap"
export AUTOPI_USERNAME="your-username"
export AUTOPI_PASSWORD="your-password"
export AUTOPI_DEFAULT_CATALOG="mycommands-<<<TENANT_ID>>>"Supported hostnames:
emea.autopilot.cloud.sap(default - Europe)aus.autopilot.cloud.sap(Australia)apac.autopilot.cloud.sap(Asia Pacific)amer.autopilot.cloud.sap(Americas)ksa.autopilot.cloud.sap(Saudi Arabia)
- Ensure
curlis available in your environment.
Values Are Always Strings on the Wire
When creating or updating inputs via the API, every entry in values and defaultValue must be a JSON string, regardless of the declared type in keys.
Declared type | Wire representation |
string | "my-app" |
number | "42" |
boolean | "true" |
array | "[\"a\",\"b\"]" |
object | "{\"url\":\"...\",\"user\":\"...\"}" |
This also applies to inputValues on trigger and schedule endpoints — every value must be a string on the wire. The runtime converts it to the declared type inside the executor.
Catalogs
List Catalogs
# List all catalogs owned by the tenant
curl -s -u "$AUTOPI_USERNAME:$AUTOPI_PASSWORD" "https://$AUTOPI_HOSTNAME/api/v1/catalogs?own=true"
# List catalogs provided by SAP
curl -s -u "$AUTOPI_USERNAME:$AUTOPI_PASSWORD" "https://$AUTOPI_HOSTNAME/api/v1/catalogs?provided=true"
# List all catalogs (owned + provided)
curl -s -u "$AUTOPI_USERNAME:$AUTOPI_PASSWORD" "https://$AUTOPI_HOSTNAME/api/v1/catalogs"
# List catalogs filtered by tag
curl -s -u "$AUTOPI_USERNAME:$AUTOPI_PASSWORD" "https://$AUTOPI_HOSTNAME/api/v1/catalogs?tag=environment:production"Get Catalog by ID
CATALOG_ID="mycatalog-xxx"
curl -s -u "$AUTOPI_USERNAME:$AUTOPI_PASSWORD" "https://$AUTOPI_HOSTNAME/api/v1/catalogs/$CATALOG_ID"Create Catalog
curl -s -X POST \
-u "$AUTOPI_USERNAME:$AUTOPI_PASSWORD" \
-H "Content-Type: application/json" \
-d '{
"name": "my-catalog",
"description": "My custom catalog for automation commands",
"tags": {
"environment": "development"
}
}' \
"https://$AUTOPI_HOSTNAME/api/v1/catalogs"Update Catalog
CATALOG_ID="mycatalog-xxx"
curl -s -X PUT \
-u "$AUTOPI_USERNAME:$AUTOPI_PASSWORD" \
-H "Content-Type: application/json" \
-d '{
"description": "Updated description",
"tags": {
"environment": "production"
}
}' \
"https://$AUTOPI_HOSTNAME/api/v1/catalogs/$CATALOG_ID"Delete Catalog
Note: Catalog must be empty (no commands or inputs) before deletion.
CATALOG_ID="mycatalog-xxx"
curl -s -X DELETE -u "$AUTOPI_USERNAME:$AUTOPI_PASSWORD" "https://$AUTOPI_HOSTNAME/api/v1/catalogs/$CATALOG_ID"Commands
List Commands
# List all commands in a catalog
CATALOG="mycatalog-xxx"
curl -s -u "$AUTOPI_USERNAME:$AUTOPI_PASSWORD" "https://$AUTOPI_HOSTNAME/api/v1/commands?catalog=$CATALOG"
# List commands with design-time issues
curl -s -u "$AUTOPI_USERNAME:$AUTOPI_PASSWORD" "https://$AUTOPI_HOSTNAME/api/v1/commands?catalog=$CATALOG&includeIssues=true"
# List commands by tag
curl -s -u "$AUTOPI_USERNAME:$AUTOPI_PASSWORD" "https://$AUTOPI_HOSTNAME/api/v1/commands?tag=type:monitoring"
# List only command IDs (lightweight)
curl -s -u "$AUTOPI_USERNAME:$AUTOPI_PASSWORD" "https://$AUTOPI_HOSTNAME/api/v1/commands/ids?catalog=$CATALOG"Get Command by ID
Command ID format: catalog:name:version
COMMAND_ID="mycatalog-xxx:MyCommand:1"
curl -s -u "$AUTOPI_USERNAME:$AUTOPI_PASSWORD" "https://$AUTOPI_HOSTNAME/api/v1/commands/$COMMAND_ID"Create/Upload Command
Upload a command from a .command.json file:
COMMAND_FILE="path/to/MyCommand.command.json"
# Create the command
curl -s -X POST \
-u "$AUTOPI_USERNAME:$AUTOPI_PASSWORD" \
-H "Content-Type: application/json" \
-d @"$COMMAND_FILE" \
"https://$AUTOPI_HOSTNAME/api/v1/commands"Create command inline:
curl -s -X POST \
-u "$AUTOPI_USERNAME:$AUTOPI_PASSWORD" \
-H "Content-Type: application/json" \
-d '{
"name": "MyCommand",
"catalog": "mycatalog-xxx",
"description": "My custom command",
"version": 1,
"inputKeys": {
"message": {
"type": "string",
"description": "Message to process",
"required": true
}
},
"outputKeys": {
"result": {
"type": "string",
"description": "Processing result"
}
},
"configuration": null,
"tags": {}
}' \
"https://$AUTOPI_HOSTNAME/api/v1/commands"Update Command
COMMAND_ID="mycatalog-xxx:MyCommand:1"
COMMAND_FILE="path/to/MyCommand.command.json"
curl -s -X PUT \
-u "$AUTOPI_USERNAME:$AUTOPI_PASSWORD" \
-H "Content-Type: application/json" \
-d @"$COMMAND_FILE" \
"https://$AUTOPI_HOSTNAME/api/v1/commands/$COMMAND_ID"Delete Command
COMMAND_ID="mycatalog-xxx:MyCommand:1"
curl -s -X DELETE -u "$AUTOPI_USERNAME:$AUTOPI_PASSWORD" "https://$AUTOPI_HOSTNAME/api/v1/commands/$COMMAND_ID"Release Command
⚠️ USE ONLY IF THE USER EXPLICITLY REQUESTED IT
Release a draft command:
COMMAND_ID="mycatalog-xxx:MyCommand:1"
curl -s -X PUT -u "$AUTOPI_USERNAME:$AUTOPI_PASSWORD" "https://$AUTOPI_HOSTNAME/api/v1/commands/$COMMAND_ID/release"Deprecate Command
Mark a command as deprecated:
COMMAND_ID="mycatalog-xxx:MyCommand:1"
curl -s -X PUT -u "$AUTOPI_USERNAME:$AUTOPI_PASSWORD" "https://$AUTOPI_HOSTNAME/api/v1/commands/$COMMAND_ID/deprecate"Restore Command
Restore a deprecated command:
COMMAND_ID="mycatalog-xxx:MyCommand:1"
curl -s -X PUT -u "$AUTOPI_USERNAME:$AUTOPI_PASSWORD" "https://$AUTOPI_HOSTNAME/api/v1/commands/$COMMAND_ID/restore"Bulk Create Commands
Upload multiple commands at once:
curl -s -X POST \
-u "$AUTOPI_USERNAME:$AUTOPI_PASSWORD" \
-H "Content-Type: application/json" \
-d '{
"commands": [
{"name": "Cmd1", "catalog": "mycatalog-xxx", ...},
{"name": "Cmd2", "catalog": "mycatalog-xxx", ...}
]
}' \
"https://$AUTOPI_HOSTNAME/api/v1/bulk/commands"Inputs
List Inputs
# List inputs in a catalog
CATALOG="mycatalog-xxx"
curl -s -u "$AUTOPI_USERNAME:$AUTOPI_PASSWORD" "https://$AUTOPI_HOSTNAME/api/v1/inputs?catalog=$CATALOG"
# List inputs by tag
curl -s -u "$AUTOPI_USERNAME:$AUTOPI_PASSWORD" "https://$AUTOPI_HOSTNAME/api/v1/inputs?tag=type:credentials"Get Input by ID
Input ID format: catalog:name:version
INPUT_ID="mycatalog-xxx:MyInput:1"
curl -s -u "$AUTOPI_USERNAME:$AUTOPI_PASSWORD" "https://$AUTOPI_HOSTNAME/api/v1/inputs/$INPUT_ID"Create Input
curl -s -X POST \
-u "$AUTOPI_USERNAME:$AUTOPI_PASSWORD" \
-H "Content-Type: application/json" \
-d '{
"name": "MyCredentials",
"catalog": "mycatalog-xxx",
"description": "Service credentials",
"version": 1,
"keys": {
"username": {
"type": "string",
"description": "Service username",
"sensitive": false
},
"password": {
"type": "string",
"description": "Service password",
"sensitive": true
}
},
"values": {
"username": "<your-username>",
"password": "<your-password>"
},
"tags": {
"type": "credentials"
}
}' \
"https://$AUTOPI_HOSTNAME/api/v1/inputs"Update Input (Full)
INPUT_ID="mycatalog-xxx:MyInput:1"
curl -s -X PUT \
-u "$AUTOPI_USERNAME:$AUTOPI_PASSWORD" \
-H "Content-Type: application/json" \
-d '{
"name": "MyCredentials",
"catalog": "mycatalog-xxx",
"description": "Updated credentials",
"version": 1,
"keys": {...},
"values": {...}
}' \
"https://$AUTOPI_HOSTNAME/api/v1/inputs/$INPUT_ID"Update Input (Partial - Values Only)
Update only specific values without replacing the entire input:
INPUT_ID="mycatalog-xxx:MyInput:1"
curl -s -X PATCH \
-u "$AUTOPI_USERNAME:$AUTOPI_PASSWORD" \
-H "Content-Type: application/merge-patch+json" \
-d '{
"values": {
"password": "<your-new-password>"
}
}' \
"https://$AUTOPI_HOSTNAME/api/v1/inputs/$INPUT_ID"Delete Input
INPUT_ID="mycatalog-xxx:MyInput:1"
curl -s -X DELETE -u "$AUTOPI_USERNAME:$AUTOPI_PASSWORD" "https://$AUTOPI_HOSTNAME/api/v1/inputs/$INPUT_ID"Release Input
⚠️ USE ONLY IF THE USER EXPLICITLY REQUESTED IT
INPUT_ID="mycatalog-xxx:MyInput:1"
curl -s -X PUT -u "$AUTOPI_USERNAME:$AUTOPI_PASSWORD" "https://$AUTOPI_HOSTNAME/api/v1/inputs/$INPUT_ID/release"Deprecate Input
INPUT_ID="mycatalog-xxx:MyInput:1"
curl -s -X PUT -u "$AUTOPI_USERNAME:$AUTOPI_PASSWORD" "https://$AUTOPI_HOSTNAME/api/v1/inputs/$INPUT_ID/deprecate"Restore Input
INPUT_ID="mycatalog-xxx:MyInput:1"
curl -s -X PUT -u "$AUTOPI_USERNAME:$AUTOPI_PASSWORD" "https://$AUTOPI_HOSTNAME/api/v1/inputs/$INPUT_ID/restore"Bulk Create Inputs
curl -s -X POST \
-u "$AUTOPI_USERNAME:$AUTOPI_PASSWORD" \
-H "Content-Type: application/json" \
-d '{
"inputs": [
{"name": "Input1", "catalog": "mycatalog-xxx", ...},
{"name": "Input2", "catalog": "mycatalog-xxx", ...}
]
}' \
"https://$AUTOPI_HOSTNAME/api/v1/bulk/inputs"Working with Inputs
Inputs are reusable parameter sets stored in Automation Pilot. They allow you to save credentials, configurations, or commonly-used values that can be referenced when triggering command executions.
Input Structure
{
"name": "MyCfCredentials",
"catalog": "mycatalog-xxx",
"description": "CF credentials for eu10 region",
"version": 1,
"keys": {
"region": { "type": "string", "sensitive": false },
"user": { "type": "string", "sensitive": false },
"password": { "type": "string", "sensitive": true }
},
"values": {
"region": "cf-eu10",
"user": "technical-user",
"password": "<your-password>"
},
"tags": {}
}- keys: Defines the schema (type and sensitivity) for each value
- values: The actual stored values
- sensitive: true: Value is masked in logs and UI
Common Input Patterns
CF Credentials (for applm-sapcp, cf-sapcp commands)
{
"name": "CfCredentials-EU10",
"catalog": "mycatalog-xxx",
"description": "Cloud Foundry credentials for EU10",
"version": 1,
"keys": {
"region": { "type": "string", "sensitive": false },
"user": { "type": "string", "sensitive": false },
"password": { "type": "string", "sensitive": true }
},
"values": {
"region": "cf-eu10",
"user": "cf-technical-user@example.com",
"password": "your-password"
}
}Service Key (for sm-sapcp, aicore-sapcp commands)
{
"name": "HanaCloudServiceKey",
"catalog": "mycatalog-xxx",
"description": "HANA Cloud service binding credentials",
"version": 1,
"keys": {
"serviceKey": { "type": "object", "sensitive": true }
},
"values": {
"serviceKey": "{\"url\":\"https://hana-instance.hana.cloud.sap\",\"user\":\"DBADMIN\",\"password\":\"<your-password>\",\"certificate\":\"...\"}"
}
}API Token (for jira-sapcp, github-sapcp commands)
{
"name": "JiraCredentials",
"catalog": "mycatalog-xxx",
"description": "JIRA API credentials",
"version": 1,
"keys": {
"host": { "type": "string", "sensitive": false },
"user": { "type": "string", "sensitive": false },
"password": { "type": "string", "sensitive": true }
},
"values": {
"host": "https://jira.example.com",
"user": "automation@example.com",
"password": "api-token-here"
}
}Kubernetes Config (for kubernetes-sapcp commands)
{
"name": "K8sClusterConfig",
"catalog": "mycatalog-xxx",
"description": "Kubernetes cluster kubeconfig",
"version": 1,
"keys": {
"kubeconfig": { "type": "object", "sensitive": true }
},
"values": {
"kubeconfig": "{\"apiVersion\":\"v1\",\"kind\":\"Config\",\"clusters\":[...],\"users\":[...],\"contexts\":[...]}"
}
}Best Practices
- Separate inputs by environment - Create distinct inputs for dev/staging/prod
- Mark sensitive values - Always set
"sensitive": truefor passwords, tokens, and keys - Use descriptive names - Include region/environment in the name (e.g.,
CfCredentials-EU10-Prod) - Keep inputs minimal - Store only reusable values; command-specific values go in
inputValuesat trigger time
Utility Patterns
Export Command to File
COMMAND_ID="mycatalog-xxx:MyCommand:1"
OUTPUT_FILE="MyCommand.command.json"
curl -s -u "$AUTOPI_USERNAME:$AUTOPI_PASSWORD" \
"https://$AUTOPI_HOSTNAME/api/v1/commands/$COMMAND_ID" > "$OUTPUT_FILE"
echo "Command exported to $OUTPUT_FILE"Upload All Commands from Directory
DIRECTORY="./commands"
for file in "$DIRECTORY"/*.command.json; do
echo "Uploading: $file"
curl -s -X POST \
-u "$AUTOPI_USERNAME:$AUTOPI_PASSWORD" \
-H "Content-Type: application/json" \
-d @"$file" \
"https://$AUTOPI_HOSTNAME/api/v1/commands"
doneCheck if Command Exists
COMMAND_ID="mycatalog-xxx:MyCommand:1"
STATUS=$(curl -s -o /dev/null -w "%{http_code}" \
-u "$AUTOPI_USERNAME:$AUTOPI_PASSWORD" \
"https://$AUTOPI_HOSTNAME/api/v1/commands/$COMMAND_ID")
if [[ "$STATUS" == "200" ]]; then
echo "Command exists"
elif [[ "$STATUS" == "404" ]]; then
echo "Command not found"
else
echo "Error: HTTP $STATUS"
fiCreate or Update Command (Upsert Pattern)
COMMAND_FILE="MyCommand.command.json"
COMMAND_ID="<catalog:name:version-from-file>"
# Check if exists
STATUS=$(curl -s -o /dev/null -w "%{http_code}" \
-u "$AUTOPI_USERNAME:$AUTOPI_PASSWORD" \
"https://$AUTOPI_HOSTNAME/api/v1/commands/$COMMAND_ID")
if [[ "$STATUS" == "200" ]]; then
echo "Updating existing command..."
curl -s -X PUT \
-u "$AUTOPI_USERNAME:$AUTOPI_PASSWORD" \
-H "Content-Type: application/json" \
-d @"$COMMAND_FILE" \
"https://$AUTOPI_HOSTNAME/api/v1/commands/$COMMAND_ID"
else
echo "Creating new command..."
curl -s -X POST \
-u "$AUTOPI_USERNAME:$AUTOPI_PASSWORD" \
-H "Content-Type: application/json" \
-d @"$COMMAND_FILE" \
"https://$AUTOPI_HOSTNAME/api/v1/commands"
fiError Handling
The API returns standard HTTP status codes:
| Code | Description |
200 | Success (GET, PUT) |
201 | Created (POST) |
204 | No Content (DELETE) |
400 | Bad request - invalid JSON or missing required fields |
401 | Unauthorized - invalid credentials |
403 | Forbidden - insufficient permissions |
404 | Not found - resource doesn't exist |
409 | Conflict - resource already exists or invalid state |
429 | Too many requests - rate limited |
500 | Internal server error |
503 | Service unavailable |
Always check the response for error messages:
RESPONSE=$(curl -s -w "\n%{http_code}" -u "$AUTOPI_USERNAME:$AUTOPI_PASSWORD" "https://$AUTOPI_HOSTNAME/api/v1/commands")
HTTP_CODE=$(echo "$RESPONSE" | tail -1)
BODY=$(echo "$RESPONSE" | head -n -1)
if [[ "$HTTP_CODE" != "200" && "$HTTP_CODE" != "201" ]]; then
echo "Error ($HTTP_CODE): $BODY"
exit 1
fi
echo "$BODY"Required Permissions
| Operation | Required Permission |
| List/Get resources | Read |
| Create/Update/Delete resources | Write |
Mandatory Description Patterns
⚠️ When creating or updating commands/inputs, use these exact description patterns for standard parameters.
See the complete authoritative list in ../automation-pilot-command-generation/references/description-patterns.md.
Examples
Example 1: Deploy a command from a JSON file
User: "Deploy this command to Automation Pilot"
- Check if the command already exists by reading its ID from the file and doing a GET
- If it exists: PUT to
/api/v1/commands/$COMMAND_ID; if not: POST to/api/v1/commands - Report success with the command ID from the response
Example 2: Export all commands from a catalog
User: "Export all commands from my catalog to files"
- GET
/api/v1/commands?catalog=$AUTOPI_DEFAULT_CATALOGto list all command IDs - For each ID, GET
/api/v1/commands/$COMMAND_IDand write the response to<CommandName>.command.json - Report how many files were exported and where
Example 3: Rotate credentials in an input
User: "Update the password in my JiraCredentials input"
- PATCH
/api/v1/inputs/mycatalog-xxx:JiraCredentials:1withContent-Type: application/merge-patch+json - Send only
{"values": {"password": "<new-value>"}}— do not replace the entire input - Confirm the update succeeded (HTTP 200)
Troubleshooting
Error: HTTP 401 Unauthorized
Cause: Invalid credentials.
Solution: Verify AUTOPI_USERNAME and AUTOPI_PASSWORD are correct for the target hostname.
Error: HTTP 403 Forbidden
Cause: The user lacks the required permission for the operation.
Solution: Check the Required Permissions table — everything needs Write.
Error: HTTP 409 Conflict on command or input create Cause: A resource with the same ID already exists. Solution: Use the Upsert Pattern — GET first to check existence, then PUT if found or POST if not.
Error: HTTP 400 Bad Request on command create Cause: Invalid JSON or a missing required field in the command definition. Solution: Check the response body for the specific field that failed.
Error: HTTP 404 on command update
Cause: The command ID in the request URL doesn't match any existing command.
Solution: Verify the ID format is catalog:name:version and that the catalog and command exist. Use GET first to confirm.
⚠️ CAUTION: DO NOT RELEASE COMMANDS & INPUTS IF NOT EXPLICITLY REQUESTED BY THE USER
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

