agentleFS
farukzahrafarukzahra/agent-skills/skills/skills-sh-maintainer/SKILL.md

skills-sh-maintainer

Skill0 starsChanged 2 months agoMITView on GitHub

Create, update, publish, and sync Cursor agent skills on skills.sh (farukzahra/agent-skills) and the local environment (~/.cursor/skills, ~/.agents/skills). Use when the user asks to create or change a skill, publish to skills.sh, install skills globally, or sync skill copies.

  • Reads credentials
  • Commits and pushes

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 0 are distinctive, and 4 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 4

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Never: consider a skill change done if you only edited ~/.cursor/skills/ without commit + push in ../agent-skills.

    line 26
  2. Very specific:

    Commit PATs, .env, or credentials.

    line 104
  3. Very specific:

    Put project-specific slash commands inside the skills.sh package.

    line 106
  4. Very specific:

    Use ~/.cursor/skills-cursor/ (reserved for Cursor built-ins).

    line 107

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “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

Skills.sh maintainer — create & publish agent skills

You maintain Faruk's published agent skills on skills.sh and keep local copies in sync.

Source of truth

WhatPath / URL
Git repo (edit here first)../agent-skills (sibling of project repos under shared parent)
GitHubhttps://github.com/farukzahra/agent-skills
skills.sh listinghttps://skills.sh/farukzahra/agent-skills
Local Cursor skills~/.cursor/skills/<name>/
Local agents skills~/.agents/skills/<name>/
GitHub PAT../secrets/github/pat.txt (line ghp_...)

Never consider a skill change done if you only edited ~/.cursor/skills/ without commit + push in ../agent-skills.

When to use this skill

  • User asks to create a new skill
  • User asks to change an existing published skill (e.g. recap)
  • User asks to publish or push skills to skills.sh
  • User asks to install or sync skills in the local environment
  • User says "skill no skills.sh", "agent-skills repo", "publicar skill"

Create a new skill (workflow)

  1. Choose kebab-case name (English): e.g. recap, skills-sh-maintainer.
  2. Create folder in repo:
    ../agent-skills/skills/<skill-name>/
      SKILL.md          # required — YAML frontmatter + body (English)
      reference/        # optional snippets, templates
  3. SKILL.md rules (see also Cursor create-skill skill):
    • name and description in frontmatter (English)
    • description must say when to invoke the skill (discovery)
    • Body: workflow steps, templates, quality bar
    • User-facing HTML/copy may be PT-BR when the skill targets a PT project
  4. Update README.md in repo root — list the new skill + install one-liner.
  5. Commit + push main (Conventional Commits, English message).
  6. Sync everywhere — /commit-push in this repo runs scripts/sync-faruk-skills.ps1 after push (global + all C:\repo git repos + ~/.cursor/skills/). Manual run if not using /commit-push:
    ../agent-skills/scripts/sync-faruk-skills.ps1
  7. Rollout — see reference/rollout.md: bulk sync is automatic on /commit-push; do not ask the user.
  8. Project slash commands (if needed) live in consumer repos, e.g. sessao-gravador/.cursor/commands/recap.md — not in the skills.sh package.

Update an existing skill

  1. Edit under ../agent-skills/skills/<skill-name>/.
  2. /commit-push (or commit → push → scripts/sync-faruk-skills.ps1).
  3. Report commit hash + skills.sh URL to the user.

Push when gh is unavailable

cd ../agent-skills
$pat = (Get-Content "../secrets/github/pat.txt" -Raw).Trim() -split "`n" | Where-Object { $_ -match '^ghp_' } | Select-Object -First 1
git push "https://${pat}@github.com/farukzahra/agent-skills.git" main

Quality bar for published skills

  • Concise SKILL.md (< 500 lines); split heavy reference into reference/.
  • Actionable steps — no vague advice.
  • No secrets in skill files or examples.
  • English for skill metadata and instructions; UI copy in target project language when relevant.
  • Test the skill once in a real project before telling the user it's ready.

Skills currently in this repo

SkillPurpose
recapSession delivery recap → self-contained HTML
dont-forgetEncode recurring obligations as CI/hooks/codegen, not prose
semantic-versionBump docs/release-history.json on /commit-push (feeds /sobre)
caveman-commitTerse Conventional Commits for /commit-push
project-initBootstrap Superpowers workflow (/init) in a project
automate-before-manualPAT/SSH/API via ../secrets/ before manual steps
dont-be-lazyUser lazy → API/MCP, vault creds, Cursor browser — agent finishes
validate-before-shareVerify URLs before sharing with user
finish-with-dev-serverDev server, port conflicts, test URLs
ask-before-architectureAsk before stack/architecture decisions
diagrams-mermaidMermaid diagrams with syntax validation
ui-change-e2eE2E on UI changes and bugfixes
find-jobLinkedIn Jobs search from resume (browser, manual login, match report)
instagram-chrome-postInstagram publish via Chrome CDP + Playwright (not Cursor MCP upload)
google-calendar-mcpGoogle Calendar events/reminders via Cursor MCP plugin
skills-sh-maintainerThis skill — create/publish/sync skills (workspace-specific rollout)

Do not

  • Commit PATs, .env, or credentials.
  • Edit only ~/.cursor/skills/ without pushing agent-skills.
  • Put project-specific slash commands inside the skills.sh package.
  • Use ~/.cursor/skills-cursor/ (reserved for Cursor built-ins).

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.