← all publishers

adewale

@adewale source repo

18 published skills

  1. Good Pr 2 · adewale bundle
    Help users prepare and review pull requests that maintainers actually want to merge. Use this skill whenever someone asks for help writing a PR description, preparing a contribution to an open-source project, reviewing their own PR before submitting, writing a bug fix PR, drafting a feature PR, or asks anything like "how do I make a good pull request", "review my PR", or "why do my PRs keep getting rejected". Also trigger when a user shares a diff or patch and wants help presenting it, when they mention contributing to a repo they don't maintain, when they're preparing their first contribution to a project, or when they want a pre-submission sanity check. Even if the user doesn't explicitly mention "PR" — if they're packaging a code change for someone else to review, this skill applies.
    0
    installs
  2. Testing Best Practices 2 · adewale bundle
    Enforce testing best practices when writing, reviewing, or improving tests. Covers Red-Green-Refactor TDD, property-based testing (invariant-proof and model-gap tactics), real objects over mocks, correctness by construction (types and schemas over runtime validation), test quality assessment (assertion density, not just coverage), E2E testing, contract tests, flaky test upgrades, and detection of sabotaged/skipped tests and logical defense-in-depth. Use when writing tests, reviewing test quality, fixing flaky tests, or when the user mentions TDD, testing, coverage, mocks, invariants, types vs tests, defense in depth, or test quality.
    0
    installs
  3. Testing Best Practices 3 · adewale bundle
    Enforce testing best practices when writing, reviewing, or improving tests. Covers Red-Green TDD, property-based testing, real objects over mocks, test quality assessment (assertion density, not just coverage), E2E testing, contract tests, flaky test upgrades, and detection of sabotaged/skipped tests. Use when writing tests, reviewing test quality, fixing flaky tests, or when the user mentions TDD, testing, coverage, mocks, or test quality.
    0
    installs
  4. Demo Reviewer · adewale bundle
    Demo skill for the Skill Eval Harness example. Use it to review a proposed change and label the severity of each finding.
    0
    installs
  5. Anti Slop Writing · adewale bundle
    Use this skill to review, tighten, draft, and rewrite prose so it does not read like generic LLM output, AI writing, bland marketing, or generic launch copy. Apply it when the user asks to make writing less generic/AI-sounding, tighten a talk intro, sharpen presentation/slide copy, or improve articles, wiki pages, README text, emails, posts, scripts, product/DevRel copy, launch copy, and other important writing with AI tropes, inflated significance language, generic cadence, weak flow, or marketing fog.
    0
    installs
  6. Audit · adewale
    Comprehensive audit toolkit with 14 audit types. Includes a pre-push branch audit (8-category checklist with Clean/Minor/Blocking verdicts) plus 13 deep-dive audits run via sub-agents: code quality, documentation brittleness, docs-code sync, language best practices, concurrency, resource management, test quality, feature completeness, performance, bug patterns, design philosophy compliance, security vulnerabilities, and UI design (CRAP principles). Use this skill when the user wants to inspect a concrete codebase, branch, diff, repository, service, or docs/source pair: audit before pushing, check their branch, look for duplication or dead code, check docs-code sync, review test quality, find concurrency bugs or resource leaks, analyze concrete security/performance risks in code, review UI implementation, verify feature completeness, or check code against best practices/design principles. Do not use for conceptual explainers about audits, summarizing audit logs, changelog writing, or general security education
    0
    installs
  7. Cloudflare Doctor · adewale bundle
    Audits concrete Cloudflare projects/configurations for best-practice drift, wrong primitive/product choices, missed optimizations, product misconfiguration, security gaps, reliability risks, and cost footguns. Use when reviewing repo/account evidence for Workers, Pages, Wrangler, Static Assets, KV, D1, R2, Durable Objects, WorkerEntrypoint/RpcTarget RPC, Queues, Workflows, Workers AI, AI Gateway, Vectorize, Images, Stream, Browser Run, Dynamic Workers, Containers, Pipelines, Workers VPC, Email bindings, Secrets Store, Agents SDK, Artifacts, Analytics Engine, Workers Logs, CDN/cache, DNS, WAF, Access/Zero Trust, Cloudflare account settings, pricing/overages, budget alerts/spend monitoring, runaway-loop bill diagnosis, or IaC decisions. Do not use for generic Cloudflare status-page/uptime questions, product news, or conceptual Cloudflare explainers without project/config/account evidence to audit.
    0
    installs
  8. Guardrails · adewale bundle
    Code quality verification gates wired into the agent lifecycle. Use this skill whenever writing, modifying, reviewing, or debugging code — including new features, bug fixes, refactors, troubleshooting, CI/CD setup, or project bootstrapping. Also use when the user mentions "quality", "testing strategy", "CI pipeline", "guardrails", "debugging", or asks how to improve code reliability. If you're writing code or trying to understand why code isn't working, this skill applies. Do not use for README/prose-only edits, copywriting, or documentation wording changes unless the user asks for code/build/CI verification or the docs change affects generated/runtime output.
    0
    installs
  9. Python Workers · adewale bundle
    Skill for building Cloudflare Workers in Python. Focuses on what is unique to the Python/Pyodide runtime — the JS/Python FFI boundary, JsProxy conversion, HTTP client compatibility, cold start management, package compatibility, and testing strategies. For general Cloudflare Workers concepts (bindings, caching, routing), see the Cloudflare Workers docs.
    0
    installs
  10. Swiss Poster · adewale bundle
    Apply a Swiss Poster design system using Tailwind CSS. Use when asked to style a webpage with poster-style layouts where one dominant graphic event breaks the grid, overlaps, bleeds/crops at the edge, uses microtype, hard figure/ground contrast, and extreme typographic scale. Implements IBM Plex Sans, stone color palette, opacity hierarchy, and compositional techniques from Weingart, Troxler, Hofmann, and Odermatt & Tissi.
    0
    installs
  11. Agentic Mermaid Live Editor Development · adewale
    Develop and debug the Agentic Mermaid browser editor, including its modular UI, render/verify pipeline, examples, configuration, exports, URL sharing, website integration, and browser regression tests.
    0
    installs
  12. Agentic Mermaid Diagram Workflow · adewale bundle
    Agent-agnostic skill for authoring and editing Mermaid diagrams with structured verification, typed mutation, round-trip serialization, and graphical, terminal, and layout outputs. The live capability registry identifies renderable and mutable families; unmodeled syntax remains source-preserved.
    0
    installs
  13. Good Pr · adewale bundle
    Help users prepare and review pull requests that maintainers actually want to merge. Use this skill whenever someone asks for help writing a PR description, preparing a contribution to an open-source project, reviewing their own PR before submitting, writing a bug fix PR, drafting a feature PR, or asks anything like "how do I make a good pull request", "review my PR", or "why do my PRs keep getting rejected". Also trigger when a user shares a diff or patch and wants help presenting it, when they mention contributing to a repo they don't maintain, when they're preparing their first contribution to a project, or when they want a pre-submission sanity check. Even if the user doesn't explicitly mention "PR" — if they're packaging a code change for someone else to review, this skill applies.
    0
    installs
  14. Testing Best Practices · adewale bundle
    Enforce testing best practices when writing, reviewing, or improving tests. Covers TDD/red-green-refactor, property-based testing, real objects over mocks, correctness by construction, assertion quality, E2E/contract tests, flaky-test upgrades, mock-reality drift, mutation-style gap analysis, and sabotaged/skipped/weak tests. Use when writing tests, reviewing test quality, fixing flaky tests, improving coverage quality, or when the user mentions TDD, testing, coverage, mocks, invariants, types vs tests, defense in depth, or test quality.
    0
    installs
  15. Good Repo · adewale bundle
    Audit and configure the public GitHub repository surface: launch readiness, repo quality/adoption/trust, discoverability, contribution readiness, topics, homepage URL, description, issues/wiki/license/CI settings, owner/org-wide repo audits, repo popularity/adoption signals, README/package/GitHub metadata drift, URL/license/topics gaps, and Agent Skill repo packaging/evals. Use when the user asks for repo-level readiness, repo metadata/configuration, or visitor/contributor trust. Do not trigger for README-only writing, one PR descriptions/reviews, function-level code tests, or general implementation/architecture work; defer those to narrower specialists unless the user explicitly asks for repo-level readiness/proof/metadata judgment.
    0
    installs
  16. Slide Maker · adewale bundle
    Generate presentation decks grounded in real GitHub projects, or walk through a structured brief-to-slides process. Use when the user asks to create a presentation, slide deck, talk, pitch, keynote, or Slidev project — especially when they want slides based on an existing codebase, architecture, or project documentation.
    0
    installs
  17. Pages · adewale bundle
    The Skill
    0
    installs
  18. Good Readme · adewale bundle
    Create and improve README documents for GitHub projects. Use when the user wants to write a new README, improve an existing one, audit README quality, or asks about documentation best practices for their repository.
    0
    installs