jbdamask
- 33 skills
- 0 followers
- 16 hours ago last updated
- ▌ Til · jbdamask bundleCondense an AI session (or a single learning) into a very short, standardized TIL document — a concise title, one-line description, and a briefing of what was done, in Markdown by default or HTML on request. Use when the user says "TIL", "today I learned", or "write a TIL", or wants a short shareable write-up of something learned or done in a session.
- ▌ Sefam · jbdamask bundleProduces a concise, plain-language write-up of a technical subject that a smart but non-technical reader (like a manager) can fully understand — no jargon, but not dumbed down — and delivers it as a great-looking styled web page (an Artifact) by default, or as plain markdown if the user prefers. SEFAM means "Simple Enough For A Manager". Works on either a technical CHANGE (a PR, diff, commit, bug fix, GitHub issue) or a technical CONCEPT in a repo (a function, a process/workflow, an architecture, a system, a service, a design decision). Use when the user says "sefam", "SEFAM", "explain it like I'm not an engineer", or asks to explain how some function/process/architecture/system works for a non-technical audience.
- ▌ Devlog · jbdamaskCreate and maintain a DEVLOG.md file capturing the development story of a project. Use this periodically over the course of a project to capture important information about the development story. Invoke when the user asks to update the devlog, create a devlog, document project progress, or capture development history. Also appropriate after completing significant milestones or before context switches.
- ▌ Gilfoyle · jbdamask bundlePlay Napalm Death's 'You Suffer' — the shortest song ever recorded (1.316 seconds of grindcore). Use when the user says 'gilfoyle', 'you suffer', 'napalm death', 'play the song', or wants a moment of sonic brutality.
- ▌ My Voice · jbdamask bundleWrites or rewrites content in the user's own voice by applying an existing `voice-profile.yaml` (weights, variability, register) to the requested piece. Use when the user asks for something written or edited to sound like them — "write this in my voice", "rewrite this the way I'd say it", "make this sound like me", "use my voice profile", "draft this in my style" — including emails, posts, essays, proposals, and other prose. This skill READS the profile and never modifies it; use the build-my-voice skill to create or update the profile itself.
- ▌ Pass Along · jbdamask bundleWrite a session pass-along document to .pass-along/<YYYY-MM-DD-HHMM>-PASS-ALONG.md capturing operational state — what moved, what is half-done, which loops are still open, and the traps that wasted time — with frontmatter metadata (model, repo, branch, HEAD sha, issue tracker, issues, beads) for the agent that picks the work up. Use when the user says "write a pass-along", "/pass-along", "write a handoff", "hand this off", "I'm wrapping up", "save state for next session", "end of session notes", or is about to stop work, switch machines, or hand a branch to someone else. Also offer one proactively after a significant milestone or when context is about to compact. Companion to the session-recap skill, which reads these.
- ▌ Plan Only · jbdamaskPlan-only mode that replicates Claude Code's built-in plan mode workflow but stops after the user approves the plan — no auto-execution. Use when the user wants to plan without executing, says "plan only", "just plan", "plan but don't execute", or when another skill needs planning without triggering auto-execution. Writes the plan to .claude/plans/<slug>.md.
- ▌ Clone Repos · jbdamask bundleBulk-clone a set of git repositories into a single root directory using the bundled clone-repos.sh script. Use this whenever the user wants to clone several repos at once, pull down all the repos for a project or engineering estate, lay multiple repositories out side-by-side under one folder, or set up a local working tree of many repos (e.g. as the first step before reading, documenting, or doing an architecture review across a codebase). Trigger on phrases like 'clone these repos', 'clone all the repos', 'bulk clone', 'clone a bunch of repositories into a folder', or when the user hands over a list of git URLs and a destination directory.
- ▌
- ▌ MCP Scanner · jbdamask bundleHelp users evaluate whether an MCP (Model Context Protocol) tool is safe and right for them before installing it. Use when a user wants to check, scan, review, or assess a third-party MCP server from GitHub, npm, or any repository URL. Provides plain-language assessments that anyone can understand, with technical details available on request.
- ▌ Cringelinter · jbdamaskLints writing for AI slop tells, including overused words, cringe phrases, structural patterns, and bro-speak declaratives that are fingerprints of LLM-generated text. Use this skill any time the user asks to check, clean, lint, or review writing for AI tells, AI slop, cringe phrases, or generic LLM-sounding language. Also use it when the user says things like "does this sound AI-written?", "make this sound more human", "remove the AI vibes", "de-slop this", or "clean up my draft". If the user shares a piece of writing and expresses any concern about it sounding robotic, generic, or artificial, use this skill.
- ▌
- ▌ AWS Learnings · jbdamaskProactively catch common AWS infrastructure mistakes before they happen. Use when creating or modifying AWS components — CloudFormation, CDK, Lambda, API Gateway, IAM, S3, CloudFront, EC2, EventBridge, SQS, Secrets Manager, or SSM — to find and apply hard-won deployment lessons and avoid known pitfalls. Read-only: fetches lessons, does not add them.
- ▌ Cost Tracking · jbdamask bundleTrack API token costs for specific operations in Claude Code. Use when the user invokes /cost-tracking to start measuring costs, or says "stop tracking", "stop cost tracking", or "how much did that cost" to stop and calculate. Tracks input, output, and cache tokens per API call and calculates USD cost using current Anthropic pricing.
- ▌ Session Recap · jbdamaskReconstruct where a coding session left off by reading the latest .pass-along document if one exists, then gathering context from git history, planning docs, task trackers, and past agent chat logs from any supported harness (Claude Code, Codex CLI, Amp, opencode, Grok CLI), then summarizing it as recent activity, current state, active tasks, and likely next steps. Use when the user asks "where were we?", "what were we working on?", "recap the session", "catch me up", "what did I do yesterday", or otherwise returns to a project and needs to resume. Also use when a new conversation looks like a continuation of earlier work.
- ▌ Build My Voice · jbdamaskAnalyzes samples of the user's writing and creates or updates a structured `voice-profile.yaml` describing their writing voice as weighted, evidence-backed features, then asks the author a short round of questions to confirm the inferences the samples cannot settle on their own. Use when the user wants to capture, build, learn, profile, or update their writing voice or style from writing samples — "build my voice profile", "analyze my writing style", "learn how I write", "create a voice profile from these posts", "update my voice profile with this new sample". This skill only ANALYZES writing and produces the profile; it never drafts new content in the user's voice — use the my-voice skill for that.
- ▌ Bullshit Tests · jbdamask bundleAudit a codebase's test suite for tests that pass for no good reason — no assertions, tautologies, assertions on mocks only, swallowed exceptions, unawaited async assertions, permanently skipped tests, and other patterns that stay green no matter how broken the code is. Produces a red/yellow/green report. Use when the user says "bullshit tests", "find fake tests", "audit my test suite", "which tests are useless", "are these tests actually testing anything", "check test quality", "find tests that always pass", or asks whether green CI means anything.
- ▌ Company Shorts · jbdamaskGenerate a succinct, factual, up-to-date company research report ('Company Short') in a fixed Markdown format. Use whenever the user asks to research a company, get a company overview/profile/brief, asks 'what does <company> do', wants competitive or market intel on a business, or invokes 'company shorts'/'company short' with a company name or URL. Covers business model, products, financials, partnerships, market position, customers, and recent news.
- ▌ Phone A Friend · jbdamaskSpawn an Opus sub-agent in extended-thinking max-effort mode to debate, critique, and pressure-test the primary agent's current thinking through an unbounded multi-turn dialogue, terminating when the agents either reach genuine consensus or cleanly agree to disagree. Supports escalating clarifying questions to the human user mid-debate, and supports the user sending the debate back for another round (jury-room rule). Use when the user invokes "phone a friend", asks for a "second opinion", "sanity check", "debate this with another model", or otherwise signals they want rigorous adversarial review of an approach, plan, design, diagnosis, or decision before proceeding.
- ▌ Ec2 Claude Code · jbdamask bundleCreate an Ubuntu 24.04 LTS EC2 instance with Claude Code, Playwright (headless browser testing), tmux, git, beads (bd) task tracking, and agent-deck session manager pre-installed. Use when user wants to spin up a cloud development environment, create an EC2 for Claude Code, launch a remote Claude Code instance, or set up a dev box on AWS. Supports multiple instances per account with unique naming.
- ▌ Issue To Beads · jbdamask bundleDecomposes GitHub issues into structured Beads epics, tasks, and sub-tasks with objectively verifiable acceptance criteria. Use this skill whenever the user mentions converting GitHub issues to Beads, planning work from a GitHub issue, decomposing issues into tasks, breaking down a GitHub issue, or wants to take an issue and turn it into actionable Beads work items. Also trigger when the user says things like "plan this issue", "break down issue X", "convert this to beads", or references a GitHub issue URL and wants it turned into trackable work. Requires that the user's project uses Beads (bd) for issue tracking.
- ▌ Project Memories · jbdamaskMaintain durable project memories as files in the repo, using the llms.txt pattern — a docs/memories/ folder with one markdown file per memory plus a docs/memories/llms.txt index. Use when the user says "remember this for the project", "save a project memory", "add to project memories", "update a project memory", "retire a memory", "migrate memories", "set up project memories", or wants project knowledge to travel with the repo instead of living in an ad-hoc mechanism like beads' `bd remember`.
- ▌ AWS Learnings Add · jbdamaskContribute a new lesson to the AWS Learnings library (the llms.txt-format library at github.com/jbdamask/aws-learnings-library). Use this whenever you've just debugged, fixed, or discovered a non-obvious AWS gotcha — CloudFormation, CDK, Lambda, API Gateway, IAM, S3, CloudFront, EC2, EventBridge, SQS, Secrets Manager, SSM — and want to capture it for next time. Triggers on phrases like 'add an AWS learning', 'save this AWS lesson', 'capture this gotcha', 'add this to the learnings library', or after solving a tricky AWS deployment problem worth remembering. This skill WRITES files (a new lesson file + an updated index) and prepares a pull request; it is the write companion to the read-only 'aws-learnings' skill.
- ▌ Memory Checkpoint · jbdamask bundleSave and restore session state for continuity across context compressions. Invoke with "/memory-checkpoint" to save current session state, or "/memory-checkpoint your search query" to search past checkpoints by semantic similarity.
- ▌ Git Push And Tag · jbdamaskFinal-phase skill that stages beads, commits, pushes to the remote branch, and labels the GitHub issue as "Ready". Invoked by issue-to-beads as the last step after all beads have been filed, reviewed, and synced. Can also be used standalone when you have synced beads on an issue branch that need to be committed and pushed.
- ▌ AWS Quick Endpoint · jbdamask bundleCreate a token-secured REST API endpoint backed by AWS Lambda and DynamoDB with full CRUD and paginated list support. Deploys via CloudFormation. Use when user wants to quickly spin up an API endpoint, create a simple REST API on AWS, build a quick data store with an API, set up a Lambda+DynamoDB endpoint, or needs a fast way to log and retrieve structured data. Triggers on "create an endpoint", "quick API", "Lambda endpoint", "DynamoDB API", "CRUD endpoint", "log data to AWS".
- ▌ Github Pages Deploy · jbdamask bundleStand up a new static site (an index.html plus assets) on GitHub Pages from the terminal — creates the repo, pushes, enables Pages, waits for the build, and checks the live URL and its images actually load before handing it over. Also checks the page lays out properly on phones and laptops (no sideways scrolling, no half-empty screen) and tells you how to write the HTML so it does. Use this whenever the user wants to put a static page, landing page, demo, report, or standalone HTML on the web, or says "deploy this", "host this", "publish this page", "put this online", "get me a link I can send someone", or "ship it to GitHub Pages" — including when they never say "GitHub Pages" and just want a public URL. Also use to push updates to a site published this way.
- ▌ Youtube Transcripts · jbdamask bundleDownload transcripts (auto-captions) for videos from a YouTube channel within a date range, as timestamped markdown linked back to the source video. Use when the user wants to grab transcripts/subtitles/captions from a channel, e.g. "download transcripts for all AI Daily Brief videos from July 2026", "get the captions from this channel for last month", "pull transcripts between two dates". Requires yt-dlp and ffmpeg installed.
- ▌ Five Whys Root Cause Analysis · jbdamaskEvidence-based root cause diagnosis using a branching five-whys investigation. Produces a likelihood-ranked list of candidate root causes — diagnosis only, never a fix. Use ONLY when the user explicitly asks to diagnose a problem or find a root cause, with phrases like "find the root cause", "diagnose this", "do a five whys check", "root cause analysis", "why is this happening", or "run a five whys". Do NOT trigger on generic mentions of errors, bugs, or fix requests.
- ▌ Google Doc Style Guide · jbdamask bundleWrites and edits technical documentation and application help content in a consistent house style derived from the Google developer documentation style guide — second person, active voice, present tense, sentence-case headings, procedures, lists, tables, code font, placeholders, notices, link text, accessible and inclusive language, and a word list of preferred and prohibited terms. Use whenever writing or revising a README, quickstart, how-to, tutorial, concept page, troubleshooting guide, CLI or API docs, API reference comments, release notes, in-app help, tooltips, or error-message text; also use when asked to "apply the Google style guide", "make these docs consistent", "edit this doc for style", "write docs for this", or to review documentation for style problems.
- ▌ Context Optimization · jbdamask bundleThis skill should be used when the user asks about "context window optimization", "reduce context usage", "context is filling up", "running out of context", "context bloat", "optimize my sessions", "why is context so large", or when providing advice on how to keep Claude Code sessions efficient. Provides knowledge about what consumes context and strategies to minimize waste.
- ▌ Plugin Marketplace Creator · jbdamask bundleCreate and configure Claude Code plugin marketplaces hosted on GitHub. Use this skill when users want to set up a new plugin marketplace repository, add plugins to an existing marketplace, configure team distribution settings, or troubleshoot marketplace issues. Triggers include "create a plugin marketplace", "set up a marketplace on GitHub", "add plugins to my marketplace", "configure marketplace for my team", or "distribute Claude Code plugins".
- ▌ Architecture Decision Records · jbdamaskWrite and maintain Architecture Decision Records (ADRs) that capture the context and rationale behind significant technical decisions. Use when documenting an architectural or technology choice, recording a design trade-off, superseding a past decision, or setting up an ADR process. Also use proactively to offer an ADR when a significant decision is made during a coding session (database, framework, auth scheme, API style, integration pattern). Triggers on "write an ADR", "document this decision", "record this architecture choice", "add a decision record", "supersede ADR".