Explore skills
Search every indexed skill by name, description, repository or instructions, then narrow the results.
Showing 40831–40860 of 43571 skills
| Skill | Stars | Updated | Works with | Status | 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 |
| variant-huntAL-JANEF/janef-forgeAfter any vulnerability or bug is confirmed, sweep the entire codebase for every other instance of the same pattern with ripgrep and custom Semgrep rules so the whole class is fixed, not one case. Use right after finding or fixing a security issue, when checking a fix is complete, or to prove a past pattern is eradicated. Defensive only. | Stars: 1 | Updated | Claude CodeCodex | Unverified | Install |
| vuln-auditAL-JANEF/janef-forgeAudit application code for the OWASP Top 10 classes: injection (SQL/NoSQL/command), XSS, CSRF, SSRF, IDOR and broken access control, insecure deserialization, unsafe file upload, and misconfiguration. Use for any security review, "is this safe?", or code that handles untrusted input, queries, uploads, outbound URLs, or objects by ID. Produces a severity-ranked report with concrete fixes and proof. Defensive only. | Stars: 1 | Updated | Claude CodeCodex | Unverified | Install |
| risky-skillAL-JANEF/janef-forgeA fixture skill that contains patterns the static auditor must flag. | Stars: 1 | Updated | Claude CodeCodex | Unverified | Install |
| safe-skillAL-JANEF/janef-forgeA harmless fixture skill that only describes a code-review checklist for tests. | Stars: 1 | Updated | Claude CodeCodex | Unverified | Install |
| aeronautical-engineeringGriffing-Technology-LLC/engineering-pe-skillsAeronautical and aerospace engineering analysis with authoritative citations — airfoil and wing aerodynamics, lift/drag/moment build-up, propeller and EDF thrust, weight and balance, CG and static margin, V-n envelopes, and airframe load factors. Use when sizing a wing, computing lift or drag, analysing an airfoil or aerofoil section, checking CG or static margin, building a V-n diagram, sizing a propeller or ducted fan, doing a weight-and-balance or mass-properties roll-up, or evaluating a UAS or light aircraft airframe against FAA Part 23/107, NASA, or ASTM F38 standards. | Stars: 1 | Updated | Claude CodeCodex | Unverified | Install |
| computer-engineeringGriffing-Technology-LLC/engineering-pe-skillsComputer engineering aligned to the NCEES PE Electrical and Computer (Computer Engineering) exam — number and data representation, error detection and correction, processor and memory architecture, embedded systems and microcontroller interfacing, real-time scheduling and interrupts, firmware and boot, digital logic and timing analysis, ADC/DAC and signalling standards, computer networks, system cybersecurity, and software verification and validation. Use when choosing a number format or checking overflow, sizing a CRC or ECC scheme, estimating CPI/speed-up or cache performance, checking real-time schedulability or interrupt latency, designing or timing a synchronous digital circuit, resolving metastability or clock-domain crossing, selecting a bus or signalling standard (CAN, LVDS, Ethernet), specifying a secure boot or firmware-update chain, laying out a network or threat model for an embedded product, or building a V&V/test plan for safety-critical software. | Stars: 1 | Updated | Claude CodeCodex | Unverified | Install |
| control-systems-engineeringGriffing-Technology-LLC/engineering-pe-skillsControl systems engineering aligned to the NCEES PE Control Systems exam — PID tuning, loop dynamics, transfer functions, stability and frequency response, process instrumentation and P&IDs, final control elements, safety instrumented systems and SIL, and industrial control security. Use when tuning or diagnosing a control loop, building a transfer function or block diagram, checking stability or phase and gain margin, sizing a control valve or selecting a sensor, reading or drafting a P&ID, doing a SIL or LOPA assessment, or designing a feedback controller for a physical plant. | Stars: 1 | Updated | Claude CodeCodex | Unverified | Install |
| electrical-engineeringGriffing-Technology-LLC/engineering-pe-skillsElectrical power engineering aligned to the NCEES PE Electrical and Computer (Power) exam — per-unit and three-phase power system analysis, transformers, short-circuit and fault current calculation, overcurrent protection and coordination, grounding and bonding, and arc-flash hazard assessment. Use when computing per-unit or three-phase power quantities, sizing or checking a transformer, running a short-circuit or fault study, selecting or coordinating overcurrent protection, checking a grounding/bonding scheme, or estimating an arc-flash incident-energy or boundary requirement. | Stars: 1 | Updated | Claude CodeCodex | Unverified | Install |
| electronics-engineeringGriffing-Technology-LLC/engineering-pe-skillsElectronics engineering aligned to the NCEES PE Electrical and Computer — Electronics, Controls, and Communications module — signal integrity and transmission-line analysis, EMC/EMI emissions and immunity, analog and digital circuit design, ADC/DAC and data-conversion basics, and board-level power regulation. Use when analyzing transmission-line reflections or termination, estimating crosstalk or an eye diagram, assessing EMC emissions/immunity or FCC Part 15 applicability, designing or reviewing an analog or digital circuit (amplifiers, filters, logic families), selecting an ADC/DAC, or sizing board-level power regulation. Not for power-system, protection, or arc-flash work — see `electrical-engineering` for that. | Stars: 1 | Updated | Claude CodeCodex | Unverified | Install |