$ loading_
Create and maintain design docs for the OpenZL component registry.
The material indicates a prompt/documentation-only skill with no keys, no remote endpoints, and no stated code execution or data exfiltration capability, so overall risk is low. Caution is mainly limited to weak community signals and unknown maintenance, while the open-source nature helps reduce supply-chain risk.
The material explicitly states that no keys or environment variables are required. There is no request for API tokens, account credentials, or local sensitive secrets, so credential exposure and abuse risk appears low.
No remote endpoints are declared, and the system classifies it as prompt-only. There is no indication that it sends user data to external services or connects to third-party hosts.
Based on the provided description, this is a design-document/prompt skill for content under tests/registry, with no stated ability to spawn local processes, execute scripts, install dependencies, or invoke system commands.
The material only indicates relevance to the tests/registry directory and does not claim broad access to local files, databases, system resources, or write permissions beyond that scope.
The source points to an open-source GitHub repository, which is a positive factor because the code is theoretically auditable. However, the license is unspecified, it has 0 stars, maintenance status is unknown, and the README references an external file via a relative path, limiting visibility in the provided material; verify repository contents and recent maintenance before use.
Copy the install command and let the AI configure it · recommended for beginners
Please install the "openzl-component-registry" skill from askskill: 1. Download https://raw.githubusercontent.com/facebook/openzl/dev/.claude/skills/openzl-component-registry/SKILL.md 2. Save it as ~/.claude/skills/openzl-component-registry/SKILL.md 3. Reload skills and tell me it's ready
Please add design documentation for the OpenZL component registry under tests/registry, covering the directory structure, component registration flow, naming conventions, and constraints for adding new components.
A clear design document draft describing registry structure and maintenance rules.
I just changed the component definition format in tests/registry. Please update the related design documentation, highlighting the changes, compatibility impact, and migration guidance.
Updated design documentation reflecting the new format, its impact, and migration guidance.
Please write a design overview of the tests/registry component registry for new developers, helping them quickly understand its purpose, key files, and common editing workflows.
An onboarding-friendly overview that helps new contributors understand the component registry quickly.
@../../../tests/registry/README.md
Design, modify, and review OpenZL codecs with consistent patterns and requirements.
Create benchmark scenarios for new openzl codec nodes in unitBench.
Write and run Markdown-driven end-to-end tests for Relay apps.
Get idiomatic Relay guidance for React code, debugging, and code reviews.
Apply the right commit prefix, reviewer, and test plan for code changes.
Debug Pysa false negatives by comparing outputs and locating lost taint flows.
Create and maintain screenshot test fixtures for UI components effectively.
Create, validate, and render deterministic .zen design docs to PNG or PDF.
Fetch glasz spec files from GitHub to answer feature and acceptance questions.
Build, version, audit financial models, and export them to Excel.
Handle UI changes, fixtures, screenshots, and visual testing in component explorer projects.
Search the EU component library docs and retrieve code recipes fast.