SkillFoxx

Agent Skills (AsyrafHussin)

Agent Skills

24 skills for Laravel, PHP, React and TypeScript: code rules, testing, security, technical debt and documentation.

  • 103 ★ on the repository
  • Last commit
  • MIT
Skill

Minimal access

Why this level

  • The set contains agent instructions and rules and runs no programs of its own.
All reasons and checks

asyrafhussin/agent-skillsAuthor:AsyrafHussin

Install

In your terminal, with SkillFoxx CLI

npx skillfoxx add skills/asyrafhussin-agent-skills

Detects the agents on your machine, shows the access level and pins the version.

Other ways to install

Access and checks

How we review

Minimal accessThe tool runs nothing and makes no network calls.

  • The set contains agent instructions and rules and runs no programs of its own.

This is third-party code. Review the repository files before installing.

What it does

The repository collects 24 skills following the Agent Skills specification. They cover Laravel 13 (architecture, queues, Pest and PHPUnit testing, database optimization, OWASP audit), modern PHP 8, React with Vite, TypeScript, Tailwind, TanStack Query and Zustand, REST API design, Git, SEO and accessibility. Each skill holds `SKILL.md`, `AGENTS.md`, a `rules/` folder and `metadata.json`. Some skills work as audits: `technical-debt` ranks debt on a P0-P3 scale, `code-slop` gives a diff a CLEAN, SUSPICIOUS, INFLATED or CRITICAL verdict, and `web-design-guidelines` returns a PASS and FAIL accessibility checklist.

Who it is for. Laravel, PHP, React and TypeScript developers who want ready-made rules and audits for Claude Code, Cursor and Codex.

Good fit when

  • Reviewing a Laravel controller against the rules and OWASP.
  • Before a refactor you need a ranked list of technical debt.
  • An AI-assisted pull request is checked for narrating comments, generic names and needless interfaces.
  • Feature tests are written in Pest and the agent needs hints on factories and facade fakes.

Not a fit when

  • Your stack is different, for example Django or Spring: the rules target PHP, Laravel and Node with TypeScript and React.
  • You need an automated linter: the skills steer the agent and do not replace PHPStan or ESLint.
  • You need one narrow skill: install it by name with the `--skill` flag, the whole set is unnecessary.

Example request

Audit the technical debt in this project and tell me what to refactor first.

Limitations

Rules are tied to versions: Laravel 13, Pest 4, PHPUnit 12, Tailwind 3.4 and 4, TanStack Query 5 and Zustand 5. They may age for other versions. `npx skills add` copies files into `.claude/skills/`, or into `~/.claude/skills/` with the `-g` flag. Tuning for other stacks is not provided. The skills describe practices and rules, while the agent runs checks with the project's own tools: tests, linters and build.

How to disable. Run `npx skills remove` and pick the skills, or delete their folders from `.claude/skills/` or `~/.claude/skills/`.

FAQ

How do I install a single skill instead of the whole set?

Add the `--skill` flag, for example `npx skills add AsyrafHussin/agent-skills --skill laravel-best-practices`. Repeat the flag for several skills.

How does technical-debt differ from code-slop?

`technical-debt` measures metrics (complexity, duplication, vulnerabilities, database indexes) and ranks the work. `code-slop` judges the taste of code in a diff: names, comments, needless abstractions. Run both for a full audit.

How do I list the skills without installing?

Run `npx skills add AsyrafHussin/agent-skills --list`.

Which agents does the set work with?

Claude Code, Cursor, Codex and more than 70 other agents from the vercel-labs/skills list. Pick an agent with the `-a` flag, for example `-a claude-code`.

What does each skill in the set contain?

A `SKILL.md` file, `AGENTS.md`, a `rules/` folder with individual rules and `metadata.json`. Skills group rules by category: `laravel-testing`, for example, has 24 in six categories.

Discussion

No questions or reviews yet.

Skills

15 skills for Claude Code and Codex: Laravel, Docker, UI, debugging, tests and docs in four ready plugin bundles

PluginExtended access69

A skill set against AI slop: UI and typography audits, change review, releases, docs and SEO.

SkillExtended access199

A vetted skill registry with a CLI that installs into twenty-plus agents and an MCP server for on-demand skill lookup

SkillExtended access7.2K

Brooklyn skills: 25 portable agent skills for pull requests, triage, cleanup, UI checks and research

SkillExtended access215

A skills library for Claude Code, Cursor and Codex: team code review, TDD, stacked PRs and repository readiness scoring

PluginExtended access72

A set of independent skills against drift in large codebases: hard-cut, root-cause tracing, lean testing and CI right-sizing.

SkillMinimal access140

README in short

The skills follow the Agent Skills specification and are listed on skills.sh. Install through `npx skills`, by copying folders by hand, or with `-g` for all projects. The README gives an example prompt for every skill.

README badge

Original SKILL.md

---
name: code-slop
description: Detect AI-generated code patterns ("slop") in PHP/Laravel and TypeScript/React source — comment narration, generic naming, premature interfaces, defensive overdose, mock-everything tests, and the absence of human "scars". Use when reviewing AI-assisted PRs, auditing code for taste/quality (not metrics — that's technical-debt), or hardening a code-review checklist. Triggers on "review for AI slop", "find AI patterns", "check code feels human", "audit code-quality taste".
license: MIT
metadata:
  author: agent-skills
  version: "1.0.0"
---

# Code Slop Detection

Taste-level review of code for AI-generated patterns. Contains 24 rules across 6 categories covering comments, naming, over-engineering, defensive overdose, test slop, and style fingerprints. Where [`technical-debt`](../technical-debt) measures *quantitative* code debt (complexity, duplication, CVEs), this skill measures the *qualitative* failure mode: code that passes every metric but reads like a tutorial blog post, not like a human wrote it.

## Metadata

- **Version:** 1.0.0
- **Scope:** PHP / Laravel + TypeScript / React (Node)
- **Rule Count:** 24 rules across 6 categories
- **License:** MIT

## Why this skill exists

Industry data on AI-assisted code (GitClear 2025, cURL bug-bounty shutdown 2025, arXiv 2510.03029):

- **Refactoring collapsed** from 25% to <10% of changes
- **Copy-paste surged** 8.3% → 12.3%; code duplication rose ~8x
- **Code-smell rates +42–85%** over human baselines
- **82% of AI PRs** use generic catch blocks that don't distinguish error types
- **76% miss timeouts** on external calls

None of this fails a typical CI lint. It just makes the codebase slowly unmaintainable. This skill is the lens for catching it before it ships.

The core insight: **reading cost > writing cost now**. The cost of writing code collapsed; the cost of reading it didn't. Code you can't quickly understand is slop, even if it works.

## How to Audit

When the user asks "review for AI slop", "audit code-quality taste", or "find AI patterns" — run through this skill's rules as a checklist against the changed files (PR diff) or full repo.

### Audit Step 1: Determine Scope

- If a PR diff is provided: audit only files changed in the diff
- If files are named: audit those
- If no scope: audit the whole repo, prioritized by recently-touched files (most likely AI output)

### Audit Step 2: Detect Stack

Report a problem