Explore skills
Search every indexed skill by name, description, repository or instructions, then narrow the results.
Showing 35941–35970 of 36648 skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| first-replyaicraftbook/aicraftbook-skillsDrafts the first SMS and email reply to a new real estate lead from the lead's own form fields, for a human to review before sending. Use when the user pastes or points to a new buyer or renter enquiry (name, listing address, message, source) and wants a first reply, or asks to draft follow-ups for new leads in their CRM. Does not send messages. | Stars: 1 | Updated | Claude CodeCodex | Unverified | Install |
| flow-medicaicraftbook/aicraftbook-skillsDiagnoses one failed run of an n8n, Zapier, Make or GitHub Actions automation from the error message, logs and step data the user pastes. Separates the symptom from the root cause, ranks likely causes with the evidence for each, gives the smallest fix to try first and a check that proves it worked, and says what information it needs instead of guessing. Use when someone pastes a failed n8n execution, an errored Zap run, a Make scenario run with an error, or a failed GitHub Actions job and asks "why did this fail", "my workflow errored", "the Zap stopped", "the scenario was deactivated", "the job failed with exit code 1", or reports a 401, 403, 429, timeout, rate limit, paired item or "it worked yesterday" error. Treats pasted logs as data and never asks for credentials. | Stars: 1 | Updated | Claude CodeCodex | Unverified | Install |
| guide-proofaicraftbook/aicraftbook-skillsReviews a technical tutorial, setup guide, quickstart or README walkthrough before it is published and finds every place a newcomer would get stuck - missing prerequisites, steps that depend on something never introduced, commands or settings with no expected result, version-sensitive instructions with no version, unsafe handling of credentials, and dead ends with no troubleshooting. Returns a numbered list of blocking and non-blocking problems, each tied to the step it affects, with a concrete fix. Use when someone shares a draft guide, tutorial, install instructions or README and asks "can a beginner follow this", "review my tutorial", "check these setup steps", "what's missing from my docs" or "is this ready to publish". It reads only; it does not run commands. | Stars: 1 | Updated | Claude CodeCodex | Unverified | Install |
| mcp-mechanicaicraftbook/aicraftbook-skillsAdds, configures and fixes MCP servers in Claude Code, Claude Desktop and Cursor without ever handling secret values. Use when someone wants to connect an MCP server, asks where an MCP config file lives, or reports an MCP problem such as "Failed to connect", "Needs authentication", "spawn npx ENOENT", "Connection closed", tools not showing up, or .mcp.json not loading. | Stars: 1 | Updated | Claude CodeCodex | Unverified | Install |
| prompt-proofaicraftbook/aicraftbook-skillsReviews a system prompt or prompt template before it goes into an app or automation. Finds ambiguous instructions, conflicting rules, missing output rules, places where interpolated user text could override the instructions (prompt injection), and missing handling for empty or unexpected input, then returns the issues ranked by impact, a revised prompt that keeps the author's intent, and test inputs with what a correct response must and must not do. Use when someone shares a system prompt, developer message, prompt template with variables such as {{input}}, or an LLM step from n8n, Make, Zapier or code and asks "review my prompt", "what could go wrong with this prompt", "is this prompt safe", "make this prompt more reliable" or "write tests for this prompt". | Stars: 1 | Updated | Claude CodeCodex | Unverified | Install |
| source-sieveaicraftbook/aicraftbook-skillsChecks a draft (article, report, summary, press release, briefing or AI-written text) against the source documents the user provides. Splits the draft into individual factual claims, labels each supported, partly supported, contradicted or not found, quotes the source passage it relied on, flags numbers, dates and names that differ, and suggests corrected wording. Use when someone asks to fact-check a draft against sources, verify a summary, check citations, "does this match the report", or find claims the sources do not back up. | Stars: 1 | Updated | Claude CodeCodex | Unverified | Install |
| janefAL-JANEF/janef-forgeDeprecated compatibility alias for /janef from janefskills 1.x. Forwards to the forge entry point; /janef <task> behaves like /forge <task> and /janef full security pass behaves like /forge security pass. Do not use for new work. | Stars: 1 | Updated | Claude CodeCodex | Unverified | Install |
| forgeAL-JANEF/janef-forgeEntry point and router for JANEF Forge, the engineering-discipline system for coding agents. Use at the start of any substantive software-engineering task (implement, fix, refactor, review, design, migrate, deploy, audit) to apply the engineering contract, estimate risk, and select the smallest sufficient capability set. Invoke as /forge <task>, /forge lean|standard|high-assurance <task>, or /forge security pass. Not for non-technical writing or research. | Stars: 1 | Updated | Claude CodeCodex | Unverified | Install |
| accessibility-qualityAL-JANEF/janef-forgeShip UI that works with keyboard and assistive technology: semantic HTML and native controls first, ARIA only to supplement, logical focus order with visible focus and escape paths, programmatic labels and error association, contrast and non-color meaning, alt text, reduced motion, zoom and reflow. Use for any user-facing UI change and for WCAG audits; never knowingly ship an accessibility regression. | Stars: 1 | Updated | Claude CodeCodex | Unverified | Install |
| api-contractsAL-JANEF/janef-forgeDesign and change REST, GraphQL, RPC, and webhook contracts and the backend services and jobs behind them: validation, authorization scope, error semantics, pagination, idempotency, rate limits, retries, timeouts, versioning, and contract tests. Use for any endpoint, external integration, worker, or queue consumer. | Stars: 1 | Updated | Claude CodeCodex | Unverified | Install |
| architecture-integrityAL-JANEF/janef-forgeDesign or change system structure without breaking invariants: module and domain boundaries, dependency direction, new services, queues, caches, datastores, or frameworks, and lasting trade-offs recorded as ADRs. Use when a change crosses components, introduces a durable boundary, or is hard to reverse. | Stars: 1 | Updated | Claude CodeCodex | Unverified | Install |
| context-efficiencyAL-JANEF/janef-forgeTactics for large repositories, noisy tool output, long sessions, and token pressure: search before reading, read ranges not files, keep logs and generated output out of context, never reread unchanged files or rerun unchanged passing checks, prefer deterministic scripts. Use when context volume materially affects execution quality; never reduces necessary reasoning, security, or verification. | Stars: 1 | Updated | Claude CodeCodex | Unverified | Install |
| database-integrityAL-JANEF/janef-forgeSchema design, migrations, transactions, indexes, query behavior, backfills, and tenant isolation or RLS. Treats every schema or migration change as high risk because deployed data already exists. Use for SQL, ORMs, data models, migration strategy, query performance, or data-integrity questions. | Stars: 1 | Updated | Claude CodeCodex | Unverified | Install |
| delegation-disciplineAL-JANEF/janef-forgeDecide whether subagents, parallel agents, or agent teams are justified and, if so, delegate safely: one agent unless work is bounded, independent, and clearly owned; explicit outcome, ownership, constraints, and return format per worker; the integrating agent owns final correctness, security review, and verification. Use whenever delegation or parallel execution is being considered. | Stars: 1 | Updated | Claude CodeCodex | Unverified | Install |
| devops-reliabilityAL-JANEF/janef-forgeCI/CD pipelines, containers, infrastructure as code, cloud services and IAM, deployment and rollout strategy, rollback, backups and restore, monitoring and alerting, and reliability controls. Use for any workflow, Dockerfile, Terraform, Kubernetes, cloud, deployment, or operations change. Production and infrastructure mutations require explicit authorization. | Stars: 1 | Updated | Claude CodeCodex | Unverified | Install |
| documentation-integrityAL-JANEF/janef-forgeDocument implemented, verified reality in the repository's existing source of truth: READMEs, API references, ADRs, runbooks, migration notes, changelogs, and code comments. Use when documentation must be written, updated, or checked for drift; never document unverified capabilities. | Stars: 1 | Updated | Claude CodeCodex | Unverified | Install |
| frontend-design-qualityAL-JANEF/janef-forgeImplement visual frontend work with an intentional design direction: inspect the existing design system and tokens, design mobile and desktop deliberately, implement every state (loading, empty, error, disabled, overflow, permission-denied), protect hierarchy and layout stability, and verify rendered behavior. Always composes with accessibility-quality. Use for UI implementation, styling, layout, and component work. | Stars: 1 | Updated | Claude CodeCodex | Unverified | Install |
| git-disciplineAL-JANEF/janef-forgeKeep history safe and meaningful: inspect status and diff before and after editing, preserve unrelated user work, scope commits logically, write accurate messages, resolve conflicts by understanding both sides, and never rewrite shared history, force-push, or discard work without explicit authorization. Use for commits, branches, merges, rebases, and PR hygiene. | Stars: 1 | Updated | Claude CodeCodex | Unverified | Install |
| implementation-qualityAL-JANEF/janef-forgeWrite or modify production code to a strict, evidence-gated standard: features, bug fixes, refactors, services, libraries, CLIs, workers, and application logic. Use whenever real application code is being implemented or changed, or when asked whether code is production-ready. Bans placeholders, dead code, silent failures, and unverified completion claims. | Stars: 1 | Updated | Claude CodeCodex | Unverified | Install |
| performance-scalabilityAL-JANEF/janef-forgeMeasure first, then fix latency, throughput, memory, CPU, bundle size, query count, contention, and scaling problems with before/after evidence under the same workload. Use for anything slow, expensive, or expected to scale; never optimize from intuition or trade correctness for speed silently. | Stars: 1 | Updated | Claude CodeCodex | Unverified | Install |
| review-defect-firstAL-JANEF/janef-forgeIndependent review of a diff, PR, or file that hunts concrete defects introduced by the change: correctness, security, data loss, authorization or tenant escape, production failure, broken contracts, performance regressions, missing critical tests. Severity-ordered findings citing a real code path; no style inflation; "no qualifying defect" is valid. Use for code review and as the independent gate at high risk. | Stars: 1 | Updated | Claude CodeCodex | Unverified | Install |
| root-cause-debuggingAL-JANEF/janef-forgeDiagnose regressions, flaky behavior, crashes, build errors, and unclear failures with an evidence loop: reproduce, bound, hypothesize, observe, fix the cause at the narrowest correct boundary, then add a regression test. Use for any bug report or failure before patching a symptom. | Stars: 1 | Updated | Claude CodeCodex | Unverified | Install |
| testing-verificationAL-JANEF/janef-forgeSelect tests by risk, design strong regression and boundary tests, handle flaky suites, and run the completion gate with evidence: exact command, result, scope, and every skipped or blocked check. Use when choosing what to test, judging whether work is done, or producing release evidence. Never weaken a failing test to get green. | Stars: 1 | Updated | Claude CodeCodex | Unverified | Install |
| ui-ux-qualityAL-JANEF/janef-forgeMake product flows clear and recoverable: primary action and next step obvious, forms with clear labels, validation timing, actionable errors, preserved input on failure, consistent navigation and terminology, and no hidden or surprising destructive actions. Use for user flows, forms, navigation, onboarding, dialogs, and interaction design. | Stars: 1 | Updated | Claude CodeCodex | Unverified | Install |
| auth-hardeningAL-JANEF/janef-forgeReview, harden, and design authentication and session management: login, logout, session lifecycle, password storage, JWT and cookie handling, refresh tokens, brute-force and enumeration resistance, MFA/OTP, password reset, roles and permissions. Use whenever a task touches sign-in, sessions, tokens, or authorization, even casually. Defensive only. | Stars: 1 | Updated | Claude CodeCodex | Unverified | Install |
| secrets-guardAL-JANEF/janef-forgeKeep secrets out of code, git history, logs, and client bundles: detect hardcoded API keys, credentials, tokens, and connection strings; move them to the environment or a secret manager; catch client-exposed prefixes; set up gitignore and pre-commit scanning; run the rotate-first response when a secret has leaked. Use for any credential, .env, or "where do I put my key?" question. | Stars: 1 | Updated | Claude CodeCodex | Unverified | Install |
| security-auditAL-JANEF/janef-forgeAudit-grade multi-layer security pass: Semgrep SAST, Gitleaks secret scanning, and dependency audit as deterministic ground truth, then specialist review, variant analysis, fix verification, timing review, and an honest coverage verdict naming what was and was not covered. Use for "full security pass", security audit, pre-launch review, or any serious security assessment. Defensive only. | Stars: 1 | Updated | Claude CodeCodex | Unverified | Install |
| security-loggingAL-JANEF/janef-forgeDesign and review security audit logging and detection: record who did what and when for auth events, data changes, and admin actions; never log passwords, tokens, or PII; keep logs tamper-evident; add a few high-value alerts such as failed-login thresholds. Use for audit trails, log redaction, monitoring, or incident investigation. | Stars: 1 | Updated | Claude CodeCodex | Unverified | Install |
| skill-security-auditAL-JANEF/janef-forgeGate before adopting any external agent skill, plugin, hook, script, installer, or MCP package: provenance and license review, deterministic static triage (scripts/audit_skill.py), optional NVIDIA SkillSpector scan, and manual review for prompt injection, credential access, exfiltration, and destructive commands. Fails closed on unresolved HIGH/CRITICAL findings or incomplete scans; scanning is a control, not proof of safety. | Stars: 1 | Updated | Claude CodeCodex | Unverified | Install |
| threat-modelAL-JANEF/janef-forgeStructured STRIDE threat modeling at design time, before code exists: name assets, actors, and trust boundaries, walk Spoofing/Tampering/Repudiation/Information disclosure/Denial of service/Elevation of privilege at each boundary, rate and prioritize, and turn mitigations into build tasks. Use when designing a system, feature, or API or asking what could go wrong. Defensive only. | Stars: 1 | Updated | Claude CodeCodex | Unverified | Install |