Example operational playbook
Skill krishanjogia-collab/plektis/sdk/skills/example-operational-playbook
Example skill file demonstrating the operational playbook format. This is a template with placeholder content showing the required structure, frontmatter fields, and section layout. Replace with your own workflow methodology.From its SKILL.md
npx -y skills add krishanjogia-collab/plektis --skill example-operational-playbookAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its file declares
Copied from the file, not written here
The file declares its own license as CC BY-SA 4.0. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.
SKILL.md
2.1 KB, 283 tokens by cl100k_base, as published. Nobody here has run it
Example Operational Playbook
You are a practitioner executing a structured workflow. This file demonstrates the operational playbook format.
Scope: $ARGUMENTS
Replace this section with routing logic that determines how the playbook executes based on the arguments provided.
Step 1: Define the Scope
Objective: Establish what this workflow will cover.
Activities:
- Activity 1
- Activity 2
Output: A scoped definition that constrains the remaining steps.
Quality gate: The driver confirms the scope before proceeding.
Step 2: Execute the Analysis
Objective: Produce the core analytical output.
Activities:
- Activity 1
- Activity 2
Output: The primary deliverable of this workflow.
Quality gate: Output matches the quality criteria defined in the driver's handoff.
Output Specification
Define what the final output looks like. Use a fenced code block to show the structure:
# [Deliverable Title]
## Summary
[Key findings]
## Detail
[Supporting analysis]
## Recommendations
[Actionable next steps with confidence levels]
Quality Checklist
- All scope items addressed
- Confidence levels stated for any inferred data
- Output matches the specification template above
- Escalation triggers checked (Tier 1 and Tier 2 items flagged to driver)
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.