Architecture & codebase
12,712 rows, by stacks then stars
1,011 of these skill files have been read, by 858 distinct authors, and what they tell an agent counted. What Architecture & codebase authors agree on, and what they forbid
IdkwhatImD0ing/hackathonstarterkit/.agents/skill-improvement-workspace/baseline-skills/scaffold-backend Skill
no license2★ repoPRD-driven backend scaffold. Reads AGENTS.md and PRD.md from the repo root and creates a FastAPI app inside server/ with optional Supabase integration and one stub route per entry listed under PRD.md > Backend Routes. Refuses to run if AGENTS.md and PRD.md do not exist, or if PRD.md says Backend Needed? = No. Run AFTER scaffold-frontend.
IdkwhatImD0ing/hackathonstarterkit/.agents/skill-improvement-workspace/baseline-skills/scaffold-frontend Skill
no license2★ repoPRD-driven frontend scaffold. Reads AGENTS.md and PRD.md from the repo root and creates a Next.js + TypeScript + Tailwind app inside client/ with pages, navigation, and placeholder components that match the PRD. Refuses to run if AGENTS.md and PRD.md do not exist. Run this AFTER domain-to-spec.
IdkwhatImD0ing/hackathonstarterkit/.agents/skills/quickstart Skill
no license2★ repoOrchestrate a new project from idea to running scaffold by chaining `domain-to-spec`, `scaffold-frontend`, and optional `scaffold-backend`. Use this skill when the user wants a one-shot setup, full-stack bootstrap, empty-repo starter, or guided path from rough idea to `AGENTS.md`, `PRD.md`, `client/`, and optionally `server/`.
IdkwhatImD0ing/hackathonstarterkit/.agents/skills/scaffold-backend Skill
no license2★ repoCreate a PRD-driven FastAPI backend in `server/` from repo-root `AGENTS.md` and `PRD.md`. Use this skill after frontend scaffolding only when `PRD.md` says `Backend Needed?` is Yes, especially for API routes, Pydantic models, health checks, optional Supabase wiring, and type-safe placeholder data.
IdkwhatImD0ing/hackathonstarterkit/.agents/skills/scaffold-frontend Skill
no license2★ repoCreate a PRD-driven Next.js frontend in `client/` from repo-root `AGENTS.md` and `PRD.md`. Use this skill after `domain-to-spec` when the user wants the initial UI scaffold, pages, navigation, types, and optional API client generated from the confirmed PRD.
vahagn-madatyan/netsec-skills-suite/skills/config-management Skill
2★ repoConfiguration backup, drift detection, and golden config validation across Cisco IOS-XE/NX-OS, Juniper JunOS, and Arista EOS. Covers running vs startup comparison, config archival, section-level drift analysis, and compliance validation for ongoing configuration assurance.
ajaygodbole7/rest-api-skill/skills/api-contract-review Skill
no license2★ repoUse when reviewing or auditing an existing OpenAPI 3.1 specification for compliance with Zalando RESTful API Guidelines. Produces a structured checklist report (BLOCKER / WARNING / INFO severity) covering naming, security, HTTP usage, pagination, compatibility, and all other rule categories. Activate for API review, contract audit, or spec compliance checking tasks.
t4sh/dotfiles/agents/skills/architecture Skill
no license2★ repoCreate or evaluate an architecture decision record (ADR). Use when choosing between technologies (e.g., Kafka vs SQS), documenting a design decision with trade-offs and consequences, reviewing a system design proposal, or designing a new component from requirements and constraints.
The same file is in 4 other repositories
t4sh/dotfiles/agents/skills/codebase-design Skill
no license2★ repoShared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.
The same file is in 19 other repositories
t4sh/dotfiles/agents/skills/feature-dev Skill
no license2★ repoGuided feature development with codebase understanding and architecture focus. Use for implementing features systematically: explore → clarify → design → implement → test → review.
t4sh/dotfiles/agents/skills/improve-codebase-architecture Skill
no license2★ repoScan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.
The same file is in 8 other repositories
t4sh/dotfiles/agents/skills/init-rulebook Skill
no license2★ repoLoad the user-level agent rulebook — an `~/.agents/AGENTS.md` index plus every referenced `rules/*.md` — so one consistent, portable baseline applies across any agent app (Claude Code, Codex, Conductor, Copilot, Craft-Agents,Cursor, OpenCode etc.). Re-run after context compaction to rehydrate. Triggers: init rulebook, reload rulebook, load user-level agent rules.
t4sh/dotfiles/agents/skills/migrate-to-shoehorn Skill
no license2★ repoMigrate test files from `as` type assertions to @total-typescript/shoehorn. Use when user mentions shoehorn, wants to replace `as` in tests, or needs partial test data.
The same file is in 15 other repositories
t4sh/dotfiles/agents/skills/monorepo-management Skill
no license2★ repoMaster monorepo management with Turborepo, Nx, and pnpm workspaces to build efficient, scalable multi-package repositories with optimized builds and dependency management. Use when setting up monorepos, optimizing builds, or managing shared dependencies.
The same file is in 4 other repositories
t4sh/dotfiles/agents/skills/refactoring-ui Skill
no license2★ repoAudit and fix visual hierarchy, spacing, color, and depth in web UIs. Use when the user mentions "my UI looks off" (or amateur/unprofessional), "fix the design", "Tailwind styling", "color palette", "visual hierarchy", "design system", "spacing scale", or "component styling". Also trigger when building consistent design tokens, creating dark mode themes, improving data-visualization clarity, or polishing UI details before launch. Covers grayscale-first workflow, constrained design scales, shadows, and component styling. For typeface selection, see web-typography. For usability audits, see ux-heuristics.
The same file is in 3 other repositories
t4sh/dotfiles/agents/skills/request-refactor-plan Skill
no license2★ repoCreate a detailed refactor plan with tiny commits via user interview, then file it as a GitHub issue. Use when user wants to plan a refactor, create a refactoring RFC, or break a refactor into safe incremental steps.
The same file is in 13 other repositories
t4sh/dotfiles/agents/skills/scaffold-exercises Skill
no license2★ repoCreate exercise directory structures with sections, problems, solutions, and explainers that pass linting. Use when user wants to scaffold exercises, create exercise stubs, or set up a new course section.
The same file is in 12 other repositories
t4sh/dotfiles/agents/skills/setup-matt-pocock-skills Skill
no license2★ repoConfigure this repo for the engineering skills — set up its issue tracker, triage label vocabulary, and domain doc layout. Run once before first use of the other engineering skills.
The same file is in 6 other repositories
t4sh/dotfiles/agents/skills/setup-pre-commit Skill
no license2★ repoSet up Husky pre-commit hooks with lint-staged (Prettier), type checking, and tests in the current repo. Use when user wants to add pre-commit hooks, set up Husky, configure lint-staged, or add commit-time formatting/typechecking/testing.
The same file is in 19 other repositories
t4sh/dotfiles/agents/skills/skill-architect Skill
no license2★ repoArchitect and audit portable agent skills for retrieval, predictability, progressive disclosure, evals, and repository gates. Use when the user asks to "create a skill", "author a skill", "improve a skill", "review a skill", "refactor a skill", "compare skill rubrics", "distill a skill from sessions", "reconcile skill plans", or "teach skill authoring"; when paths include `skills/<name>/SKILL.md`, `references/*.md`, helper scripts, evals, lockfiles, security manifests, or vendor adapters; or when mentions include skill-creator, Skill Development, skills.sh, trigger descriptions, completion criteria, leading words, or model/user invocation.
t4sh/dotfiles/agents/skills/system-design Skill
no license2★ repoDesign systems, services, and architectures. Trigger with "design a system for", "how should we architect", "system design for", "what's the right architecture for", or when the user needs help with API design, data modeling, or service boundaries.
The same file is in 5 other repositories
t4sh/dotfiles/agents/skills/tech-debt Skill
no license2★ repoIdentify, categorize, and prioritize technical debt. Trigger with "tech debt", "technical debt audit", "what should we refactor", "code health", or when the user asks about code quality, refactoring priorities, or maintenance backlog.
The same file is in 5 other repositories
GlamgarOnDiscord/claude-saas-blueprint/.claude/skills/env-setup Skill
2★ repoConfigure l'environnement de développement pour un SaaS Next.js + Supabase + Vercel : outils CLI, variables d'env, RTK, vérifications.
GlamgarOnDiscord/claude-saas-blueprint/.claude/skills/refactor Skill
2★ repoRefactoring sûr et méthodique. Améliorer sans casser.
GlamgarOnDiscord/claude-saas-blueprint/.claude/skills/saas-init Skill
2★ repoBootstrap complet d'un projet SaaS from scratch. Système de Q/R interactif pour configurer chaque aspect.
nanxiaoyao/network-huawei-skills/interface-config Skill
2★ repoThis skill should be used when the user asks to configure or troubleshoot physical interfaces and link aggregation (Eth-Trunk) on Huawei CloudEngine / S series switches. Covers interface attributes (speed, duplex, MTU, jumbo frame, flow control, PoE, error packets), Eth-Trunk in manual and LACP modes, M-LAG/iStack cross-device aggregation, and interface fault diagnosis. Applicable platforms S/CE switches (V200R011C10+/V200R022C00+) and USG firewalls (V500R005C20+/V600R007C20+).
nanxiaoyao/network-huawei-skills/nat-config Skill
2★ repoThis skill should be used when the user asks to configure, inspect, or troubleshoot NAT on Huawei USG6000E series firewalls. Covers source NAT (NAT-policy / NAPT / Easy-IP), destination NAT (NAT Server), bidirectional NAT, NAT64/NAT46, and CGN scenarios. Applicable platforms USG6000E V600R007C20+ and USG6000/USG9500/NGFW Module V500R005C20+ (CLI syntax identical between versions).
nanxiaoyao/network-huawei-skills/ospf-config Skill
2★ repoThis skill should be used when the user asks to configure or troubleshoot OSPF on Huawei switches (S1720/S2700/S5700/S6720 V200R011C10+ and CloudEngine 5800-9800 V200R022C00+) or USG firewalls. Covers multi-area OSPF, VLANIF-based OSPF on switches, DR/BDR election, Stub/NSSA areas, route import, route summarization, OSPF-BFD linkage, OSPF GR, and IP FRR. Applicable to both switch (VLANIF interface) and firewall (Layer-3 interface) scenarios.
nanxiaoyao/network-huawei-skills/vlan-config Skill
2★ repoThis skill should be used when the user asks to configure or troubleshoot VLANs on Huawei CloudEngine / S series switches. Covers VLAN creation, access/trunk/hybrid port modes, VLANIF Layer-3 inter-VLAN routing, voice VLAN, management VLAN, VLAN isolation (Layer-2/3), and VLAN tag manipulation. Applicable platforms S/CE switches (V200R011C10+/V200R022C00+) as primary scope; USG firewalls (V500R005C20+/V600R007C20+) only use VLAN in transparent mode or policy filtering.
jacob-balslev/skills/skills/agent-ops/gemini-pro Skill
2★ repoUse when deciding whether to route a task to Google's Gemini Pro frontier model (current Gemini 3.1 Pro generation, moving to Gemini 3.5 Pro) instead of Claude Opus or GPT-5 — especially for very-large-context reasoning (1M-token input), whole-codebase or long-document analysis, native multimodal input (audio/video/PDF/image in one call), or capability-per-dollar at the frontier. Covers the context window, the 200K context-tier pricing cliff, multimodal support, and the per-lane comparison against Claude Opus / GPT-5. Do NOT use for choosing the cheap/fast tier (use `gemini-flash`), for general agent-system architecture (use `agent-engineering`), or for dispatching among local skills (use `skill-router`).
jacob-balslev/skills/skills/agent-ops/skill-scaffold Skill
2★ repoUse when creating a new SKILL.md from scratch, restructuring a draft before it becomes a stable skill, or teaching another author the canonical Skill Metadata Protocol frontmatter, body, and audit-state.json sidecar structure. Covers flat schema-conformant frontmatter, the sidecar split, v8 classification, body layout by skill intent, semantic-layer discipline (description vs activation vs Coverage), teaching-layer mechanics (TEMPLATE NOTE blockquotes), native skill-creator handoff, public/private safety, and routing-eval honesty. Do NOT use when modifying an already-written skill (edit it directly), writing general technical documentation, routing an existing request across skills, or fixing malformed library health at scale (use `skill-infrastructure`).
jacob-balslev/skills/skills/backend-engineering/api-design Skill
2★ repoUse when designing or reviewing HTTP API surfaces: consumer tasks, audience class, protocol/paradigm fit, resources/actions, route taxonomy, request and response schemas, status codes in context, pagination, filtering, sorting, field selection, idempotency, auth and tenant boundaries, error envelopes, rate-limit signals, versioning, deprecation, discovery, and contract artifacts. Do NOT use for pure HTTP protocol semantics (use `http-semantics`), framework-specific route handler mechanics (use `route-handler-design`), non-HTTP system contracts (use `system-interface-contracts`), async event contracts (use `event-contract-design`), database design (use `entity-relationship-modeling`), inbound provider webhook mechanics (use `webhook-integration`), or post-failure diagnosis (use `debugging`).
jacob-balslev/skills/skills/backend-engineering/http-semantics Skill
2★ repoUse when designing or reviewing HTTP-based systems where method semantics, status codes, idempotency, safe methods, conditional requests, content negotiation, caching headers, range requests, integrity digests, or representation metadata are load-bearing. Covers the RFC 9110/9111/9112 contract layer below any specific framework. Do NOT use for API surface shape and route taxonomy (use api-design), for WebSocket or SSE bidirectional streams (use streaming-architecture skill when available), for vendor-specific webhook signing (use webhook-integration), or for transport-level concerns like TLS or QUIC (use platform-level documentation).
jacob-balslev/skills/skills/backend-engineering/route-handler-design Skill
2★ repoUse when designing or reviewing Next.js Route Handlers (the `route.ts`/`route.js` file convention in App Router): when a Route Handler is the right public HTTP endpoint surface vs Server Actions or Server Components, the HTTP-method-as-export contract (GET/POST/PUT/PATCH/DELETE/HEAD/OPTIONS), the Web-standard Request/Response interface (no Node `req`/`res`), the body-parsing primitives (`request.json`/`formData`/`text`/`blob`/`arrayBuffer`) and one-shot body consumption, the default caching behavior of GET responses (NOT cached by default since Next 15; opt IN via `dynamic = 'force-static'`) and the Cache Components `use cache` model, async `params`/`cookies`/`headers` and `RouteContext` typed params, dynamic segments and search params, the rule that every Route Handler is a PUBLIC surface that must authenticate/authorize/validate inside the handler, manual CORS, runtime/deployment selection (Node default and recommended after Vercel folded standalone Edge Functions onto Vercel Functions; the Edge runtime still selectable; `maxDuration`/`preferredRegion`/static-export limits), streaming via `ReadableStream` including `pull()` backpressure, status-code and header discipline, error responses, webhook-style handlers (signature verify before parse, ACK fast, `after()` for short post-response work), and the design rule that a Route Handler is the right surface when the caller is not your own Next.js UI. Do NOT use for internal mutations triggered from your own UI (use server-actions-design), for render-time reads from your own Server Components (call the data source directly), for the broader REST/contract/versioning discipline (use api-design), for HTTP method/status semantics in the abstract (use http-semantics), for request preprocessing across all routes — now `proxy.ts`/`middleware.ts` (use middleware-patterns), or for the broader webhook reliability story — HMAC verification, idempotency, retries, queue handoff (use webhook-integration).
jacob-balslev/skills/skills/backend-engineering/streaming-architecture Skill
2★ repoUse when reasoning about systems that emit a sequence of values over time and consume them incrementally: the producer/stream/consumer/backpressure/termination primitives, the difference between streaming and request-response, the difference between streaming and pub-sub messaging, how WHATWG Streams, Server-Sent Events, HTTP chunked transfer, WebSockets, gRPC streaming, and React Server Component streaming compose, push vs pull backpressure, and the failure modes (slow consumer, abandoned consumer, partial-result correctness). Do NOT use for the message-history protocol between a model and a tool runtime (use tool-call-flow), browser freshness or live dashboard UX transport choice (use real-time-updates), single-response API design (use api-design), durable worker execution and retry semantics (use background-jobs), or event payload/domain-event contracts (use event-contract-design).
jacob-balslev/skills/skills/design/color-system-design Skill
2★ repoUse when designing a color system — palette construction, semantic color tokens, WCAG contrast pairings, perceptual scale generation in OKLCH/LCH/HCT, wide-gamut fallbacks, and light/dark/high-contrast parity. Do NOT use for single brand-color picks, runtime theme-switching mechanics, token delivery architecture, or non-color design tokens.
jacob-balslev/skills/skills/design/component-architecture Skill
2★ repoThe architectural discipline of structuring a UI component library — layering, API surface design, headless/styled split, and state contracts — so component APIs survive reuse across products, themes, and teams.
jacob-balslev/skills/skills/design/form-ux-architecture Skill
2★ repoUse when designing or auditing form structure and validation UX: field grouping, required vs optional inputs, validation timing, client/server validation split, submission lifecycle, recovery, multi-step forms, and high-risk data entry. Do NOT use for labels and announcements alone (use `a11y`), validation-message wording (use `microcopy`), API schema design (use `api-design`), or stored data modeling (use `entity-relationship-modeling`).
jacob-balslev/skills/skills/design/information-architecture Skill
2★ repoUse when structuring information for findability: navigation, page hierarchy, docs architecture, sitemap shape, labeling systems, wayfinding, and content grouping. Do NOT use for formal category-governance work (use `taxonomy-design`), responsive page composition (use `layout-composition`), component/token architecture (use `design-system-architecture`), or sentence-level UI text (use `microcopy`).
jacob-balslev/skills/skills/design/visual-design-foundations Skill
2★ repoUse when designing or auditing visual craft at foundation level: color palette, typography, spacing, elevation, rhythm, density, optical alignment, visual hierarchy direction, brand fit, contrast intent, and motion feel — making a surface more legible, polished, scannable, and tone-appropriate without changing its task structure. Do NOT use for sign-system meaning (use `semiotics`), token/component architecture (use `design-system-architecture`), responsive structure (use `layout-composition`), accessibility compliance (use `a11y`), or the DEEP contract of one dimension — formal color systems (use `color-system-design`), full type systems (use `typography-system`), deep hierarchy modeling (use `visual-hierarchy`), theming/token delivery (use `theme-system-design`), or interaction-state feedback (use `interaction-feedback`).
jacob-balslev/skills/skills/frontend-engineering/client-server-boundary Skill
2★ repoUse when reasoning about the line where execution context changes between server runtime and client runtime: what values can cross via the active serializer, what cannot, how `'use client'`, `'use server'`, guard imports, and server-only file conventions mark module/function transitions, how React Server Components differ from server-rendered HTML, why Server Functions / Server Actions are reachable network endpoints, why client input is adversarial, and how server-only modules, secrets, raw records, or closures leak into client bundles and payloads. Do NOT use for choosing when and where UI is produced (use rendering-models), full Server Component read-path placement (use server-components-design), full Server Action mutation/form/cache design (use server-actions-design), public Route Handler endpoint design (use route-handler-design), HTTP wire semantics (use http-semantics), frontend codebase organization (use frontend-architecture), or API JSON contract design (use api-design).
jacob-balslev/skills/skills/frontend-engineering/design-system-architecture Skill
2★ repoUse when designing or auditing a design system's architecture: token taxonomy, semantic tokens, component APIs, theming, accessibility contracts, documentation, governance, and migration strategy. Do NOT use for information hierarchy and navigation (use `information-architecture`), page-specific layout (use `layout-composition`), visual craft direction (use `visual-design-foundations`), sentence-level UI copy (use `microcopy`), or accessibility-only audits (use `a11y`).
jacob-balslev/skills/skills/frontend-engineering/frontend-architecture Skill
2★ repoUse when organizing a frontend codebase: module boundaries, component layering, state ownership, data-flow direction, route/file colocation, public module APIs, and the separation between feature code and shared primitives. Do NOT use for visual design decisions, detailed React Server Component/read-path design, rendering-model selection, specific framework migration tactics, or backend API contract design.
jacob-balslev/skills/skills/frontend-engineering/rendering-models Skill
2★ repoUse when reasoning about how a web UI is produced and delivered: client-side rendering, server-side rendering, static-site generation, incremental static regeneration, React Server Components, streaming SSR, edge rendering, and partial prerendering. Covers the time × place grid (build/request/stream/interaction × server/edge/client), the trade-offs between first-paint latency and time-to-interactive, the relationship between rendering and hydration, and how a route's content profile (dynamic / static / personalized) maps to a model. Do NOT use for organizing the frontend codebase (use frontend-architecture), the serialization frontier between server and client code (use client-server-boundary), the wire protocol itself (use http-semantics), or specific deploy-platform composition patterns (use vercel-composition-patterns).
jacob-balslev/skills/skills/frontend-engineering/theme-system-design Skill
2★ repoUse when designing a theme system — design tokens, semantic token layering, CSS custom property strategy, runtime theme switching, and theme contract guarantees. Do NOT use for one-off color choices, brand-only palette work, or framework-specific styling-library configuration.
jacob-balslev/skills/skills/knowledge-organization/skill-evolution Skill
2★ repoUse when running or auditing Skill Graph's corpus-level `evolve` operation: the continuous skill-improvement loop that analyzes a skill library, triages a priority queue, executes bounded improve/scaffold/eval-generation actions, verifies the result, records checkpoints, and repeats. Covers `skill-graph evolve`, `lib/audit/skill-evolution-loop.js`, the Karpathy keep-or-revert spine, the priority signals based on Audit Status, standalone workspace flags, and the boundary between corpus walking and single-skill audit/improve/evaluate operations. Do NOT use for initial skill scaffolding alone (use skill-scaffold), single-skill schema/eval checks (use graph-audit or the audit operation), or generic evaluation rubric design (use evaluation / eval-driven-development).
jacob-balslev/skills/skills/quality-assurance/best-practice Skill
2★ repoCross-cutting best practices enforcement across code, templates, skills, prompts, scripts, documentation, pages, and design. The enforcement layer that catches violations any specialist might miss. Do NOT use for deep code review methodology (use code-review), application security depth (use owasp-security), accessibility implementation depth (use a11y), or specialist design-system work (use design-system-architecture, color-system-design, or typography-system).
jacob-balslev/skills/skills/software-architecture/architecture-decision-records Skill
2★ repoUse when writing, reviewing, or updating Architecture Decision Records: context, decision, options rejected, consequences, status, supersession, and follow-up verification. Do NOT use for general documentation prose (use `documentation`), code review findings (use `code-review`), or choosing between frameworks before a decision exists (use `framework-fit-analysis`).
jacob-balslev/skills/skills/software-architecture/dependency-architecture Skill
2★ repoUse when designing or auditing dependency structure: package boundaries, runtime vs build dependencies, adapter layers, duplicate-purpose libraries, supply-chain risk, upgrade policy, lock-in, and dependency graph health. Do NOT use for choosing a major framework (use `framework-fit-analysis`), vulnerability-only review (use `owasp-security`), or routine refactoring without dependency boundary changes (use `refactor`).
jacob-balslev/skills/skills/software-architecture/event-contract-design Skill
2★ repoUse when designing or reviewing asynchronous event contracts: producer/consumer ownership, event envelope, schema, topic/channel naming, ordering, idempotency, versioning, compatibility, replay, dead-letter behavior, and AsyncAPI/CloudEvents-style documentation. Do NOT use for domain-event discovery (use `event-storming`), broad interface contracts (use `system-interface-contracts`), inbound provider webhook mechanics (use `webhook-integration`), or HTTP endpoint design (use `api-design`).
jacob-balslev/skills/skills/software-architecture/system-interface-contracts Skill
2★ repoUse when defining or reviewing contracts between systems, modules, services, agents, jobs, events, APIs, or teams: ownership, inputs, outputs, invariants, compatibility, errors, idempotency, and versioning. Do NOT use for REST resource design alone (use `api-design`), async event contract detail (use `event-contract-design`), database schemas (use `entity-relationship-modeling`), or post-failure debugging (use `debugging`).
jacob-balslev/skills/skills/software-engineering-method/refactor Skill
2★ repoUse when reorganizing existing code without changing external behavior — extracting functions, reducing duplication, renaming for clarity, splitting modules, or tightening structure. Covers behavior preservation, duplication reduction, decomposition, naming improvements, structural reorganization, and before/after verification. Do NOT use for bug investigation, adding new product behavior, or writing documentation (even when the docs describe the refactored code).
wassengerhq/whatsapp-skills/skills/wassenger-setup Skill
2★ repoSet up Wassenger to automate WhatsApp Business with an AI agent. Use when the user is new to Wassenger, has not connected a number yet, needs an API key, or wants to install the Wassenger MCP server. Walks through API key creation, connecting a number on the official WhatsApp Business API (new or via Coexistence), MCP install, and a sanity test. Targets the official WABA only — the legacy QR-pairing path is not covered by this skills pack.
latent-variable/agentscope/skills/onboarding Skill
2★ repoFirst-run setup for agentscope. Interview the user, fill the AGENTS.md template + memory with their identity and preferences, detect which agent CLIs are installed, wire them all to ~/.agents, and tune optional features (ELI5 explanations, the Speak-to-me TTS block, the review-cycle workflow). Run this the first time someone clones agentscope, or when they say "onboard me" / "set up agentscope".
lhh1301506137/CoTend/skills/cotend-init Skill
2★ repoUse when the user wants one simple entry to initialize, update, repair, migrate, or resume the CoTend development framework for the current project, including migration from a legacy dual-ai project. Thin entry point that delegates to cotend-project-init Auto Mode and preserves pending-human-question boundaries before reporting whether it is safe to continue.
lhh1301506137/CoTend/skills/cotend-project-init Skill
2★ repoInitialize, update, repair, migrate, or resume a coding project workflow for the user's CoTend development framework, including migration from legacy dual-ai project truth. Auto-classifies fresh init, legacy update, partial repair, current resume, or blocked human decision; coordinates Codex primary + CodexSelf review, optional Claude review with advisor trigger map, Trellis active/dormant decisions, dev-high local fast mode, user interruption/new idea reconciliation, Plan Tree, user-readable expanded understanding, PROJECT-DECISION-LOG, PROJECT-KNOWLEDGE-CHANGELOG, progressive active-path loading, post-init consistency self-check, layered reports, high-level user confirmation gates, local closeout authorization, CodeGraph setup, vertical slices, Acceptance/Test Harness with Playwright/browser/Chrome routing, Done Gate with intent drift review, and Release Hardening.
yu-iskw/skill-inspector/.claude/skills/initialize-project Skill
2★ repoInitialize a new project from the TypeScript template by renaming packages, updating metadata, and cleaning up documentation. Use when starting a new project, "bootstrapping" from this template, or setting up a fresh repository.
The same file is in 1 other repository
yu-iskw/skill-inspector/.claude/skills/setup-dev-env Skill
2★ repoSet up the development environment for the project. Use when starting work on the project, when dependencies are out of sync, or to fix environment setup failures.
allanbian1017/skills/skills/personal/study-github-repo Skill
2★ repoAnalyze a GitHub repository and generate a comprehensive study report covering architecture, design decisions, code quality, and repo health. Use this skill whenever the user provides a GitHub repo URL and wants to understand it deeply, says 'study this repo', 'analyze this GitHub project', 'what does this repo do', 'how is this repo designed', or any request to understand a GitHub repository's architecture, codebase, or engineering quality. Also use when the user wants a repo breakdown, code review, or architecture analysis of a GitHub project.
allanbian1017/skills/skills/productivity/architecture-decision-records Skill
2★ repoWrite and maintain Architecture Decision Records (ADRs) following best practices for technical decision documentation. Use when documenting significant technical decisions, reviewing past architectural choices, or establishing decision processes.
The same file is in 5 other repositories