Back to authors
sofer

sofer

35 Skills published on GitHub.

email-voice-draft

Draft an email reply in the user's voice using their business context and Notion knowledge

UncategorizedView skill →

skill-creator

Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Codex's capabilities with specialized knowledge, workflows, or tool integrations.

UncategorizedView skill →

skill-installer

Install Codex skills into $CODEX_HOME/skills from a curated list or a GitHub repo path. Use when a user asks to list installable skills, install a curated skill, or install a skill from another repo (including private repos).

UncategorizedView skill →

anonymise

Anonymise CSV files by removing personal identifying information and adding datetime stamps. Use when user wants to process a new CSV file or strip PII from data.

UncategorizedView skill →

calendar-fetch

Fetch upcoming calendar events from Google Calendar

UncategorizedView skill →

code-review

Review code for quality, security, and standards compliance. Works as a pipeline gate after refactor phase, or standalone against PR URLs, branch names, commit ranges, or file lists.

UncategorizedView skill →

commit

Git workflow operations with Conventional Commits. Supports subcommands - branch (create feature branch), commit (stage and commit changes), pr (create pull request), merge (merge PR). Automatically available when the current directory is a git repository. Use when user needs git operations during development workflow.

UncategorizedView skill →

contact-research

Research a person given their name and email, returning a brief profile with role, company, LinkedIn summary, and previous interactions

UncategorizedView skill →

deploy

Ship code to target environment. Use after code is merged to deploy to staging or production. Handles build, artifact creation, and deployment orchestration.

UncategorizedView skill →

design-review

Validate design before implementation. Use after design phase to ensure architecture meets standards, spec requirements, and quality criteria. Gates progression to stubs phase.

UncategorizedView skill →

design

Plan architecture and components for a single user story. Use after spec phase to create a technical design before implementation. Produces design documents that guide stubs and implementation.

UncategorizedView skill →

distribution-channel

Identify and evaluate distribution channels for the ML engineer apprenticeship

UncategorizedView skill →

distribution-strategist

Discuss and evolve distribution strategy for the ML engineer apprenticeship

UncategorizedView skill →

draft-post

Guide the user through creating a blog post draft for Substack (200-500 words) and LinkedIn (100-300 words). Use when user wants to draft a post or share work.

UncategorizedView skill →

email-drafter

Fetch unread emails, triage them, draft replies in the user's voice, and save as Gmail drafts for human review

UncategorizedView skill →

feature

Implement a feature using TDD. Works standalone (user describes what to build) or as part of the orchestrated pipeline (story and context provided). Handles complexity scaling, design, stubs, tests, implementation, migrations, refactoring, and review. Use when building a feature in an existing codebase.

UncategorizedView skill →

gmail-draft

Create a draft email in Gmail from provided email data

UncategorizedView skill →

gmail-fetch

Fetch recent emails from Gmail with sender, subject, body, and thread context

UncategorizedView skill →

implement

Write code to pass all tests (TDD green phase). Expect 100% test pass rate. Use after tests are written to implement the actual functionality.

UncategorizedView skill →

init-override

Create a symlink from AGENTS.md to CLAUDE.md in the current project directory. Use when the user wants to initialise a project to use AGENTS.md as the memory file instead of CLAUDE.md.

UncategorizedView skill →

intent

Interactive conversation to clarify user intent step-by-step before creating specifications or solutions. Use when requirements are unclear or user has a new idea to explore.

UncategorizedView skill →

meeting-context

Determine why a meeting is happening and what should be discussed

UncategorizedView skill →

meeting-prep

Check calendar, research attendees, and produce a briefing document for each upcoming meeting

UncategorizedView skill →

monitor

Observe application health and gather feedback after deployment. Use to validate success criteria, collect metrics, and feed issues back to the backlog. Closes the feedback loop.

UncategorizedView skill →

notion-query

Search and retrieve content from a Notion workspace

UncategorizedView skill →

orchestrate

Coordinate full SDLC pipeline for software projects. Manages backlog, spawns phase agents with minimal context, gates transitions, and handles checkpoints. Use when starting a new project, picking up the next story, or resuming pipeline work.

UncategorizedView skill →

postgres-query

Query a Postgres database (read-only) and return structured results

UncategorizedView skill →

readme-review

Review the project README to understand what it does and suggest a recommended next step. Use when starting work on an unfamiliar project.

UncategorizedView skill →

reconcile

Analyse and resolve divergences between SDLC manifest and actual development state (git commits, branches, uncommitted files). Use when manifest and reality have drifted apart, or before picking next story to ensure clean state.

UncategorizedView skill →

refactor

Clean up implementation code while keeping tests green. Improve code quality without changing behaviour. Use after implement phase to polish code before review.

UncategorizedView skill →

requirements

Transform intent into user stories with acceptance criteria. Use after intent clarification to build a prioritised backlog. Produces stories in standard format ready for spec phase.

UncategorizedView skill →

spec

Define contracts, schemas, and behaviours for a single user story. Use after a story is selected from the backlog to create a detailed specification before design. Produces testable specifications.

UncategorizedView skill →

stubs

Create interfaces, type definitions, and stub implementations that compile but are not functional. Use after design-review approval to establish code structure before writing tests. Enables TDD red-green-refactor cycle.

UncategorizedView skill →

test

Write tests against stubs following TDD red phase. Tests should fail initially (0% pass expected). Use after stubs to define expected behaviour before implementation.

UncategorizedView skill →

user-test

Reformat code-review manual test script for human or agent execution, run user testing checkpoint, and record pass/fail results. Gates progression to commit:pr.

UncategorizedView skill →