This repository is a curated resource hub (awesome list) for Claude Code skills, targeting Chinese-speaking developers. It contains 20 original SKILL.md files that can be directly installed into Claude Code, plus a curated directory of 441+ third-party skills organized by categories such as development efficiency, content creation, platform operations, and more. The repo includes a static website (docs/index.html) that mirrors the README, automated Python/Node.js scripts for synchronization, and rigorous CI/CD pipelines with pinned dependencies and comprehensive tests. It is not a running application but a content curation project with high-quality infrastructure for maintaining consistency between the README and the website, including atomic file writes and strict anchor validation. The original skills are well-structured and cover practical scenarios like code review, documentation generation, API testing, and refactoring, all in Chinese.
This is not a conventional software application — it is a curated awesome-list repository (classified as 'application' only because its CI/CD pipeline and shell tooling are the sole executable content). The actual product is README.md: a comprehensive, categorized catalog of Android security resources covering online analyzers, static/dynamic analysis tools, reverse-engineering utilities, fuzzers, vulnerability scanners, intentionally vulnerable practice apps, research papers, malware datasets, exploit lists, and bug bounty programs. The repository ships no libraries, services, or user-facing code; its runtime behavior is limited to link-liveness checking (urlsup) and linting of the repository's own documentation and automation. The repository's engineering value lives in its maintenance infrastructure. GitHub Actions workflows lint Markdown (mdl), shell scripts (shellcheck), YAML (yamllint), and the workflows themselves (actionlint plus a zizmor security scan), while a scheduled job validates all README links weekly using a carefully curated urlsup configuration (.urlsup.toml) that distinguishes dead links (strikethrough-removed from the list) from flaky or bot-protected endpoints (allowed 403/429/503). Dead and archived tools are explicitly marked with strikethrough in the README, keeping the resource list honest without silently deleting historical references. All third-party actions are pinned to commit SHAs, permissions are least-privilege, and the cargo-based link checker is cached for fast CI runs. For an Android security practitioner, the repo serves as the de facto reference index for the ecosystem — many entries point to the actual tools (MobSF, Drozer, Frida, jadx, Androguard, QARK) and malware datasets (AndroZoo, Drebin, Kharon). For an engineer, the reusable assets are the link-liveness pipeline and the CI self-audit pattern, both of which can be transplanted into any link-heavy or automation-heavy repository. The repo is a hybrid: content-curation project with application-grade CI scaffolding around it, rather than either a true application or a data research project.
This repository is a curated, interactive learning roadmap for building AI agents. It is not a software library or framework, but a single-page web application (index.html) that renders a comprehensive todo list, project ladder, and curated resource collection. The application allows users to track progress via checkboxes stored in localStorage, take Markdown notes per stage, search content, toggle dark mode, and navigate via a sidebar. The underlying data is a static JSON structure embedded in the JavaScript. The repo's primary value is its meticulously organized learning path covering agent loops, tool use, RAG, multi-agent coordination, skills/protocols, browser agents, evaluation, and production deployment. It references dozens of high-quality external resources (official docs, papers, open-source projects) and provides clear learning principles. While the repo contains no runnable agent code, the interactive frontend is a well-crafted tool for self-paced learning. The codebase is a hybrid: it is an application (web UI) but its content is a curated research/learning resource.
This repository is a comprehensive, curated list of anomaly detection (outlier detection) resources, maintained by the author of the PyOD library. It aggregates books, academic papers, tutorials, open-source toolkits, datasets, and relevant conferences/journals, covering tabular, time-series, graph, and text data modalities. The repository also includes two utility scripts: a downloader for paper PDFs and a robust URL checker for verifying links in the documentation. While the core value is the curated resource list itself, the utility scripts demonstrate clean engineering practices and are reusable for similar link-checking and batch download tasks. This is not a software application or data pipeline; it is a reference catalog for researchers and practitioners.
This repository is a curated 'awesome list' for ESLint, not a software application or data pipeline. Its core is a single, extensively organized README.md that catalogs ESLint configurations, plugins, parsers, formatters, globals, tools, tutorials, and setup resources. The only functional code is a package.json declaring the `awesome-lint` dev dependency and a GitHub Actions workflow that runs this linter against the README on every push and pull request to ensure list quality and formatting consistency. The architecture is intentionally static—no runtime services, APIs, or data processing exist. The repo's production value is purely informational: it serves as the de facto community reference for discovering and choosing ESLint-related tooling. It is actively maintained with recent commits, high visibility, and a clear contribution guide. Technical drift is limited to outdated CI details (e.g., actions/checkout@v3) and a broad dev-dependency range, but the content itself stays current with the ESLint ecosystem. While not a codebase in the traditional sense, the curation quality, categorization, and maintenance discipline are strong, making it a reliable resource for developers evaluating ESLint tools.
This repository is a curated list of Bash scripts, tools, and resources, following the 'awesome' list format. It contains no application code or data pipelines; the primary content is a README.md that organizes hundreds of external links into categories such as Command-Line Productivity, Customization, Shell Script Development, and Games. The only source file is a trivial hello.sh script that echoes 'hello', which serves no functional purpose. The repository is essentially a documentation and curation project, maintained by the awesome-lists community. It is actively maintained with recent commits and a clear contribution guideline. The value lies in its curated selection of high-quality Bash resources, not in any code implementation. As such, it is not a software application in the traditional sense, but rather a reference index for developers seeking Bash-related tools and learning materials.
This repository is a curated 'awesome list' for Game Boy and Game Boy Color development — a community-maintained directory of resources rather than a software application. Its production function is curation: organizing and continuously validating links to documentation (Pan Docs, opcode references, hardware schematics), emulators (SameBoy, mGBA, BGB), development toolchains (RGBDS, GBDK), homebrew games, and reverse-engineering projects. The main README.md is meticulously organized into roughly 15 categories, with EMULATORS.md and MORE.md serving as supplementary lists for open-source emulators and lower-tier resources respectively. The contribution guidelines (CONTRIBUTING.md) define a clear triage process between the main list and MORE.md, establishing quality gates for what qualifies as 'awesome'. The only executable code is the GitHub Actions CI workflow (.github/workflows/ci.yml), which runs two validation jobs: awesome-lint (installed from a custom fork, gbdev/list-linter) to enforce markdown formatting standards, and brok (a dead-link checker) to detect broken URLs across all markdown files. The workflow runs on push, pull request, a weekly schedule, and manual dispatch, and it deliberately ignores tcrf.net due to that site's DDoS protection — a thoughtful, reusable pattern for any awesome-list maintainer. The repository also ships CartridgeList.csv, a structured dataset cataloging thousands of Game Boy cartridge dumps with columns for mapper type (MBC1/MBC3/MBC5/RUMBLE/CAMERA/etc.), ROM size, RAM size, battery presence, RTC presence, and game title — a valuable reference for emulator developers, cartridge hardware projects, and ROM preservation efforts. Maintenance is active: the last commit is recent, the CI pipeline runs on a weekly schedule, and the community is engaged (4,497 stars, 21 open issues, active Discord). The repo is the de facto canonical starting point for Game Boy development. While it contains no application code in the traditional sense, its curation quality, CI infrastructure, and reference data make it a high-value, well-maintained resource.
This repository is a curated list of awesome Jupyter projects, libraries, and resources. It serves as a reference for developers and data scientists seeking tools to enhance their Jupyter experience, including runtimes, visualization libraries, collaboration tools, and more. The list is organized into thematic categories (e.g., Runtimes/Frontends, Collaboration/Education, Visualization) for easy navigation and discovery. The repository includes maintenance workflows to ensure the quality and consistency of the list. A GitHub Actions workflow runs awesome-lint and remark-lint to validate the format of the list and keep it alphabetized. Another workflow tracks GitHub traffic statistics. The project follows standard contribution guidelines and is licensed under Creative Commons Attribution-ShareAlike 4.0. While the repository itself does not contain executable code or data, it provides significant value as a discovery tool for the Jupyter ecosystem. The maintained workflows demonstrate good practices for keeping awesome lists clean and consistent, which can be reused in similar projects. The content is regularly updated, as evidenced by recent commits, indicating active maintenance.
This is an 'awesome list' curation repository — the definitive index of the LangGraph/LangChain ecosystem — rather than a conventional software application. The core product is a ~30k-line README.md that maps the ecosystem into core frameworks (LangChain, LangGraph, Deep Agents, LangSmith, LangSmith Fleet, and integrations), official LangChain projects, and ~100 community projects organized across 20+ use-case categories (RAG, finance, web automation, coding agents, research, cybersecurity, workplace productivity, media, robotics, and more), plus learning resources, templates, case studies, and communities. Its practical function is as a discovery and evaluation map for engineers building stateful, tool-using AI agents: everything is categorized, linked, badged, and maintained under defined contribution quality gates. The only real code is scripts/repo-checks.mjs, a maintenance automation script that parses every GitHub URL from the README, queries the GitHub API for each repo's metadata, classifies repos as archived or stale (15-month staleness cutoff for community projects), writes a markdown check report, and fails CI when problems are found. This is orchestrated by three GitHub Actions workflows: awesome-lint/markdownlint on PRs, a monthly scheduled repo-health cron, and a stale-issue/PR bot. The package.json exposes npm scripts for these checks with Node >=20 as the engine. The repository is actively maintained (latest commit 2026-07-10), uses current GitHub Actions major versions (v6 checkout/setup-node, stale@v9), and follows a documented contribution process with a PR template enforcing category placement, alphabetical order, and non-archived/active-project requirements. For AI agents and engineers, the value is twofold: (1) it is a currently-maintained, comprehensively categorized starting point for discovering LangGraph/LangChain projects and patterns by domain — useful before writing any code; (2) the repo-checks script is a genuinely extractable pattern for anyone maintaining any markdown document containing GitHub links, since it is a self-contained, env-configurable health checker that requires minimal adaptation. It is as close to a 'productized' awesome list as exists in this space, with CI, lint enforcement, and automated freshness audits. Limitations: no unit tests for the maintenance script (its errors surface only monthly via cron), descriptions for some official projects are generic and low-signal, and there is no actual application or library code to reuse beyond the single maintenance script.
This repository is a curated, community-maintained 'awesome list' for the Blazor framework (a Microsoft .NET web UI framework). It aggregates and categorizes hundreds of external resources including sample projects, tutorials, libraries, videos, articles, podcasts, tooling, books, and community links. The main entry point is the README.md, which provides a structured table of contents with shields.io badges (GitHub stars, last commit, license) for each listed resource. The repository also contains yearly archives (2017–2024) tracking historical resources, a Component-Bundle-Comparison.md that compares 16+ Blazor UI component libraries, and a CONTRIBUTING.md with contribution guidelines. The repository itself contains no executable application code or data pipelines; it is purely a documentation/curation project that serves as a discovery and reference hub for the Blazor ecosystem. The curation methodology follows a consistent pattern of categorization, metadata badges, and archival, making it a reusable template for other awesome lists. The repository is actively maintained with recent commits referencing .NET 11 previews in 2026, though the sheer volume of external links introduces inherent risk of link rot and staleness for less popular entries.
This repository is a curated collection of JavaScript libraries, resources, and tools - an 'awesome list' rather than executable code. The README.md contains categorized links to 300+ JavaScript packages across domains including frameworks, utilities, testing, data visualization, and more. The only actual code is a GitHub Actions workflow that validates links using awesome_bot. The repository's value lies entirely in its curation quality and organization, not in reusable code components. The validator workflow ensures link integrity but the list itself requires manual maintenance to stay current with the rapidly evolving JavaScript ecosystem.
This repository is not a software application, service, or data pipeline. It is an "awesome list": a manually curated Markdown directory of WebGPU resources. The only substantive content is readme.md, which organizes links into roughly a dozen categories: official specifications, browser support details, articles, tutorials, books, libraries, debuggers/profilers, gists, demos, videos, presentations, community channels, and bug-reporting trackers. It includes enablement instructions for Chrome, Firefox, Safari, and iOS/iPadOS, and points to both the W3C WebGPU/WGSL specifications and the MDN API reference. The repository is maintained as a community resource: it is CC0-licensed, has contribution guidelines and a code of conduct, and receives regular commits. Its value is informational rather than executable—there are no build scripts, package manifests, tests, entry points, or runtime dependencies. It is best used as a discovery reference for engineers evaluating WebGPU libraries, WGSL tooling, rendering engines, or GPU compute examples. The list also internally flags stale debugger projects, demonstrating careful curation. Because this repo contains no source code, there are no reusable software components, libraries, or data assets to extract. Its quality should be evaluated as documentation and curation, not as software engineering.
This repository is a curated 'awesome list' of threat detection and hunting resources. It does not contain any executable code, application logic, or data pipelines. The content is purely a markdown document (README.md) and its HTML equivalent, along with a small number of PDF guides. The repository functions as an index of links to external tools (e.g., osquery, Sigma, HELK), datasets (e.g., Mordor, BOTS), frameworks (MITRE ATT&CK), blogs, videos, and training resources. It is a static, non-functional reference directory. While it serves as a valuable starting point for security professionals, it has no software architecture, no entry points, no data flows, and no reusable code components. Its value lies in curation and organization rather than engineering.
This repository is a curated awesome-list of research papers, projects, datasets, and industry demos related to digital humans: 3D avatar generation and animation, clothed human reconstruction, head avatars, human motion generation, virtual try-on, cloth simulation, and related topics. It contains only a README.md plus LICENSE; there is no application code, no executable pipeline, no tests, no CI, and no dependency manifests. Despite the data_research classification, it is best understood as a manually maintained literature index rather than a data pipeline or software project.
Awesome Video is a curated resource catalog for streaming video technologies, maintained as structured JSON (contents.json) and rendered into both a README and a static documentation site (MkDocs Material) deployed to awesome.video. The catalog spans ~50 hierarchical categories covering HLS, DASH, FFmpeg, codecs (HEVC/VP9/AV1), transport protocols (RIST/SRT/RTMP), players, DRM, QoE, testing, CDN, HDR, subtitles, and learning resources. It is not a runtime application — it is a content curation pipeline: contents.json is the source of truth, convert.rb generates the README, database.json feeds the site's lunr search index, and loader.py imports bookmarks from Raindrop.io. The repo is hybrid in nature: primarily a curated data catalog with a static-site build system around it, rather than a software application or research pipeline. The build pipeline (GitHub Actions) validates the JSON against schema.json, checks external links with awesome_bot, and deploys to GitHub Pages. The curation quality is strong — entries include authoritative references (Netflix TechBlog, DASH-IF specs, Apple WWDC sessions, Xiph test media) — but the supporting code is simple utility scripting with notable weaknesses: hardcoded Raindrop.io credentials in loader.py, inconsistent category identifiers and malformed tag entries in the data, and aging CI dependencies (Python 3.7, jinja2 3.0.3). The repo is actively maintained and the data model (hierarchical categories + multi-tagged project records) is a clean, portable schema for any awesome-list-style content site.
This is an awesome list (curated directory) for the Preact ecosystem. It contains links to community resources, toolkits, boilerplates, routing libraries, components, libraries, testing utilities, articles, example apps, and related libraries. The repository itself contains no application code or data pipelines; it is purely a documentation and curation project. The list is well-organized and follows standard awesome-list conventions. As there is no executable code, the typical architectural and reusability analysis does not apply.
EmbedBooks is a Chinese-language, static GitHub repository whose only substantive content is README.md: a hand-maintained, categorized index of embedded-systems and computer-science textbooks, mostly PDFs hosted on Baidu Pan. It organizes 80+ titles into categories such as electronics, C, data structures, OS, ARM/RISC-V, Linux, networking, testing, design patterns, and career material. Every entry consists of a book title, an external Baidu cloud link, and an extraction code. There is no application code, no build system, no CI, no tests, and no executable logic.
This repository is a curated 'awesome' list of biomechanical resources. It contains no executable code, notebooks, or data pipelines. The entire content is a single README.md file with hundreds of categorized links to learning materials, datasets, software tools, books, societies, and other resources relevant to biomechanics research and education. It functions as a community-maintained directory rather than a software project or research pipeline. While the list is well-organized and frequently updated, there are no computational components to analyze or reuse.
This repository is a curated 'awesome list' of Android security resources. It contains a single README.md file that organizes links to blogs, tools (static/dynamic analysis, online analyzers, decompilers, forensics), papers, books, training materials, labs, talks, bug bounty writeups, cheat sheets, and checklists. No executable code, APIs, or data pipelines are present. The repo functions solely as a reference index for Android security practitioners and researchers. It has no software architecture, no entry points, and no data flows. The only file beyond README is the MIT license.