BytesAgain is a curated directory of 60,000+ AI agent skills from ClawHub, GitHub, LobeHub, and Dify. Search skills by keyword in 7 languages, browse by role (developer, creator, trader, marketer) or by use case.

How do I find AI skills on BytesAgain?

Use the search bar on BytesAgain.com to search by keyword in 7 languages. You can also browse by role (developer, creator, trader, marketer) or by use case. Each skill shows install instructions for Claude, Cursor, OpenClaw, Continue, and more.

Yes, BytesAgain is completely free. No registration required for searching skills. The MCP API is also free with rate limits.

Does BytesAgain have an API for AI agents?

Yes! BytesAgain provides a free MCP SSE endpoint at /api/mcp/sse for AI agents, plus a REST API at /api/mcp?action=search&q= . No authentication needed.

Can I request a new AI skill on BytesAgain?

Yes! Visit the Requests page on BytesAgain.com to submit a skill request. Your request will be visible to the community and notified to the site admin.

🦀 ClawHub✦ BytesAgain

Lint

by @xueyetianya

Check code syntax, enforce style, and suggest auto-fixes with CI integration. Use when linting PRs, enforcing code style, detecting errors before merge.

Versionv2.0.1

Downloads878

Installs3

#finance #legal

View on ClawHub →

TERMINAL

clawhub install lint

📖 About This Skill

name: lint version: "2.0.0" author: BytesAgain homepage: https://bytesagain.com source: https://github.com/bytesagain/ai-skills license: MIT-0 tags: [lint, tool, utility] description: "Check code syntax, enforce style, and suggest auto-fixes with CI integration. Use when linting PRs, enforcing code style, detecting errors before merge."

Lint

Lint is a developer-focused toolkit for recording and tracking code quality operations from the terminal. It provides 13 core action commands for managing checks, validations, formatting, linting, code generation, conversions, templates, diffs, previews, fixes, reports, and explanations — all with timestamped local logging for full traceability. Additional utility commands let you view statistics, export data, search history, and monitor health status.

Commands

Core Action Commands

Each action command works in two modes: run without arguments to view the 20 most recent entries, or pass input text to record a new timestamped entry.

| Command | Description | |---------|-------------| | lint check | Record a syntax/code check entry | | lint validate | Record a validation result | | lint generate | Record a code generation action | | lint format | Record a formatting operation | | lint lint | Record a linting pass | | lint explain | Record an explanation or annotation | | lint convert | Record a conversion operation | | lint template | Record a template action | | lint diff | Record a diff comparison | | lint preview | Record a preview action | | lint fix | Record an auto-fix action | | lint report | Record a report generation |

Utility Commands

| Command | Description | |---------|-------------| | lint stats | Show summary statistics — entry counts per category, total entries, data size, and earliest activity timestamp | | lint export | Export all data to JSON, CSV, or TXT format. Output file saved to ~/.local/share/lint/export. | | lint search | Full-text search across all log files (case-insensitive) | | lint recent | Show the 20 most recent entries from the history log | | lint status | Health check — version, data directory, total entries, disk usage, last activity | | lint help | Show help with all available commands | | lint version | Print version string (lint v2.0.0) |

Data Storage

All data is stored locally in ~/.local/share/lint/. Each action command writes to its own log file (e.g., check.log, validate.log, fix.log). A unified history.log records every action with timestamps. No external services, databases, or network connections are used.

Directory structure:

~/.local/share/lint/
├── check.log        # Check entries
├── validate.log     # Validation entries
├── generate.log     # Generation entries
├── format.log       # Formatting entries
├── lint.log         # Lint pass entries
├── explain.log      # Explanation entries
├── convert.log      # Conversion entries
├── template.log     # Template entries
├── diff.log         # Diff entries
├── preview.log      # Preview entries
├── fix.log          # Fix entries
├── report.log       # Report entries
├── history.log      # Unified activity log
└── export.*         # Export output files

Requirements

Bash (with set -euo pipefail)

Standard Unix utilities: date, wc, du, head, tail, grep, basename, cut

No external dependencies or API keys required

When to Use

1. Tracking linting sessions — Record which files you linted, what issues you found, and what fixes you applied, all with timestamps for audit trails. 2. Code review workflows — Log check and validate results during PR reviews so you can refer back to what was inspected and when. 3. Template and diff management — Keep a running record of template operations and diff comparisons across project iterations. 4. Exporting quality reports — Use lint export json to generate machine-readable reports of all recorded lint activity for CI dashboards or team reviews. 5. Searching past actions — Quickly find previous lint results, fixes, or explanations with lint search across all categories.

Examples

# Record a check on a Python file
lint check "src/main.py — 3 unused imports found"
Record a fix applied
lint fix "Removed unused imports in src/main.py"
View recent formatting actions
lint format
Search for all entries mentioning "import"
lint search import
Export everything to JSON
lint export json
View overall statistics
lint stats
Health check
lint status

⚡ When to Use

Trigger	Action
2. Code review workflows — Log check and validate results during PR reviews so you can refer back to what was inspected and when.
3. Template and diff management — Keep a running record of template operations and diff comparisons across project iterations.
4. Exporting quality reports — Use `lint export json` to generate machine-readable reports of all recorded lint activity for CI dashboards or team reviews.
5. Searching past actions — Quickly find previous lint results, fixes, or explanations with `lint search ` across all categories.

💡 Examples

# Record a check on a Python file
lint check "src/main.py — 3 unused imports found"
Record a fix applied
lint fix "Removed unused imports in src/main.py"
View recent formatting actions
lint format
Search for all entries mentioning "import"
lint search import
Export everything to JSON
lint export json
View overall statistics
lint stats
Health check
lint status

Trigger	Action
2. Code review workflows — Log check and validate results during PR reviews so you can refer back to what was inspected and when.
3. Template and diff management — Keep a running record of template operations and diff comparisons across project iterations.
4. Exporting quality reports — Use `lint export json` to generate machine-readable reports of all recorded lint activity for CI dashboards or team reviews.
5. Searching past actions — Quickly find previous lint results, fixes, or explanations with `lint search ` across all categories.