Catalog and plugin skills
Distinguish discovery starters from installed, owned instruction packages
You need a Semogram account with membership in the target workspace and access to a project in it. The Skills screen is opened from a project, while standalone skills belong to the workspace.
The Skills home shows installed packages and discovery starters. Installed skills combine editable standalone assets with enabled skill capabilities from workspace plugins. The source and read-only state determine how to change them.
Current catalog starters
| Starter | Purpose | Catalog identifier |
|---|---|---|
| Plan Reviewer | Review draft workflows and weak assumptions | plan-reviewer |
| Plugin Setup Guide | Clarify connector configuration and runtime setup | integration-setup |
| Run Ops Investigator | Investigate failed or partial runs | run-ops-investigator |
| Ontology Mapper | Identify operational-field mapping gaps | ontology-mapper |
Selecting a starter opens an unsaved blank package seeded with its catalog identifier as name and its description. It is not a download of a complete prewritten procedure. Fill the instructions, add references, validate and choose Create skill. A selected starter can also inform the generation context, but you still review the actual generated package.
Plugin-provided guidance
An installed plugin can declare a skill capability with a resourcePath pointing to a SKILL.md inside its artifact. Enabled workspace skill capabilities appear as source plugin and read-only. The resolved package contains the head and files beneath that skill directory.
Inspect the source before editing. Plugin skills have no editable standalone branches and cannot be saved, activated or deleted as if they were standalone assets. Change the plugin through its supported lifecycle. When removing a plugin or capability, first inspect workflows that reference its skill.
Create an independent copy
If you need different guidance, create a standalone package with a unique name and copy the instruction/reference text you are permitted to reuse. Review references and behavior, then change consumers to the new asset ID. The new package is independent; future parent plugin changes do not automatically merge into your copy.
Bundle a custom plugin skill
A minimal package has these two files:
apiVersion: 1
kind: plugin
name: equipment-review
packageName: equipment-review
version: 1.0.0
displayName: Equipment review
description: Review equipment failure-risk evidence
author:
name: Maintenance team
capabilities:
- kind: skill
key: equipment-review
displayName: Equipment review
description: Review dated equipment prediction evidence
resourcePath: skills/equipment-review/SKILL.md---
name: equipment-review
description: Review a supplied failure-risk prediction against dated evidence.
---
Record equipment ID, evidence cutoff and evaluation window.
Flag observations newer than the cutoff.
Separate predicted probability from observed failure.
Report missing information and propose next checks without changing records.Use the custom plugin authoring/install flow to validate, publish and install the package in the intended workspace. See custom plugin creation and skills in plugins for its installation lifecycle. A standalone package JSON is different from a plugin manifest; importing one does not install the other.