Andrey Markin
  • home
  • services
  • products
    • Peektrace
    • Agent Skills
    • SEO Lens
  • projects
  • blog
  • directory
  • courses
  • resume
  • about
  • contact
  • meet

Mark Life Ltd

  1. Home
  2. Products
  3. Agent Skills
Meet

Mark Life Ltd

BG208147965

HomeContactPrivacyLLM-friendlyBlog RSSDirectory RSS
Agent SkillsLive

Agent Skills

Agent skills that teach Claude Code and Codex how I work.

Free & open source·Claude Code, Codex
Claude CodeCodexAgent SkillsDeveloper Tools
Browse on skills.shView on GitHub
Install
npx skills add Mark-Life/agent-skills -g
Agent Skills

Eight skills I run every day: the parts of my judgment I got tired of retyping into every session. Each is plain markdown, loaded only when the work matches.

The command above uses the skills CLI and installs globally, prompting for which skills and which agents. Add --skill <name> for just one, or --all to take everything without prompts.

Coding Workflows

Taste and process for the build loop: what to make, how to start it, how to write it up.

  • product — scope the ambition to what agents made possible, and name the primitive others compose on.
  • new-project — scaffolds a repo from my Next.js monorepo template and runs the bootstrap.
  • pr-issue — titles in Vim's area: summary style, then labelled sections in template order.

product is the one that runs before any code exists: it decides what is worth building. It makes the agent name the primitive others will compose on and leave the rest to the caller, so an API, an SDK or a spec comes out with a surface someone can build on instead of a pile of features.

A PR body carries Problem:, Solution:, Security Impact:, Testing:; an issue carries Problem:, Reproduction:, Expected vs actual:, Proposed solution:. Nothing else: no changelog, no checklist, no command output that was not really produced.

Communication

A matched pair. agent-to-human governs what the agent says to you: it reasons at any length in private, then answers first, cuts to the decision, and shows only receipts. It is the highest-leverage skill here, because it stops the model narrating what it did and makes it say the thing you needed. human-to-agent governs what you say to the agent: prompt the positive, cut no-ops, give checkable completion criteria. Load it whenever you are writing something an agent will later execute as instruction — a skill, a CLAUDE.md or AGENTS.md, a set of agent rules, a prompt.

Inspect & Debug Agents

All three answer one question: what is actually in the agent's context, and what is it costing you.

  • session-report — HTML report of a session's context window: token budget, thinking cost, dumb-zone cutoff, full history.
  • memory-view — secret-redacted HTML explorer for Claude Code's per-project auto-memory. Read-only, no curation.
  • context-doctor — audits the context auto-loaded into every session and ranks the cuts: prune, gate behind a trigger, or route elsewhere.

That auto-loaded context is tool and MCP definitions, connectors, plugins, skills, subagents, memory and rules files. You pay for it on every turn, before you have typed anything, so context-doctor cross-checks it against what you actually invoke.

session-report and memory-view are the one-shot path: nothing to install, one command, one report answering one question. Peektrace is the same data as a live pane — browse every session, and edit the memory instead of only reading it.

MIT licensed.

Need custom agent skills or AI tooling?

Get in Touch