writing-postmortems
Turns outages, user-facing defects, data issues, and near misses into durable incident documentation. Covers evidence-based timelines, contributing factors, blameless framing, and assigned action items.
Your agent can do more. Find the skill that makes it happen.
Find your next superpower If you are an agent, refer to our llms.txt for full access.Turns outages, user-facing defects, data issues, and near misses into durable incident documentation. Covers evidence-based timelines, contributing factors, blameless framing, and assigned action items.
Helps transform abstract ideas into actionable project specifications. Aligns engineering and design teams on the problem to solve and the metrics that define success.
Structures executable operational documentation for use under time pressure. Covers risk labels, symptom-first troubleshooting, migration mappings, rollback steps, deprecation dates, and guide expiry.
Writing, exploit — shape raw material into an article, paragraph by paragraph.
Develops raw writing material into an article by shaping it one paragraph at a time.
Transforms raw writing material into an article. Develops the piece progressively, one paragraph at a time.
Converts hunt findings into portable Sigma detection rules: choosing the right logsource, expressing robust selection/filter logic, setting level and ATT&CK tags, and validating before converting to a SIEM query. Activates for requests to write a Sigma rule, convert a hunt to a detection, or create portable SIEM detection logic.
Use when creating new skills, editing existing skills, or verifying skills work before deployment
Supports creating new agent skills and modifying existing ones. Also covers verifying that skills work before deployment.
Writes and validates Suricata/Snort IDS rules for network-based malware detection, covering rule anatomy, content/pcre matching, flow and threshold options, and common mistakes that cause false positives or no matches. Activates for requests to write a Suricata rule, create Snort signatures, or build network detection rules from IOCs or C2 patterns.
Operately test layout, naming (.projections.json), factories, feature/e2e steps, external query/mutation auth specs, and how to run Elixir/API/JS/EE tests. Use when adding, renaming, splitting, or reviewing tests; choosing where a test belongs; writing Factory/TurboCase/FeatureCase or ExternalApi QuerySpec/MutationSpec tests; or running make test / feature tests.
Guides new and refactored unit tests, including flaky or unreadable tests. Promotes one behavior per test, descriptive names, deterministic setup, and mocks only at unowned boundaries while avoiding sleeps and duplicated implementation logic.
Skills give your agent reusable instructions for a specific job. Pick one, read what it does, and bring it into your workflow.
A name only tells half the story. Search the full description and instructions to find the right fit.
Read the skill, visit its source, and see exactly what you’re adding to your agent.
Copy the install command from a skill page and run it in your project.
npx skillycli add owner/repo --skill name