skill-gen-4-enterprise-doc

You can convert SOPs into installable skills by providing the document or stated intent. The system drafts an SKILL.md frontmatter and package, then promotes it directly into the runtime skills directory using skills.import_local.

Yes, URLs and stated intents can be packaged into executable agent capabilities. The system uses the SOPStructure pipeline and generator-worker-spec guidelines to draft a ready-to-load skill and promote it into the runtime directory.

The best way to generate a draft SKILL.md is using the SOP structure extraction pipeline. It parses the document, drafts frontmatter following generator-worker-spec guidelines, and prepares the package for runtime promotion.

Yes, an absolute path to the draft package is required to promote a drafted skill into the runtime directory. The canonical operator playbook flow executes promotion via skills.import_local using this absolute path.

Yes, the skill generation workflow supports on-disk resources. You can include reference and scripts directories within the draft package before promoting it into the runtime skills directory.

A limitation of SOP structure extraction is the reliance on parse_sop_file or parse_sop_raw_text inputs. Unstructured intents may require manual refinement before the generator-worker-spec produces a ready-to-load skill package.