Skip to content
Back to search

claude-skills

SkillWorks with Claude CodeGitHub

Claude Code skills from real business systems: post checks, ZKTeco attendance, safe Supabase + Vercel releases, ops checks, project boards.

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/iamovaiz--claude-skills/badge.svg)](/listings/iamovaiz--claude-skills)

HTML

<a href="/listings/iamovaiz--claude-skills"><img src="/api/listings/iamovaiz--claude-skills/badge.svg" alt="findsafeskills safety rating" /></a>

Install

i

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

**Claude Code**, all projects:

git clone https://github.com/iamovaiz/claude-skills.git
cp -r claude-skills/skills/post-check ~/.claude/skills/

Use `.claude/skills/` inside a repo instead to install for that project only. Claude picks a skill up from its description, so you don't need to call it by name.

**Claude apps** (web, desktop): download a skill's zip from the [latest release](https://github.com/iamovaiz/claude-skills/releases/latest) and upload it under Settings, Capabilities, Skills.

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

README.md · README · 94 lines
  1. <p align="center">
  2. <img src="assets/banner.png" alt="I AM OVAIZ Claude Skills" width="100%">
  3. </p>
  4. <h1 align="center">Claude Skills for people who run real businesses</h1>
  5. <p align="center">
  6. Seven Claude Code skills taken from live business systems: a factory HR and payroll system, client online stores, and the release work behind them.<br>
  7. Each one exists because something broke without it.
  8. </p>
  9. <p align="center">
  10. <a href="LICENSE"><img alt="License: Apache 2.0" src="https://img.shields.io/badge/license-Apache%202.0-E8FF3B?labelColor=0A0A0A"></a>
  11. <a href="https://github.com/iamovaiz/claude-skills/actions/workflows/checks.yml"><img alt="Checks" src="https://github.com/iamovaiz/claude-skills/actions/workflows/checks.yml/badge.svg"></a>
  12. <img alt="Skills: 7" src="https://img.shields.io/badge/skills-7-E8FF3B?labelColor=0A0A0A">
  13. <img alt="Works with Claude Code and Claude apps" src="https://img.shields.io/badge/works%20with-Claude%20Code%20%7C%20Claude%20apps-E8FF3B?labelColor=0A0A0A">
  14. </p>
  15. ---
  16. ## Why these exist
  17. I run business systems by directing Claude Code, not by writing every line myself. That works well until Claude does something reasonable that turns out to be wrong: a migration on the wrong database, a deploy that says READY while the site still serves last week's build, a night-shift worker marked absent because their shift crossed midnight.
  18. Each skill below is the written-down fix for one of those. They are plain Markdown instructions plus small Python scripts with no dependencies, so you can read every line before you trust it.
  19. ## The skills
  20. | Skill | Use it when | Script |
  21. |---|---|---|
  22. | [**post-check**](skills/post-check) | You are about to publish a LinkedIn or X post and want to catch em dashes, invisible characters, a leftover `,.`, placeholders, AI-sounding words and claims you ruled out | `postcheck.py` |
  23. | [**zkteco-attendance-import**](skills/zkteco-attendance-import) | You have ZKTeco fingerprint-machine exports and need a monthly attendance sheet that gets night shifts right | `pair_shifts.py` |
  24. | [**staged-release-supabase-vercel**](skills/staged-release-supabase-vercel) | You ship changes to a Supabase + Vercel app with separate staging and production, and want proof the live site serves the new version | `served_version.py` |
  25. | [**supabase-vercel-ops-checks**](skills/supabase-vercel-ops-checks) | You set up a new Supabase project, run migrations remotely, or a deploy looks fine but the site is not | checklist |
  26. | [**project-board-sync**](skills/project-board-sync) | You want Claude to read the project plan before working and suggest what is done, with evidence, when it stops | template |
  27. | [**one-step-command-coach**](skills/one-step-command-coach) | You run the commands Claude gives you and want one labelled step at a time, checked by evidence before the next | example session |
  28. | [**pre-sales-scope-guard**](skills/pre-sales-scope-guard) | A prospect keeps asking for proposals, research or demos before paying, and you want effort matched to the deal stage | templates |
  29. ## Install
  30. **Claude Code**, all projects:
  31. ```bash
  32. git clone https://github.com/iamovaiz/claude-skills.git
  33. cp -r claude-skills/skills/post-check ~/.claude/skills/
  34. ```
  35. Use `.claude/skills/` inside a repo instead to install for that project only. Claude picks a skill up from its description, so you don't need to call it by name.
  36. **Claude apps** (web, desktop): download a skill's zip from the [latest release](https://github.com/iamovaiz/claude-skills/releases/latest) and upload it under Settings, Capabilities, Skills.
  37. ## Try one in a minute
  38. ```bash
  39. cd claude-skills/skills/post-check
  40. python3 postcheck.py examples/bad-post.txt --offlimits offlimits.example.txt
  41. ```
  42. ```
  43. POST CHECK linkedin, 166 chars, 4 hashtags
  44. FAIL em dash: 1x
  45. FAIL Unfilled placeholders: {{CTA}}
  46. FAIL Off-limits: 500K revenue claim (not provable)
  47. FAIL Banned words: game-changer, journey, thrilled to announce
  48. FAIL Hashtags: 4 (max 3 for linkedin)
  49. ...
  50. RESULT BLOCKED: fix every FAIL
  51. ```
  52. ## What the skills will and won't do
  53. - They never publish, merge, deploy or run production SQL on their own. You approve each of those in chat.
  54. - They never ask you to paste passwords, tokens or keys into the conversation.
  55. - Every example file uses invented data. No real employees, clients or project IDs.
  56. - The scripts use the Python standard library only (reading `.xlsx` needs `openpyxl`). Only `served_version.py` touches the network, and only the URL you give it.
  57. ## Contributing
  58. Bug reports, fixes and new skills are welcome. Read [CONTRIBUTING.md](CONTRIBUTING.md) first; the main rule is that every skill comes from a real problem and ships with invented test data.
  59. Found a security issue? See [SECURITY.md](SECURITY.md) and report it privately.
  60. ## License
  61. Apache License 2.0. See [LICENSE](LICENSE) and [NOTICE](NOTICE). You can use, change and redistribute these skills, including commercially. Keep the LICENSE and NOTICE files with any copy.
  62. The license covers the code and text in this repo. It does not give permission to use the "I AM OVAIZ" name, the OV logo or other I AM OVAIZ branding, except to say where the skills came from.
  63. ---
  64. <p align="center">
  65. Made by <a href="https://iamovaiz.com"><b>I AM OVAIZ</b></a>, maintained by <a href="https://github.com/ovaizrana">@ovaizrana</a>. We build business systems for factories, retailers and e-commerce operators.<br>
  66. If a skill saved you time, a star helps other people find it.
  67. </p>

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.