<Devsly/>
NotebookLM Watermark Remover
Remove the NotebookLM watermark from PDF slide exports — free, unlimited, and 100% in your browser.
View
NotebookLM Video Watermark Remover
Remove the NotebookLM watermark from every frame of your MP4 and auto-trim the end card — free and unlimited.
View
Gemini Watermark Remover
Remove the Gemini (Veo) sparkle watermark from every frame of your AI-generated MP4 — free and unlimited.
View
MCP https://devsly.io/mcp MCP Tools Best Skills API Docs

Keyboard Shortcuts

Navigation

Quick Search
⌘ / Ctrl + K
Toggle Dark Mode
⌘ / Ctrl + D
Close Dialogs
Esc

Tool Actions

Execute / Process
⌘ / Ctrl + Enter
Clear Input
⌘ / Ctrl + Shift + C
Copy Output
⌘ / Ctrl + Shift + X

Editor

Select All
⌘ / Ctrl + A
Undo
⌘ / Ctrl + Z
Redo
⌘ / Ctrl + Shift + Z

Updated 4d ago

by zvadaadam

az-skills

A curated set of skills I use with my agents <3

  • Active — Updated in the last 14 days

50 GitHub stars (50)

Steady at 50 stars — no new stars in the 4 days since Oct 12.

  • 24 skills (24 skills found in its SKILL.md files)
  • 6 forks (6 forks)
  • 4d ago last update (Last updated 4d ago)

Install

Skills CLI

npx skills add zvadaadam/az-skills

Asks which skills and agents to install. Just one: npx skills add zvadaadam/az-skills --skill design-roundtable — add -g for every project.

Claude Code

git clone https://github.com/zvadaadam/az-skillscp -r "az-skills/skills/design/design-roundtable" ~/.claude/skills/

Copies the design-roundtable skill into ~/.claude/skills/ for every project (use .claude/skills/ for one project). Repeat for the other skills listed below.

Plugin

/plugin marketplace add zvadaadam/az-skills

Run inside Claude Code if the repository ships a plugin marketplace, then pick plugins from /plugin.

Skills can run code on your machine — read the SKILL.md first.

What it does

