SkillFoxx

Ape Skills

Eight standalone skills for developers: commits, Markdown, pseudocode, quizzes, terminal UX, talks and papers.

  • 57 ★ on the repository
  • Last commit
  • MIT
Skill

Minimal access

Why this level

  • The skills are instructions, while `ape-present` and `ape-write-paper` ship verification scripts the agent runs locally.
All reasons and checks

arpitbbhayani/ape-skillsAuthor:arpitbbhayani

Install

In your terminal, with SkillFoxx CLI

npx skillfoxx add skills/ape-skills

Detects the agents on your machine, shows the access level and pins the version.

Other ways to install

Access and checks

How we review

Minimal accessThe tool runs nothing and makes no network calls.

  • The skills are instructions, while `ape-present` and `ape-write-paper` ship verification scripts the agent runs locally.

This is third-party code. Review the repository files before installing.

What it does

The repository collects skills with an `ape` prefix. `ape-commit` formats commit messages: a crisp summary and imperative bullets. `ape-style-markdown` applies consistent Markdown rules to any output, `ape-write-pseudocode` writes pseudocode for functions and algorithms, and `ape-quiz-me` checks whether a reader understood the material or only recites it. The others are larger. `ape-cli-terminal-experience` designs a CLI's terminal experience: palette, glyphs, spinners and full-screen views. `ape-present` turns a blog post into a self-contained HTML document with animated diagrams, and `ape-write-paper` builds a two-column LaTeX paper while auditing claims against evidence. `ape-design` enforces the Array UI design system.

Who it is for. Developers who want a few separate skills instead of a monolithic bundle: take one folder and use it right away.

Good fit when

  • Commit messages in a team vary and you need one format.
  • An author prepares a LaTeX paper from gathered material and wants claims audited against evidence first.
  • A blog post needs to become a one-page HTML for a talk.
  • After reading a book or article you want to check the material was truly understood.

Not a fit when

  • You need one bundle with shared install and updates.
  • You need a design system other than Array UI.
  • The paper must be formatted in Word or a different journal template rather than two-column LaTeX.

Example request

ape commit: write a message for the current changes.

Limitations

Each folder installs separately; there is no shared package or shared update. The `ape-present` and `ape-write-paper` skills need a `reference` directory beside `SKILL.md`, so copy the whole folder. `ape-write-paper` needs LaTeX build tools on the machine. The set is small and personal: the author tunes it to his own work, so commit and Markdown rules may differ from your team's. Read the relevant `SKILL.md` and compare its rules with yours before installing.

How to disable. Delete the relevant skill folder from `~/.claude/skills` or run your skills manager's remove command.

FAQ

How do I install a single skill?

Run `npx skills add` with the URL of the skill folder in the repository. Copying the folder into `~/.claude/skills` also works.

How do I trigger a skill?

Write `ape` and the action name, for example `ape commit`. You can also name the skill explicitly: `/ape-commit`.

What does ape-quiz-me do?

It quizzes you on content you claim to have read, Socratically: hints narrow the search without revealing the answer. It ends with a verdict on whether you understood or just recited.

What does ape-present need?

The skill requires a `reference` directory next to `SKILL.md`, holding base styles, a page skeleton, a runtime and examples.

What licence applies?

MIT.

Discussion

No questions or reviews yet.

Skills

Twenty skills for reading unfamiliar code, reviewing documents and commits, translating Markdown and OpenSpec-driven development

SkillExtended access92

17 skills for ABAP developers: Clean ABAP, RAP, CDS, OData, ABAP Cloud, unit tests, migration and BTP diagrams

PluginMinimal access74

Five skills for daily development: requirement interviews, AGENTS.md rules, PR review triage and single-file HTML design.

SkillExtended access94

Eleven skills for Claude Code and Codex: test audit, git worktree cleanup, plan pages, screen recording transcripts and 1Password sign-in

SkillBroad access1.2K

A personal set of 15 skills: code review, PRD and tasks, an implementation orchestrator, tests and bug hunting.

SkillExtended access53

Methods for an agent in one CLI: comparing options, solving problems and changing code in steps, 20 slash commands in all.

CLIExtended access126

README in short

Skills live in separate folders and install independently. The README table gives each a one-line description; details are in its `SKILL.md`.

README badge

Original SKILL.md

---
name: ape-commit
description: >
  Defines how to write and format git commit messages. Use this skill whenever
  the user asks you to write, draft, suggest, or format a git commit message,
  summarize changes into a commit, or help stage and describe code changes.
  Trigger even for casual requests like "write me a commit for this" or "what
  should my commit say".
---

# Commit Message Style

## Format

```
<short summary line>

- <change>
- <change>
- <change>
```

## Rules

### Summary line (first line)
- One line only
- Short and crisp -- aim for under 72 characters
- Use the imperative mood: "Add feature" not "Added feature" or "Adds feature"
- No trailing period
- Describe *what* the commit does, not *how*

### Blank lines
- Always exactly one blank line between the summary line and the bullet list (never omit it)
- No blank lines between bullet list items -- the list must be tight and contiguous (single newline after each item, never an empty/blank line)
- No trailing blank lines at the end of the commit message

### Bullet points
- Each bullet describes a single, specific change
- Short and crisp -- one line per bullet
- Keep bullet items contiguous with no blank lines between them

Report a problem