op-desc-generation

Generate Ascend operator description JSON files from templates.

33|51|Updated Mar 12, 2026
One-click install
npx skills add https://github.com/Just-it/AscendOpGenAgent --skill op-desc-generation
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: op-desc-generation
Source: https://github.com/Just-it/AscendOpGenAgent/tree/main/skills/op_desc_generation
Command: npx skills add https://github.com/Just-it/AscendOpGenAgent --skill op-desc-generation

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Generate operator description JSON files from templates to accelerate Ascend operator development by providing structured op descriptors for downstream code generation.

Core Features & Use Cases

  • Template-driven generation of op_desc.json from op_desc_template.json and the example file layer_norm_op_desc.json in references
  • Auto-fill fields such as op_name, category, description, shape_info, and attributes
  • Save outputs to output/{op_name}/{op_name}_op_desc.json for easy downstream integration

Quick Start

Provide an operator name and required details to generate the corresponding op_desc.json from the template.

Frequently Asked Questions about op-desc-generation

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

FAQPage Schema
How do I generate an op_desc.json file for Ascend operator development?

To generate an op_desc.json file for Ascend operator development, provide an operator name and required details to the skill. It reads a template and example description, infers operator metadata, and outputs a structured JSON descriptor containing op_name, category, description, shape_info, and attributes.

What is an operator description JSON and why is it needed?

An operator description JSON is a structured descriptor file needed to accelerate Ascend operator development. It provides essential metadata like op_name, category, description, shape_info, and attributes for downstream code generation processes.

Can I use a template to automate operator metadata generation for Ascend?

Yes, you can automate operator metadata generation for Ascend using a template. The skill reads op_desc_template.json and an example file, infers the required metadata, and auto-fills fields to create the final operator description JSON.

What's the best way to structure shape_info and attributes for Ascend operators?

The best way to structure shape_info and attributes for Ascend operators is by using a standardized template. The skill infers this operator metadata from an example description file and automatically populates these fields in the output JSON descriptor.

Where should the generated operator description JSON be saved for downstream integration?

The generated operator description JSON should be saved to output/{op_name}/{op_name}_op_desc.json. This specific directory structure ensures easy downstream integration during Ascend operator development.