Showing 33991–34020 of 44647 skills
Break an approved steno design into an ordered, traceable task list (tasks.md). Use when the spec phase is "tasks".
rizanw/steno-spec
Execute the full end-to-end permission matrix against the live Uniffy app through the two Playwright MCP browsers: every sharing, access, denial, viewing, revocation, and request-access case on every content domain (notes, files, projects, tasks, calendar, chat, agents, automations, rooms), proven as the affected user. Covers the PostgreSQL-authoritative access behaviors: instant revocation in search and mentions, per-surface search authorization (spotlight, domain searches, filters, pagination), restricted chips, access requests, COMMENTER and role floors, expiry-aware grants, live org-default inheritance, group membership churn, delete and tag and bookmark revocation, attachment byte gating, and live no-reload pruning. Use when asked to run the permission matrix, matrix-test the permission system, do a full e2e sweep of sharing and access control, or validate a permissions PR end to end. Use `uniffy-e2e-flows` for a lighter single-domain permission loop and `uniffy-playwright` for one-off browser inspection. Skip for unit or integration tests, backend-only work, or when the dev stack is not running and the user has not asked to start it.
uniffy-io/uniffy
Reference for the Discovery phase: requirements discovery and scoping.
ilandahan/AID
Website Operations OS for AI Agents. Use this skill whenever an agent must understand, modify, deploy, verify, troubleshoot, secure, back up, or operate a website — especially a production website. Enforces risk assessment, backup-before-risk, stop conditions, semantic production verification, fix-one-scan-class, and a self-improving local experience loop. Triggers: deploy / release, website down, 500 errors, bad deployment, database or data changes, DNS or domain changes, SSL issues, SEO checks, performance problems, backup and recovery, security review, incident response, rollback, "check my website", "fix my site".
DitoSun/sitepilot
微信读书助手 — 搜索书籍、管理书架、查看笔记划线、浏览书评、阅读统计、发现推荐好书
Tencent/WeChatReading
Drafts or rewrites a work message without changing its ask or stance; use only when the user says "compose", "run compose on" or "polish this message", or asks Claude to draft a message Claude will post or send for them (Slack, email, Jira comment).
by-carlos/daikenja
Reviews a document against a predetermined checklist: clarity, undefined terms, unenforced rules, undated decisions, missing owners, contradictions, and obvious stale content. Use when the user says "review this doc", "review this page", "check this before I publish", or pastes a document and asks for a check before sharing it. Read-only -- it reports findings, it never edits or rewrites the document.
by-carlos/daikenja
Checks a thread or a document against the project ledger and general knowledge and hands back a verdict: what is being claimed or asked, which parts a recorded decision settles, which parts are plain fact, and what is presented as settled without being established. Use when the user says "is this right?", "check this against the ledger", "give me a judgement on this thread", or asks for a quick "AI review summary" of a page or pull request to share with the team. Read-only -- it never drafts a reply, never edits the document and never writes the ledger.
by-carlos/daikenja
Derives your writing-style.md from writing samples you supply, backing up whatever the file held first. It records style rules only, never facts about people or projects.
by-carlos/daikenja
Turns a meeting transcript into proposed ledger entries: decisions made, action items with owners and dates, and questions left unresolved. Use when the user pastes a transcript or asks what came out of a call. It classifies only and writes nothing itself.
by-carlos/daikenja
Challenges a draft before it goes out and hands back a revised version plus the facts only you can supply -- the six substance checks, then a set of reviewer personas whose wording problems it fixes. Never sends anything.
by-carlos/daikenja
Reports what changed in a project's Daikenja ledger since the user last checked, read from git history of each repository's DECISIONS.md and the home repository's open.md, then advances each repository's checkpoint on approval. The only skill that writes last_checkpoint in daikenja.yaml; it never touches ledger content. Accepts an optional project key -- `/daikenja:project-catchup <key>` reads that project from anywhere.
by-carlos/daikenja
Looks up what is decided about a specific topic in a project's Daikenja ledger -- the decisions in force in every repository's DECISIONS.md -- with each entry's history from git and its linked issue or ADR, plus the open items that bear on it. Read-only; writes nothing. Accepts an optional project key -- `/daikenja:project-decisions <key>` reads that project from anywhere.
by-carlos/daikenja
Audits a project's Daikenja ledger for open items with no owner or that have sat too long; only Open items are in scope. Read-only; writes nothing. Accepts an optional project key -- `/daikenja:project-gaps <key>` reads that project from anywhere.
by-carlos/daikenja
Lists every project registered in daikenja.yaml, says which one the current directory resolves to, and reports whether each project's ledger actually exists. Read-only; it never repairs what it reports.
by-carlos/daikenja
Records decisions, open items and sources in a project's ledger. Use when the user says "log this", "record this decision", "add this to the ledger", or asks for what was settled to be written down.
by-carlos/daikenja
Reports which of a project's tracked sources moved since they were last read, by comparing each source's stored last-modified value against what its system reports now. Read-only against the ledger; recording a re-read goes through /daikenja:project-log. Accepts an optional project key -- `/daikenja:project-sources <key>` reads that project from anywhere.
by-carlos/daikenja
Gives a full-state overview of a project's Daikenja ledger, written for someone with no prior context. Read-only; writes nothing. Accepts an optional project key -- `/daikenja:project-summary <key>` reads that project from anywhere.
by-carlos/daikenja
Records what the user says about a person they write to, so later messages are written for that reader. Use when the user says "remember that S challenges every technical claim", "log this persona", or describes a recipient while drafting and wants that kept.
by-carlos/daikenja
Reviews how the user themselves handled a thread they took part in, with private, direct, evidence-backed coaching on their own moves. Findings are about the user alone, and nothing is written, logged or sent.
by-carlos/daikenja
Registers the project you are in with Daikenja, sets its per-project settings, and optionally seeds its ledger from sources the project already has.
by-carlos/daikenja
One-time and re-runnable personal setup for Daikenja: creates your configuration, captures your profile, seeds the persona, writing-style and glossary files, and applies any pending version upgrade.
by-carlos/daikenja
Installs, updates, or removes Tensei, the Daikenja way of working (~/.claude/daikenja/tensei.md): how answers are shaped, how designs are recommended, and how the work behind them is done. Shows what changes, asks once to adopt it, adds the CLAUDE.md import line, and backs up anything it would overwrite.
by-carlos/daikenja
Reads a Slack or email thread, summarizes what is being asked and by whom, then collects context from the user before any reply is drafted. Use when the user pastes a thread link or a block of chat history, or says "help me answer this". It gathers only and never writes the reply.
by-carlos/daikenja
Initialize or repair the local OYYO LinkedIn workspace and explain installation. Use when the user asks to install, configure, onboard, create local state, or check whether the pack is ready.
vpicciuolo/Linkedin-SuperAgent-MultiSkills
Create GitHub Pull Request for feature request from specification file using pull_request_template.md template.
stribus/pygerengastos
Master Python 3.12+ with modern features, async programming, performance optimization, and production-ready practices. Expert in the latest Python ecosystem including uv, ruff, pydantic, and FastAPI.
stribus/pygerengastos
Guide for quality focused software architecture. This skill should be used when users want to write code, design architecture, analyze code, in any case that relates to software development.
stribus/pygerengastos
System-design thinking before any doc or code: goals/non-goals, back-of-envelope numbers, components and contracts, failure modes, operability, security, trade-offs. Use for "design this system", "architecture for X", "trade-offs for X", "how should we architect", "API design", "data model for", "service boundaries", or before an ADR. Hands off to /ship:write-docs to record the decision. Not implementation planning (/ship:design — that turns a decided design into stories).
heliohq/ship
Plan implementation before coding: investigate the repo, write spec and plan, and validate with a peer. Use for "plan", "design approach", "scope", or any coding task needing a plan. Not system-design thinking (/ship:arch-design) or full /ship:auto.
heliohq/ship