element_assistant

Generates Rierino SYSTEM element JSON configurations from the platform element catalog.

1|Updated Mar 27, 2026
One-click install
npx skills add https://github.com/rierino-open/rierino-claude-plugin --skill element-assistant-rierino-open
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: element_assistant
Source: https://github.com/rierino-open/rierino-claude-plugin/tree/main/development/skills/element_assistant
Command: npx skills add https://github.com/rierino-open/rierino-claude-plugin --skill element-assistant-rierino-open

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Manually writing Rierino SYSTEM element configurations risks invalid settings keys, wrong system types, and malformed JSON. This Skill produces valid Element JSON objects whose settings strictly match the platform's live element type catalog. ## Core Features & Use Cases - Catalog-Driven Generation: Fetches the element type catalog via the Rierino MCP server before generating, so only real system types and schema-defined settings are used. - Schema-Compliant Settings: Handles required fields, conditional rules (allOf/if/then), authentication methods, and pattern parameters like header.[header] or auth.claim.*. - Placeholder Conventions: Emits standardized placeholders for sensitive credentials (#{{...}}) and non-sensitive values (${{...}}). - Use Case: Ask for a SYSTEM element connecting to your SAP sandbox with a given URL, and receive a ready-to-use raw JSON object with the correct REST type, id format, and settings. ## Quick Start Create a SYSTEM element for our SAP sandbox at https://sandbox.api.sap.com.

Frequently Asked Questions about element_assistant

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a Rierino SYSTEM element configuration?▼

Describe the external system you want to connect, such as an SAP sandbox URL or a MongoDB instance. The Skill fetches the element type catalog from the Rierino MCP server and outputs a raw JSON element with the correct type, id, and schema-valid settings.

What system types does the Rierino element configuration support?▼

Supported types come only from the live element catalog returned by the State_GetAll_element_parameter_write tool, including REST, MongoDB, Elasticsearch, and Kafka. Types are never invented; if the catalog call fails, generation stops.

How are credentials handled in generated element settings?▼

Sensitive values like secrets use the #{{rierino.system.[alias].[field]}} placeholder, while non-sensitive values like URLs use ${{rierino.system.[alias].[field]}}. Authentication uses method-specific auth.* settings from the catalog schema rather than raw headers.

Why does the generated element JSON omit some optional settings?▼

Optional fields are only emitted when explicitly provided by the user, required by an active conditional rule, or needed to materialize a catalog-defined default. This keeps configurations minimal and compliant with the schema.

Can I use pattern parameters like header.[header] in element settings?▼

Yes, pattern parameters act as templates that are instantiated with real names, such as header.Authorization or auth.claim.user. Wildcard placeholders like [header] or * are never emitted literally in the final JSON.