This repository is a comprehensive family of GUI automation agents (Mobile-Agent series) developed by Tongyi Lab, Alibaba Group. It provides end-to-end solutions for automating interactions across mobile (Android), desktop (Windows/macOS/Linux), and web platforms using vision-language models. The system perceives GUI elements through screenshots, grounds natural language instructions to actionable commands (click, type, scroll), and executes tasks via platform-specific controllers. The architecture includes multiple agent versions (v1-v3.5, E, UI-S1, PC-Agent) with shared core modules for perception, action parsing, and controller interfaces, alongside training frameworks (VERL) and evaluation suites (Android World, MiniWoB, Mind2Web). Key entry points are version-specific run scripts (e.g., run_ma35.py) and API services for remote agent control. The system relies on external dependencies like ADB for Android, PyAutoGUI for desktop, Playwright for web, and VLMs (Qwen series) for reasoning.
This is a Model Context Protocol (MCP) server that enables AI agents to interact with the Godot game engine. It provides tools to launch the Godot editor, run projects in debug mode, capture console output, manage scenes, add nodes, load sprites, export mesh libraries, and handle UID references for Godot 4.4+. The server is a single TypeScript process that communicates via stdio, spawning Godot processes for complex operations and using a bundled GDScript for scene manipulation. It includes path traversal protection, class name validation to prevent arbitrary script instantiation, and flexible parameter naming (supports both camelCase and snake_case). The project is well-structured, with clear error handling and debug logging, making it suitable for integration with AI coding assistants like Claude, Cline, and Cursor.
Maid is a Ruby command-line tool and library that automates file organization and cleanup based on user-defined rules expressed in a Ruby DSL. It provides a suite of operations (move, trash, copy, rename, etc.) that can be combined with file metadata predicates (age, size, content type, download source, etc.) to systematically manage filesystems. The architecture is a traditional Ruby gem with a Thor-based CLI (bin/maid), a central Maid::Maid class that orchestrates rule loading and execution, and a set of tool methods mixed into the Maid instance for use in rule blocks. It also supports daemon mode using Listen (file system watcher) and rufus-scheduler (timed repeats). The code is well-structured with modular components, extensive test coverage, and modern Ruby practices, though it carries some legacy from supporting older Ruby versions. There is no data research or analytic component; it is purely an application for file automation.
The CAE Agent Hub repository provides a collection of MCP servers, reusable agent skills, solver automation workflows, and browser-based result viewers for engineering simulation. It includes various applications and modules for interacting with different CAE tools and solvers, such as Ansys, Fluent, and Mechanical. The repository follows a specific structure and pattern, and contains various data and research-related assets.
The ReVanced Documentation repository serves as a central hub for documentation related to the ReVanced suite of tools (Manager, CLI, and Patcher). It does not contain application code but instead aggregates Markdown documentation and uses Git submodules to link to the respective tool repositories. The repository features a GitHub Actions workflow that automates the process of updating these submodules and committing the changes, ensuring the documentation stays in sync with the source code. Architecturally, the repository is straightforward: it consists of documentation files organized by topic, configuration files for submodules, and a workflow for maintenance. The key entry point is the GitHub Actions workflow triggered by repository_dispatch events, which updates a specified submodule and records the change. This design allows for efficient maintenance of the documentation without manual intervention. While the repository lacks complex application logic, it demonstrates good practices in documentation management and automation. The update workflow is a reusable component that could be adapted to other projects using submodules. The documentation itself is well-organized and accessible, providing users with clear guidance on using and contributing to the ReVanced ecosystem.
This repository is a curated collection of Claude skills—markdown instructions and supporting scripts that enable Claude (or any MCP-compatible agent) to perform a wide range of tasks, from document manipulation (DOCX, PPTX, PDF, XLSX) and GIF animation to web testing, MCP server building, and automation of hundreds of third-party SaaS services via Composio's Rube MCP. The repo is primarily a skill library with a standardized template for each skill, but it also contains several well-crafted Python libraries (e.g., easing functions, particle systems, OOXML validation frameworks) that are genuinely reusable. The architecture is modular: each skill lives in its own directory with a SKILL.md and optional scripts. The heavy reliance on external services (Composio, Rube MCP) and the massive duplication of templated skill documentation introduce maintenance risks, but the core utility scripts demonstrate solid engineering craftsmanship.
coca is a static code analysis and refactoring CLI tool written in Go, designed to assess code quality, detect bad smells, analyze dependencies, and support migration tasks (specifically Spring MVC to Spring Boot). It operates as a monolithic command-line application using the Clean Architecture pattern, with distinct layers for domain models, application logic, and infrastructure. The tool supports multiple languages including Java, Go, Python, JavaScript, TypeScript, and Groovy, leveraging ANTLR for parsing and generating ASTs for analysis. The system's primary function is to scan codebases for technical debt, architectural issues, and API definitions, outputting results in various formats (JSON, CSV, Graphviz). It includes features for bad smell detection (e.g., Long Method, Large Class), test smell analysis, and dependency usage evaluation. The architecture is modular, allowing individual analysis features to be executed independently, though the tool itself is a single binary. While the codebase demonstrates solid engineering practices with a clean separation of concerns and reusable domain models, it exhibits technical drift in its dependency ecosystem. The Go version specified (1.23) is ahead of current stable releases, and several core dependencies (e.g., spf13/cobra, gomega) are significantly outdated, creating a mismatch between the code's stated requirements and the available ecosystem versions. This suggests the project is either in a transitional state or relies on specific, potentially unstable, dependency versions.
This repository is a curated list of Chinese independent developer projects, organized into three editions: main (websites/apps), programmer (CLI/tools), and games. It is primarily a static Markdown list, but includes a Python automation script (process_item.py) that scans GitHub issue comments, uses OpenAI to extract project details, and creates pull requests to add new entries. The repository relies on GitHub Actions for scheduled runs and a Claude skill definition for AI-assisted maintenance. While the list itself is the main product, the automation pipeline demonstrates a reusable pattern for community-driven list curation. The codebase is minimal and functional, with the automation script being the only non-trivial software component. The repository is actively maintained with frequent updates, but the list's growth requires periodic archiving to stay within GitHub's rendering limits.
Airtest is a cross-platform UI automation testing framework developed by NetEase, primarily targeting mobile games and apps. It provides a unified Python API and CLI for automating interactions on Android, iOS, Windows, and Linux devices. The core mechanism is image recognition using computer vision algorithms (template matching, keypoint matching with SIFT/KAZE/BRISK, etc.) to locate UI elements, combined with device-specific input simulation via ADB, minitouch, WebDriverAgent, and pywinauto. The framework supports complex gestures, multi-touch, screen recording, and HTML report generation with step logs and screenshots. Architecturally, Airtest is a library with a CLI entry point (`airtest run/report/info`). It uses a device abstraction layer with platform-specific implementations (Android, IOS, Windows, Linux) that share a common API through `airtest.core.api`. The image matching is handled by the `aircv` subpackage, which offers multiple matching strategies configurable via `CVSTRATEGY`. The Android module employs a proxy pattern for screen capture (Minicap, Javacap, ADB) and touch input (Minitouch, Maxtouch, ADB), allowing runtime switching. The framework also integrates with the Poco UI hierarchy inspection tool and supports cloud device testing. While the primary focus is application testing, the repository includes a small benchmark directory that compares the performance of various image matching algorithms, producing metrics like CPU, memory, and keypoint counts. This is a minor component and does not shift the overall classification away from application. The codebase is well-structured with clear separation of concerns, but shows signs of technical debt such as Python 2 compatibility shims, pinned outdated dependencies (opencv-contrib-python ≤ 4.6.0.66, numpy < 2.0), and bundled precompiled binaries (minitouch, minicap, iproxy) that require periodic updates. The project is actively maintained with frequent commits and community engagement, but test coverage is limited due to reliance on real devices.
Integuru is a Python application that reverse-engineers API requests from browser traffic to generate runnable integration code. It takes a HAR file (HTTP archive) containing browser network requests and cookie data, then uses LLMs to analyze these requests to identify which endpoint performs a user-specified action. The system builds a dependency graph to determine what prerequisite requests are needed to gather dynamic parameters (like IDs, tokens), and finally generates Python code that can reproduce the action by making the necessary HTTP requests in the correct order. The architecture uses LangGraph for workflow orchestration, with specialized LLM-powered agents handling different aspects of the analysis (URL identification, dynamic parameter extraction, dependency resolution).
EvoNexus is an AI-powered business operating system with a dashboard for managing various applications and services. It has features for managing systems, knowledge base, and user authentication, and uses Docker for containerization.
NOALBS is a Rust application that automatically manages OBS stream quality by monitoring real-time stream health (bitrate, RTT, offline detection) from various stream servers (Nginx-RTMP, SLS, Xiu, Mediamtx, etc.) and switching scenes in OBS accordingly. It also functions as a Twitch/Kick chat bot, allowing streamers to control streaming behavior via commands. The architecture is a single async binary using Tokio, with modular traits for stream servers (StreamServersCommands), broadcasting software (BroadcastingSoftwareLogic), chat platforms, and configuration. Key data flows: config loading → state initialization → polling stream server stats via HTTP → receiving OBS WebSocket events → switching logic updates OBS scenes. External dependencies include OBS WebSocket, Twitch IRC/PubSub, and various streaming server APIs. The codebase demonstrates non-obvious Rust patterns such as using `typetag::serde` for serializable trait objects and a localization system with YAML files. However, some commented-out code, hardcoded delays, and a warning about an OBS source feature being broken indicate areas of incomplete refactoring.
This repository is a collection of Home Assistant blueprints (YAML automation and script templates) that enable voice-controlled music playback via the Music Assistant integration. It provides three distinct options: a fully local intent-based automation using custom conversation triggers, an LLM-enhanced automation that leverages an external LLM conversation agent to parse natural language queries, and an LLM script that can be used as a tool by LLM conversation agents for more flexible music requests. The blueprints are well-structured with multi-language support (English, Dutch, French, German, Hungarian, Italian, Portuguese, Slovak, Spanish, Finnish) and demonstrate advanced use of Home Assistant's conversation triggers, Jinja2 templating, and integration with Music Assistant's play_media service. The repository is community-driven and actively maintained, with detailed documentation and changelogs. While tightly coupled to Home Assistant and Music Assistant, the blueprints exhibit good craftsmanship in handling target resolution, shuffle logic, and LLM prompt engineering.
Agregarr is a full-stack Plex collection management application built with Next.js and Express, written in TypeScript. It automates the creation, synchronization, and visual customization of Plex collections by integrating with numerous external media sources and APIs including Trakt, TMDB, IMDb, Letterboxd, MDBList, AniList, MyAnimeList, Tautulli, Overseerr, Radarr, and Sonarr. The core architecture follows a monolithic pattern: a single server process running both the React frontend and Express backend, with SQLite persistence via TypeORM and a robust migration system. In production, Agregarr performs scheduled full syncs and incremental quick syncs of collection definitions to Plex, applies poster overlays based on configurable conditions (ratings, resolution, audio codecs, HDR formats), manages placeholder items for upcoming content, and can auto-request missing media through Radarr/Sonarr or Overseerr. The UI provides per-library collection views with drag-and-drop reordering, a visual poster editor with snap-to-guides and layering, an overlay editor with condition evaluation, and dashboard statistics from Tautulli. The codebase demonstrates solid engineering with clear separation of concerns, a template method pattern for collection sources (`BaseCollectionSync`), consistent API client wrappers, and modular UI form sections. However, it carries significant maintenance overhead from fragile web scraping (IMDb WAF, Cloudflare bypass), a large dependency surface including Chromium and Playwright, commented-out legacy code from its Overseerr fork, and reliance on external APIs that may change unexpectedly. The project is actively maintained with frequent migrations and feature additions.
Botright is a Python library built on Playwright that provides advanced browser automation with stealth features to evade bot detection. It includes proxy management, fingerprint spoofing using real browser profiles (chrome-fingerprints), human-like mouse movements, and CAPTCHA solving for hCaptcha, reCAPTCHA, and Geetest (though Geetest support is currently disabled). The library wraps Playwright's API with a custom layer that intercepts browser events, modifies user agent, platform, and other fingerprinting vectors, and injects anti-detection scripts. It supports both headless and headed modes, proxy rotation, and response caching. The codebase is well-structured but has commented-out modules indicating incomplete transitions (e.g., Geetest).
This repository is the official Microsoft Azure DevOps Node.js SDK, a client library that provides programmatic access to Azure DevOps Services and Team Foundation Server (TFS) REST APIs. It is not an application itself but a reusable library consumed by Node.js applications (e.g., CI/CD automation, monitoring tools, or custom DevOps integrations). The architecture follows a classic SDK pattern: a central `WebApi` factory class that creates typed API clients for each service area (Build, Git, Test, Work Item Tracking, etc.). All API clients inherit from a common `ClientApiBase` class, use `VsoClient` for version negotiation, and rely on `typed-rest-client` for HTTP transport. The bulk of the codebase is auto-generated from Azure DevOps REST API metadata, resulting in large interface definition files with `TypeInfo` metadata for serialization. Key reusable components include authentication handlers (basic, PAT, bearer, NTLM), rate-limiting utilities, and a chunked upload mechanism for file containers. The library is well-maintained, with ongoing commits, CI pipelines, and sample code demonstrating usage across all major API areas. However, the heavy reliance on generated code and the DO NOT EDIT warnings mean that customizations or fixes must be done upstream.
This repository is a curated collection of 280+ n8n workflow templates, organized into 18 categories covering email automation, AI agents, RAG pipelines, social media, DevOps, document processing, and more. It is not a software application itself but a library of importable JSON workflow definitions for the n8n automation platform. The templates demonstrate practical automation patterns such as webhook-triggered AI agents, scheduled data enrichment, human-in-the-loop approvals, and vector-store-based retrieval-augmented generation. While the collection is extensive and popular (25k+ stars), individual templates vary in quality, with many containing hardcoded placeholders, deprecated model references, and no automated testing. The repository serves as a valuable reference for n8n users seeking ready-made automation blueprints, but users must adapt credentials and verify compatibility with their n8n version.
This repository is an automated maintenance and triage system called 'Clownfish' (ProjectClownfish) that manages the large open-source `openclaw/openclaw` repository. It is a Node.js application driven by GitHub Actions workflows that continuously processes GitHub issues and pull requests: performing deduplication, canonical selection, security-sensitive detection, automated repair of contributor branches, exact-head merge preflight validation, and closeout of superseded/fixed-by-candidate items. The system operates in plan (read-only), autonomous (lightweight actions), and execute (mutating) modes, with strict permission boundaries defined in YAML frontmatter job files. It relies on the GitHub API, a Codex/AI worker for classification, and a suite of deterministic safety gates (re-fetch live state, check updated_at, block unsafe closeouts) before any mutation. The codebase is well-structured with clear separation of concerns (scripts, job definitions, results), but it is tightly coupled to the specific workflow of a single large repository, limiting direct reuse. Notable patterns include a robust job frontmatter schema, deterministic preflight validation, and a centralized security routing mechanism.
This repository is a large collection of bare-metal firmware projects for STM32 microcontrollers (F0, F1, F3, G0, G4 families), authored by Edward V. Emelianov. It contains dozens of independent example and application projects covering USB CDC virtual serial ports, CAN bus gateways, sensor drivers (BMP280, MLX90640, DHT22, DS18B20, etc.), stepper motor control, servo control, LED displays, and more. The code is written in C with direct register access (no HAL) and uses a custom USB stack with ring-buffer-based I/O. Each project is self-contained with its own main.c, hardware initialization, and command parser, typically communicating over USB or UART with a simple text-based protocol. The architecture is monolithic per project: a main loop processes periodic tasks (ADC sampling, sensor reads, CAN message handling) and responds to commands received via USB or UART. Key entry points are the main.c files in each project directory. Data flows involve sensor acquisition (ADC, I2C, SPI), optional processing (median filtering, dew point calculation), and output via USB CDC, CAN, or UART. External dependencies are minimal: only an ARM GCC toolchain and the STM32 CMSIS-like headers provided in the inc/ folder. The repository also includes KiCad PCB designs and gerber files for many projects, indicating a full hardware+software development cycle. While the code is functional and covers a wide range of embedded use cases, it suffers from significant code duplication (ringbuffer.c, usb.c, strfunc.c are copy-pasted across many projects) and lacks a centralized library or build system. Deprecated folders and multiple versions of similar projects (e.g., chronometer_v2, chronometer_v3) add clutter. The repository is best viewed as a personal collection of working examples and prototypes rather than a polished framework. However, several components (ring buffer, string utilities, USB stack) are well-implemented and could be extracted for reuse in other STM32 projects.
This repository is a heavily modified fork of the RuneLite client for Old School RuneScape (OSRS), extended with a comprehensive automation and botting framework branded as 'Microbot'. The system provides a full game client with a plugin architecture, overlays, configuration system, and event bus, plus a large set of automation scripts for questing, combat, walking, banking, and inventory management. The core application is a Java desktop client using Swing, Guice dependency injection, and LWJGL for GPU rendering. Key entry points include the RuneLite main class, the Microbot plugin (which orchestrates script execution), and an HTTP agent server that exposes client state and allows remote control. The architecture is modular with composite Gradle builds for the cache, API, and client modules, but the microbot automation code is tightly coupled to game internals and relies on hardcoded IDs and reflection, making it fragile to game updates. The codebase integrates a vendored shortest-path planner (upstreamPlanner) for pathfinding, a quest helper subsystem with hundreds of quest-specific step classes, and a natural mouse movement library for human-like input simulation. External dependencies include OkHttp for network requests, Gson for serialization, and FlatLaf for UI theming. The project also includes cache-reading tools for extracting game definitions (items, NPCs, objects, interfaces, scripts) and a crowdsourcing plugin for collecting gameplay data. While the official RuneLite plugins are preserved, the majority of development effort appears focused on the automation layer, which introduces significant maintenance risk and potential policy violations.