Individual skill
skillify
Turns useful work from the current conversation into a reusable org skill. Captures the trigger, outcome, procedure, and judgment so the play can be rerun.
skills/ido-goldberg/skillify/SKILL.md
Source commit 5d786aad0c7b2ca59b1abf1f601f9407ca261996
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- Yes
- Observed behavior
- Not checked yet
- Last checked
- Nov 5, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 236
- Repository last updated
- Oct 20, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- engineering Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 10,514 bytes
Read excerpt
## Instructions
### When this applies
Only skillify work that is **repeatable** and **already proven**. The conversation has to have produced a real procedure with a real outcome — not a half-finished attempt, not a one-off task. If the conversation mostly wandered, say so and ask what to capture.
Shapes that skillify well: a qualification rubric just used on an inbound, a research pattern that should run on the rest of the list, a scoring approach, an outreach framework, a triage flow for a signal. Shapes that don't: ad-hoc questions, one-time data pulls, debugging sessions.
### Procedure
**1. Reconstruct the three load-bearing pieces.**
- **Trigger** — the specific repeatable situation. "When an inbound demo request comes in" beats "the user asked about a lead."
- **Outcome** — the concrete deliverable. A scored list, a draft sequence, a research brief, a CRM cleanup, a Slack handoff.