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
In this repository26 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .cursor/rules/automate-before-manual.mdcCursor rule
- .cursor/rules/finish-task-dev-server.mdcCursor rule
- brainstormingSkill
- caveman-commitSkill
- find-skillsSkill
- semantic-versionSkill
- systematic-debuggingSkill
- verification-before-completionSkill
- writing-plansSkill
- ask-before-architectureSkill
- automate-before-manualSkill
- caveman-commitSkill
- diagrams-mermaidSkill
- dont-be-lazySkill
- dont-forgetSkill
- find-jobSkill
- finish-with-dev-serverSkill
- google-calendar-mcpSkill
- init-fmzSkill
- instagram-chrome-postSkill
- project-initSkill
- recapSkill
- semantic-versionSkill
- ui-change-e2eSkill
- validate-before-shareSkill
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
- Very specific: line 26
Never: consider a skill change done if you only edited ~/.cursor/skills/ without commit + push in ../agent-skills.
- Very specific: line 104
Commit PATs, .env, or credentials.
- Very specific: line 106
Put project-specific slash commands inside the skills.sh package.
- Very specific: line 107
Use ~/.cursor/skills-cursor/ (reserved for Cursor built-ins).
≈ “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.
Files
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
| What | Path / URL |
| Git repo (edit here first) | ../agent-skills (sibling of project repos under shared parent) |
| GitHub | https://github.com/farukzahra/agent-skills |
| skills.sh listing | https://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)
- Choose kebab-case name (English): e.g.
recap,skills-sh-maintainer. - Create folder in repo:
../agent-skills/skills/<skill-name>/ SKILL.md # required — YAML frontmatter + body (English) reference/ # optional snippets, templates - SKILL.md rules (see also Cursor
create-skillskill):nameanddescriptionin frontmatter (English)descriptionmust 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
- Update
README.mdin repo root — list the new skill + install one-liner. - Commit + push
main(Conventional Commits, English message). - Sync everywhere —
/commit-pushin this repo runsscripts/sync-faruk-skills.ps1after push (global + allC:\repogit repos +~/.cursor/skills/). Manual run if not using/commit-push:../agent-skills/scripts/sync-faruk-skills.ps1 - Rollout — see reference/rollout.md: bulk sync is automatic on
/commit-push; do not ask the user. - 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
- Edit under
../agent-skills/skills/<skill-name>/. /commit-push(or commit → push →scripts/sync-faruk-skills.ps1).- 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" mainQuality 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
| Skill | Purpose |
recap | Session delivery recap → self-contained HTML |
dont-forget | Encode recurring obligations as CI/hooks/codegen, not prose |
semantic-version | Bump docs/release-history.json on /commit-push (feeds /sobre) |
caveman-commit | Terse Conventional Commits for /commit-push |
project-init | Bootstrap Superpowers workflow (/init) in a project |
automate-before-manual | PAT/SSH/API via ../secrets/ before manual steps |
dont-be-lazy | User lazy → API/MCP, vault creds, Cursor browser — agent finishes |
validate-before-share | Verify URLs before sharing with user |
finish-with-dev-server | Dev server, port conflicts, test URLs |
ask-before-architecture | Ask before stack/architecture decisions |
diagrams-mermaid | Mermaid diagrams with syntax validation |
ui-change-e2e | E2E on UI changes and bugfixes |
find-job | LinkedIn Jobs search from resume (browser, manual login, match report) |
instagram-chrome-post | Instagram publish via Chrome CDP + Playwright (not Cursor MCP upload) |
google-calendar-mcp | Google Calendar events/reminders via Cursor MCP plugin |
skills-sh-maintainer | This skill — create/publish/sync skills (workspace-specific rollout) |
Do not
- Commit PATs,
.env, or credentials. - Edit only
~/.cursor/skills/without pushingagent-skills. - Put project-specific slash commands inside the skills.sh package.
- Use
~/.cursor/skills-cursor/(reserved for Cursor built-ins).
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
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.

