agentleFS
Sign inStart free
lordmaculordmacu/nexo-rs/skills/skillify/SKILL.md

Skillify

Skill8 starsChanged 7 months agoApache-2.0View on GitHub

Turn a repeatable workflow into a reusable local SKILL.md with explicit steps, criteria, and safe defaults.

51 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use plan-tune, ios-clean and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • ShreyRaviSkill

    plan-tune

    Self-tuning question sensitivity + developer psychographic for gstack (v1: observational). Review which AskUserQuestion prompts fire across gstack skills, set per-question preferences (never-ask / always-ask / ask-only-for-one-way), inspect the dual-track profile (what you declared vs what your behavior suggests), and enable/disable question tuning. Conversational interface — no CLI syntax required.

    Also in 9 projects that use this

  • Saqlain-811Skill

    ios-clean

    Remove the DebugBridge SPM package and all #if DEBUG wiring from an iOS app. (gstack)

    Also in 5 projects that use this

  • Saqlain-811Skill

    ios-fix

    Autonomous iOS bug fixer. (gstack)

    Also in 5 projects that use this

  • ShreyRaviSkill

    landing-report

    Read-only queue dashboard for workspace-aware ship. Shows which VERSION slots are currently claimed by open PRs, which sibling Conductor workspaces have WIP work likely to ship soon, and what slot /ship would pick next. No mutations — just a snapshot. Use when asked to "landing report", "what's in the queue", "show me open PRs", or "which version do I claim next". (gstack)

    Also in 8 projects that use this

  • timurgaleevSkill

    document-generate

    Generate missing docs for a feature, module or project as tutorials, how-tos, reference and explanation.

    Also in 7 projects that use this

  • bastosSkill

    ios-design-review

    Review iOS app UI/UX design quality using Apple's design principles and the Liquid Glass-era design language from WWDC25/26. Use when asked for a design review, UX critique, visual design assessment, or evaluation of an app's interface quality, design intent, alignment with the new Apple design system, or usability. Triggers: "design review", "UX review", "visual design critique", "review the UI", "does this design work", "evaluate this interface", "design feedback", "Liquid Glass review".

    Also in 5 projects that use this

  • +1 more from Saqlain-811
  • +5 more from ShreyRavi

The file

We split this skill into the rules it gives an agent

7 rules. 0 are common, 5 are distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 44 edited versions we read keep these.

  • 5

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this to scale team workflows without rewriting instructions every time.

    line 12
  2. Very specific:

    If workflow_name is missing, ask for a concrete name.

    line 45
  3. Very specific:

    Create directory/file and persist final SKILL.md.

    line 60
  4. Distinctive:

    Never overwrite an existing skill silently.

    line 66
  5. Distinctive:

    Avoid over-broad automation promises.

    line 67
  6. Distinctive:

    Prefer minimal required tool surface over wildcard permissions.

    line 68
  7. Distinctive:

    Keep language implementation-oriented, not aspirational.

    line 70

“Common” is measured: kept by at least 6 in 10 of the 44 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Skillify

Capture a process that worked well and convert it into a reusable skill file. Use this to scale team workflows without rewriting instructions every time.

Use when

  • The same workflow appears repeatedly across sessions.
  • A process has stable inputs, ordered steps, and clear success criteria.
  • You want to convert tacit know-how into a shared SKILL.md.

Do not use when

  • The process is one-off, exploratory, or still unstable.
  • Key steps are unknown or depend on hidden tribal context.
  • The user only wants a quick summary, not a reusable artifact.

Input contract

  • workflow_name (required): short name for the new skill.
  • source_scope (optional): current_task (default) or recent_session.
  • target_location (optional): default skills/<slug>/SKILL.md.
  • required_args (optional): known runtime arguments to expose.
  • confirm_before_write (optional): default true.

Parsing rules (priority order)

  1. Structured args override everything.
  2. Else infer from user phrasing:
    • "make a skill for X" -> workflow_name=X
    • "from this session" -> source_scope=recent_session
    • "save under ..." -> target_location=...
  3. Defaults:
    • source_scope=current_task
    • target_location=skills/<slug>/SKILL.md
    • confirm_before_write=true
  4. If workflow_name is missing, ask for a concrete name.

Canonical workflow

  1. Extract process skeleton
    • Goal, inputs, step sequence, outputs, verification criteria.
  2. Identify constraints
    • Required tools, risk boundaries, irreversible actions, approvals.
  3. Draft skill frontmatter + body
    • Include Use when, Do not use when, input contract, workflow, guardrails, and output format.
  4. Review with user
    • Show full draft and request approval before writing when confirm_before_write=true.
  5. Write skill artifact
    • Create directory/file and persist final SKILL.md.
  6. Post-write validation
    • Re-read file and confirm it is syntactically intact and complete.

Guardrails

  • Never overwrite an existing skill silently.
  • Avoid over-broad automation promises; keep the skill bounded.
  • Prefer minimal required tool surface over wildcard permissions.
  • Mark ambiguous steps explicitly instead of guessing.
  • Keep language implementation-oriented, not aspirational.

Output format

Always return:

  • status: drafted | written | needs_user_input
  • workflow_name: normalized name
  • target_location: final path
  • draft_summary: what the generated skill covers
  • open_questions: unresolved ambiguities
  • next_action: required unless status=written

Example

  • workflow_name="release-pr-handoff" source_scope="recent_session" target_location="skills/release-pr-handoff/SKILL.md"

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free