component-script-designer
/component-script-designer
Use when reading or modifying a script file under `scripts/` for the exact SmartCMP component selected by an embedded component-editor page Context, with rules routed by component resource type.
- Author
- CloudChef ↗
- Repository
- atlasclaw-providers ↗
- Licence
- Apache-2.0
- Last repository change
- 03.09.2026
Assessment and security
- Files in this package
- 3
- Scripts
- 1
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 03.09.2026, without references to retired models or APIs.
Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.
- 1 scripts in this package. Review them before installing, as Claude may execute them.
Scripts: scripts/read_current_component_file.py
What it does and when to use it
Use when reading or modifying a script file under `scripts/` for the exact SmartCMP component selected by an embedded component-editor page Context, with rules routed by component resource type.
Original author description
Use when reading or modifying a script file under `scripts/` for the exact SmartCMP component selected by an embedded component-editor page Context, with rules routed by component resource type.
How it works
- Workflow
- Type Routing
- Safety
SKILL.md preview
---
name: "component-script-designer"
description: "Use when reading or modifying a script file under `scripts/` for the exact SmartCMP component selected by an embedded component-editor page Context, with rules routed by component resource type."
provider_type: "smartcmp"
instance_required: "true"
triggers:
- modify current component script
- improve component file
- update blueprint component script
- 修改当前组件脚本
- 完善组件库脚本
- 优化组件文件
use_when:
- User is interacting from a SmartCMP blueprint component editor
- User wants a complete replacement for one current component script file under `scripts/`
avoid_when:
- User wants to save, publish, upgrade, import, export, or delete a component
- User wants to create an unrelated component outside the current page Context
tool_current_name: "smartcmp_read_current_component_file"
tool_current_description: "Read the exact current SmartCMP component bound to page Context, list its files under `scripts/`, and return one complete selected script file. If file_path is omitted, a sole script file is selected automatically; multiple script files are listed for exact selection. The tool never writes to CMP."
tool_current_entrypoint: "scripts/read_current_component_file.py:read_current_component_file"
tool_current_groups:
- cmp
- component-script-designer
tool_current_capability_class: "provider:smartcmp"
tool_current_priority: 115
tool_current_result_mode: "llm"
tool_current_parameters: |
{
"type": "object",
"properties": {
"file_path": {
"type": "string",
"description": "Exact path under `scripts/` from the current component's blueprintFiles list. Omit when the component contains only one script file."
}
},
"additionalProperties": false
}
---
# component-script-designer
Read one file from the current saved component and produce a complete replacement for manual copying.
## Workflow
1. Call `smartcmp_read_current_component_file`. If several files are returned and the user did not identify one, ask for the exact listed `file_path`; never guess.
2. Use `componentFamily` to select the matching rules in `references/component-script-rules.md`.
3. Apply only the requested change and preserve the selected file's entrypoints, parameters, return shape, runtime version, line-ending expectations, and unrelated logic.
4. Return the exact file path and the complete updated file in one fenced block. Never return only a diff, partial snippet, or ellipsis placeholder.
5. State that the output is for manual review and copying into CMP. Do not claim that the component was saved, published, upgraded, or deployed.
## Type Routing
- `exporter`: Prometheus exporter and monitoring-agent components.
- `integration`: `resource.integration.*`.
- `software`: `resource.software.*`.
- `resource`: `resource.iaas.*`, `resource.paas.*`, and `resource.caas.*`.
- Unknown families fail closed; do not apply a different component family's assumptions.
## Safety
- No component write, publish, upgrade, import, export, or execution APIs.
- Do not invent third-party endpoints, cloud SDK fields, runtime variables, or credentials.
- Read `references/component-script-rules.md` before producing component code.
Files in this package (3)
- SKILL.md 3 KB
- references/component-script-rules.md 6 KB
- scripts/read_current_component_file.py 5 KB
Versions
The database has no other skills named component-script-designer.
Database snapshot: 13.11.2026 · package version 7d87c1ed8001 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 90script-designer
Use when reading or modifying the script content of the exact SmartCMP script definition selected by an embedded script-editor page Context. - 90optimization-policy-designer
Use when reading or modifying the rule content and editable definition of the exact SmartCMP cost-optimization policy selected by an embedded policy-editor page Context. - 100b2c-page-designer
Define Page Designer page types and component types with regions, attributes, and rendering scripts. Use this skill whenever the user needs to create a new page or component type, configure regions with allowed component constraints, define attribute_definition_groups, debug why… - 100component-docs-header
This skill should be used when the user asks to "add a component header", "add a ComponentHeader to the X docs page", "change the header demo for X", or otherwise discusses the live demo shown at the top of a component's usage page in the `docs/` site. For a whole new docs page,… - 100aem-component
Find all source files, AEM pages and dialog fields for an AEM component. Use for 'where is component X?', 'what files for hero?', 'find component'. - 95gameobject-component-get
Get detailed information about a specific Component on a GameObject. Returns component type, enabled state, and optionally serialized fields and properties. Use this to inspect component data before modifying it. Use 'gameobject-find' tool to get the list of all components on the GameObject.