In the author's own words, from each skill's SKILL.md.

  • design-roundtable

    5 legendary designers debate your brief in parallel using the most powerful AI model available. Spawns sub-agents as Dieter Rams, Jony Ive, Massimo Vignelli, Naoto Fukasawa, and Hella Jongerius — each explores independently, then synthesizes into a ranked consensus. Use when starting a new screen, component, or visual direction and you want breadth before committing.

    skills/design/design-roundtable/SKILL.md on GitHub (opens in a new tab)
  • az-skills-feedback

    Submit feedback about az-skills to Hivenet. Use when a skill, tool, doc, CLI, MCP, or API is broken, confusing, missing, outdated, or notably good; when an az-skills task fails after real effort or needs a workaround; or when continuing a feedback thread or answering a team question.

    skills/engineering/az-skills-feedback/SKILL.md on GitHub (opens in a new tab)
  • call-advisor

    Call the premium Fable advisor through Claude Code CLI from Codex for hard judgment, architecture, product thinking, frontend/design critique, and high-stakes decisions. Treat the advisor as the smartest and most expensive local AI. Use when the user asks to call an advisor, consult Fable/Claude, get a second opinion, compare another agent's output, improve design quality, reason through a hard p…

    skills/engineering/call-advisor/SKILL.md on GitHub (opens in a new tab)
  • call-worker

    Call the fast Codex GPT-5.5 worker through Codex CLI from Codex or another terminal for clean code implementation, focused repo exploration, tests, refactors, bug fixes, and mechanical engineering tasks. Treat the worker as fast and strong at code, but less suited than the Fable advisor for hard judgment and frontend/design taste. Use when the user asks to call a worker, trigger Codex from the CL…

    skills/engineering/call-worker/SKILL.md on GitHub (opens in a new tab)
  • code-review

    Multi-lens code review — spawns parallel sub-agents to independently review branch changes for bugs, security, and design, then validates and reports only high-signal findings. Use when you want a thorough review before merging or when self-reviewing your own changes.

    skills/engineering/code-review/SKILL.md on GitHub (opens in a new tab)
  • code-simplifier

    Simplifies and refines code for clarity, consistency, and maintainability while preserving all functionality. Use when asked to "simplify code", "clean up code", "refactor for clarity", "improve readability", or review recently modified code for elegance. Focuses on project-specific best practices.

    skills/engineering/code-simplifier/SKILL.md on GitHub (opens in a new tab)
  • complexity-check

    After making changes, audit the diff through four lenses — Additions, Premises, Spread, Duplicates — to catch overbuilt changes and surface simplification opportunities the change itself can't see. Use after implementing a feature, refactor, or bug fix, before committing. Apply only the lenses that have signal to find for your diff; mark the rest N/A.

    skills/engineering/complexity-check/SKILL.md on GitHub (opens in a new tab)
  • deslop

    Remove AI-generated code slop and clean up code style

    skills/engineering/deslop/SKILL.md on GitHub (opens in a new tab)
  • devs-roundtable

    5 legendary engineers debate your problem in parallel using the most powerful AI model available. Spawns sub-agents as John Carmack, Rich Hickey, Sandi Metz, Linus Torvalds, and Kent Beck — each explores independently, then synthesizes into a ranked consensus. Use when facing architectural decisions, non-obvious implementation choices, or when you want to stress-test an approach from multiple ang…

    skills/engineering/devs-roundtable/SKILL.md on GitHub (opens in a new tab)
  • greenlight-pr

    Greenlight a PR — fix CI failures, triage review comments, iterate until green.

    skills/engineering/greenlight-pr/SKILL.md on GitHub (opens in a new tab)
  • implementation-rehearsal

    Rehearse a proposed code change against the actual codebase without implementing it. Use when the user asks for an imagined implementation, mental dry run, or several build-and-critique passes to uncover regressions and improve the plan before coding. Produces a revised recommendation; ordinary implementation requests do not require this review.

    skills/engineering/implementation-rehearsal/SKILL.md on GitHub (opens in a new tab)
  • pre-factor

    Before implementing a feature or non-trivial change, scan the code it will land in and surface prep refactors that make the change easy — so the feature lands clean instead of accreting tech debt (Kent Beck "make the change easy, then make the easy change"). Use BEFORE writing code, when about to build a feature, add a new case/provider/handler to an existing pattern, restructure in service of up…

    skills/engineering/pre-factor/SKILL.md on GitHub (opens in a new tab)
  • repo-history-book

    Build a durable, evidence-backed "book" of how an engineering project evolved by mining git history, PRs, releases, and docs. Use when the user wants repository archaeology, commit-by-commit walkthroughs, engineering learning extraction, pivot analysis, or a readable chronology of what the team changed, learned, reverted, and refined over time.

    skills/engineering/repo-history-book/SKILL.md on GitHub (opens in a new tab)
  • setup-agent-workflow

    Set up or improve a repository so AI agents can understand the product, make changes, and verify them with less repeated human correction. Use when bootstrapping agent workflows, onboarding agents to an unfamiliar codebase, improving AGENTS.md and local skills, or turning recurring agent mistakes and throwaway scripts into durable tooling. Inspects and reuses existing conventions, implements the…

    skills/engineering/setup-agent-workflow/SKILL.md on GitHub (opens in a new tab)
  • tour

    Take a guided tour of a codebase subsystem — explore the code in parallel, then produce a self-contained HTML tour document that teaches the architecture so the reader doesn't need to read the code themselves. Optionally critiques the architecture for issues.

    skills/engineering/tour/SKILL.md on GitHub (opens in a new tab)
  • verify-harness

    Give a repository a verification harness its agents actually use — a `control-<app>` driver CLI that runs the real app in an isolated session and drives it the way a person and an agent do, plus a user-POV feature map that says what exists, how to reach it, how to prove it and what misleads — then keep it true. Use to set one up in a fresh repo, to expand or maintain the map, to verify a change w…

    skills/engineering/verify-harness/SKILL.md on GitHub (opens in a new tab)
  • ai-answer-audit

    Audit an AI answer back to the searches, sources, citations, and assumptions behind it — which results actually shaped it, and which claims are unsupported model guesswork. Traces what the answer was based on; does not grade whether it is correct. User-run on an answer (with its question if available); read-only — never alters the answer.

    skills/marketing/ai-answer-audit/SKILL.md on GitHub (opens in a new tab)
  • brand-name-explore

    Multi-persona naming exploration with consensus. Spawns parallel sub-agents — each embodying a different naming philosophy (David Placek's Lexicon methodology, the Poet, the Linguist, the Culture Hacker, the Futurist) — to explore divergent naming directions for a product or company, then synthesizes into a ranked shortlist. Based on David Placek's naming framework (Lexicon Branding — Swiffer, Bl…

    skills/marketing/brand-name-explore/SKILL.md on GitHub (opens in a new tab)
  • geo-optimize

    Turn an ai-answer-audit into a prioritized plan to get a brand cited in AI answers (ChatGPT, Perplexity, Google AI Overviews). Acts only on the audit's affectable content layer — earned citations, your own pages, open territory — and never promises to move the model layer. User-run on an audit + your brand/URL; a one-shot plan, not citation monitoring.

    skills/marketing/geo-optimize/SKILL.md on GitHub (opens in a new tab)
  • product-rehearsal

    Rehearse a proposed feature as if it had already shipped, before anyone builds it. Walks a concrete user or agent through finding it, using it and hitting its edges, then revises the proposal. Use when the user asks to imagine a feature being live, how it would affect users or agents, how it would actually be used, where it will be bad, or which product corner cases a feature idea, tool, command…

    skills/product/product-rehearsal/SKILL.md on GitHub (opens in a new tab)
  • interview-me

    Interview the user about a plan, design, or idea until reaching shared understanding. Walks down every branch of the decision tree, resolving dependencies one by one. Maintains a durable transcript on disk so the interview survives context loss. Use when you want to stress-test a plan, think through a design, or need the agent to gather all the context it needs before building.

    skills/productivity/interview-me/SKILL.md on GitHub (opens in a new tab)
  • noah-zender-it

    Rank mental models from Noah Zender's curated 468-item idea library by leverage for your current situation, with one concrete way to apply each. Use when you're at a decision point — naming, positioning, writing, picking a project, scoping work — and you want frameworks that actually fit your case, not generic mental-models advice. Default source library: noahzender.com/ideas.

    skills/productivity/noah-zender-it/SKILL.md on GitHub (opens in a new tab)
  • plan-for-goal

    Turn whatever's in the current conversation into one prompt to hand to the agent's `/goal` orchestration loop (Claude Code, Codex, or any harness with the same shape). The prompt is re-injected on every turn of the loop, so it must hold direction, taste, and a self-verification path across many iterations. Use when you're ready to hand a piece of work to `/goal`.

    skills/productivity/plan-for-goal/SKILL.md on GitHub (opens in a new tab)
  • plan-for-mega-goal

    Turn a multi-objective piece of work into a roadmap on disk plus a small pointer prompt for the agent's `/goal` orchestration loop. Each sub-goal in the roadmap is shaped like a single `plan-for-goal` output; the roadmap holds the multi-goal scaffolding that wouldn't fit in `/goal`'s 4000-character objective limit. Use when the conversation has 3+ distinct objectives that share a destination.

    skills/productivity/plan-for-mega-goal/SKILL.md on GitHub (opens in a new tab)

Review before you install

A skill is a set of instructions and scripts your agent will follow, and it can run code on your machine. Read the SKILL.md and any scripts first — this listing is not a security review.