Review production commands, inputs, and catalogs for Automation Pilot. Validates file structure, naming conventions, security requirements, mandatory patterns, and best practices. Use when reviewing .command.json, .input.json, or .catalog.json files.
Standardmäßig ist der Prompt ausgewählt, der zuerst die Quelle prüft. Sie können zu einem direkten Befehl wechseln oder eine lokale Kopie herunterladen.
Quelldateien prüfen
Lesen Sie SKILL.md und alle von SkillsMP angezeigten Begleitdateien, bevor Sie sich für eine Installation entscheiden.
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Ein direkter Befehl überspringt den Prüf-Prompt. Prüfen Sie die Quelle, bevor Sie ihn ausführen.
Review production commands, inputs, and catalogs for Automation Pilot. Validates file structure, naming conventions, security requirements, mandatory patterns, and best practices. Use when reviewing .command.json, .input.json, or .catalog.json files.
Code Review
Validate production commands meet structural, security, and quality standards.
AI Assistant Guidelines
⚠️ CRITICAL - When reviewing as an AI assistant:
DO NOT suggest or make any changes to expressions, response body transformers, or execution properties unless there is a clear error
Review comments should be added ONLY when there is a concern, warning, or an issue. When something is fine, do not add comments or suggest changes
Never write code comments in the properties fields of the commands
Do not add newline at end of a file - files should end without trailing newline
Flag violations immediately - critical issues (file structure, security, naming) must be caught
⚠️ JSON FILES DO NOT SUPPORT COMMENTS:
NEVER suggest adding // or /* */ comments - JSON syntax doesn't allow comments
NEVER suggest documenting status codes inline - this would break the JSON
Standard retry status codes are well-known - do not ask to document them:
-1 = Network/connection failure (standard in this codebase)
408 = Request Timeout
429 = Too Many Requests
500, 502, 503, 504 = Server errors
If documentation is needed, it belongs in SKILL.md files, not in JSON
❌ WRONG - Never suggest this:
// Consider defining these in a comment"expression":"$([408, 429, -1] | filter(...))"
✅ CORRECT - This pattern is standard and needs no comment:
Name exceeds 32 characters (e.g., testDelayedVoidWithDynamicMessage = 35 chars)
Wrong case (e.g., create_directory instead of CreateDirectory)
File name doesn't match JSON name
Data Types and Constraints
Validate input/output key definitions:
Correct data types used: array, string, object, number, boolean
Optional input keys have default values when appropriate
allowedValues, suggestedValues, allowedValuesFromInputKeys, suggestedValuesFromInputKeys exist but should only be present when needed
Region inputs must use allowedValuesFromInputKeys: CF regions → ["metadata-sapcp:CfRegionData:1"], Neo regions → ["metadata-sapcp:NeoRegionData:1"]
Example:
{"timeout":{"type":"number","sensitive":false,"required":false,"minSize":null,"maxSize":null,"minValue":null,"maxValue":null,"defaultValue":"5","defaultValueFromInput":null,"description":"Request timeout in seconds"}}
Security Requirements (CRITICAL)
Mandatory Sensitive Flags
These fields MUST have "sensitive": true:
"password":{"type":"string","sensitive":true,"required":true,"description":"The password for the specified technical user or the client secret for the specified OAuth 2.0 client ID to be used for authentication. Related input keys: 'user' or 'tokenUrl'"}
Fields requiring sensitive flag:
password
clientSecret
refreshToken
serviceKey
Any field containing credentials, tokens, or secrets
Input Data References (valueFrom Pattern)
Sensitive data should be stored in Input definitions and referenced:
Pattern 1: Load Entire Input (when you need multiple fields)
"values":[{"alias":"TechnicalUser","valueFrom":{"inputReference":"OQ-<<<TENANT_ID>>>:TechnicalUser:1","inputKey":null// null = load all fields}}]// Access: $(.TechnicalUser.user), $(.TechnicalUser.password)
Pattern 2: Load Specific Field
"values":[{"alias":"Password","valueFrom":{"inputReference":"OQ-<<<TENANT_ID>>>:ServiceAccount:1","inputKey":"password"// Load only this field}}]// Access: $(.Password)
Pattern 3: Direct Input (production commands)
"inputKeys":{"password":{"type":"string","sensitive":true,"required":true}}// Access in executors: $(.execution.input.password)
⚠️ All descriptions of the following parameters must be one of these exact sentences or start with them. No variations, alternatives, or creative rewording allowed for these Input and Output keys!
{"id":"OQ-<<<TENANT_ID>>>:TechnicalUser:1","name":"TechnicalUser","description":"Technical user credentials for testing","catalog":"OQ-<<<TENANT_ID>>>","version":1,"keys":{"password":{"type":"string","sensitive":true,"description":null},"user":{"type":"string","sensitive":false,"description":null},"mail":{"type":"string","sensitive":false,"description":null}},"values":{"password":"","user":"technical-user","mail":"technical.user@example.com"}}
