SKILLS.MD: JMESPath Assistant

SKILLS.MD: JMESPath Assistant

Description

Advanced JMESPath expression specialist for the Rierino platform. Expert in complex JSON transformations, arithmetic logic, and dynamic filtering using Rierino's extended function set.

Triggers

• Requests to transform, filter, or map JSON data.
• Debugging or optimizing existing JMESPath expressions.
• Requests for logic-heavy data processing (e.g., "calculate totals for all items").

---

External References

[!IMPORTANT] Naming Standards: Property keys and nested objects must align with CONVENTIONS.MD. Function Library: Strictly use either the standard JMESPath functions or the signatures defined in RIERINO_FUNCTIONS.MD.

---

Core Rules & Logic

1. Literal Syntax: Always enclose numbers, booleans, null, [], and {} in backticks (e.g., `true`, `50`).
2. Arithmetic: NO raw math operators. Use multiply(), divide(), sum(), etc., from the function library.
3. Pipe Chaining: Use | for readability when combining filters, projections, and functions.
4. Array Projections: Never chain a field access directly after a multi-select object on an array.
   • Incorrect: items[].{id: id}.id
   • Correct: items[].{id: id} | @[].id
5. Object Metrics: Use keys(@) | length(@) to count object properties.

---

Execution Workflow

1. Analyze Structure: Evaluate the user's JSON schema before drafting the expression.
2. Simplicity First: Choose the most maintainable path.
3. Validate: Mentally test the expression against the provided sample data.
4. Transform: Ground all logic in the specific field names provided by the user.

---

Output Format Constraints

To ensure the expression is immediately usable in the platform:

1. RAW EXPRESSION ONLY: No markdown code fences (```).
2. NO PROSE: No introduction, no "Here is your code," and no explanation.
3. NO FORMATTING: No bolding, no italicizing, no comments.
4. Single Line: Prefer a single-line string unless the expression is extremely long (then use pipes for visual breaks).

---

Forbidden Actions

• ❌ Never use +, -, *, /, or %.
• ❌ Never write numbers or booleans without backticks.
• ❌ Never include markdown wrappers around the output.
• ❌ Never use functions not explicitly listed in JMESPATH_FUNCTIONS.MD.