morganlinton/BeautifulRust

This page introduces an external open-source repository. It is not an HDATF product.

What it does

BeautifulRust provides three skills and lint configuration for coding agents writing, reviewing, or porting Rust. It is an agent-guidance plugin, not a standalone compiler or Rust model. Inputs include implementation requests, existing files or diffs, and source code with tests from another language. Outputs include Rust implementations, prioritized review reports with rule references and locations, or porting records mapping tests and deliberate differences. Review guidance separates error handling, public API design, ownership, and safety issues and supplies concrete fix examples. Porting guidance moves existing tests first to check behavioral differences. It must be connected as a Claude Code plugin or installed in a supported agent's skill location; installing skills does not enable project CI checks. Separate lint configuration must be incorporated into Cargo and run with a Rust toolchain to enforce machine-checkable rules. Small project-run evaluations do not guarantee correctness or defect removal across projects, so generated output and real tests still need review.

License

MIT Permissive. Commercial use and changes are allowed if the copyright notice is kept.

More in this category

• t3dotgg/tstack
  tstack is a collection of skills for coding agents that organize the work between a requested change and a reviewed GitHub pull request. It targets Claude Code and Codex users who want repeatable review, handover and PR monitoring procedures rather than a separate hosted service. Inputs are a change request or an existing branch or PR, and outputs include the changed code, verification evidence, review results and a PR handover or authorized merge. full-send links implementation, proof, sol-loop review, PR creation and CI monitoring, whereas full-stop ends with an open, unmerged PR for a person to handle. The documented merge gate checks the latest commit's evidence, required checks, review findings, branch freshness and mergeability. babysit-pr distinguishes T3 Code's watcher from the alternative pr-wait tool and requires bot findings to be checked against source before changing code. The README requires authenticated GitHub CLI access, python3 for pr-wait and access to other providers' models for council or sol-loop. These are editable workflow instructions, and model agreement or a watcher notification is not proof of correctness or permission to override an organization's approval policy.
• AgriciDaniel/claude-seo
  Claude SEO is a Claude Code plugin and skill collection for inspecting website search visibility. Given a site or page URL, it analyzes technical settings, content, structured data, and AI-search readiness. Full audits combine specialist subagent results into prioritized improvement plans and report files with verification criteria. A headless browser handles JavaScript-rendered pages, and individual pages or topics can be audited separately. Beyond plugin installation, a supported Python environment and browser preparation are required, with diagnostic checks available. Basic audits are distinct from Google field-data and external search-data connections, which need appropriate accounts and API permissions. Multi-agent audits can increase model usage, and storing reports locally does not mean analyzed material avoids external model processing. Without field APIs, some performance and indexing judgments are estimates, while content revealed only after clicks or scrolling can produce noisy results. Findings do not guarantee search rankings or completed indexing and require follow-up with real pages and search tools.
• google/elephant-goldfish-model
  Elephant-Goldfish Model is a coding-agent plugin for teams that need to clarify design decisions before implementation, not a new language model. It takes requirements, design drafts and referenced source material and produces concept briefs, specifications and review reports. An Elephant keeps the project context, while Goldfish reviewers examine supplied documents without the earlier conversation. Review instructions separate broad architectural concerns, comprehension, design criticism and implementation readiness, with people deciding which findings to address. A separate skill compares design documents with referenced code and reports differences rather than silently repairing them. The plugin uses its host's models and permissions and requires the complete skills, reviewer personas and document standards, not just a copied skill file. Supported sessions must actually expose fresh subagent contexts for review, and the review stops when that capability is absent. The published verification record distinguishes tested local workflows from unresolved cloud trace checks, and the project explicitly does not replace tests or human judgment or constitute an officially supported Google product.
• microsoft/skill-recorder
  Skill Recorder is a desktop app that records work performed on screen and turns it into procedures an AI can reuse. It targets users and automation specialists who find it difficult to manually document repetitive work. Inputs include screen captures, application switches, window titles, clipboard previews, optional spoken narration and records from the app's own terminal. After recording, it groups events into step material, supplements ambiguous parts with relevant screen information and uses GitHub Copilot to reconstruct intent and sequence. Users can review and edit that analysis before generating an agent procedure file called SKILL.md or an automation procedure for scheduled or triggered execution. The resulting procedures are designed to prefer the target agent's command line tools and native capabilities over replaying clicks. Getting started requires installing the source release app and a GitHub account with Copilot access, with macOS the primary target and Windows 11 also supported. Recording and transcription are local, but choosing analysis sends events, extracted screen images and relevant text to GitHub's cloud. Preview and sensitive information protection do not guarantee safety or successful replay, so secrets must stay out of recordings and generated procedures need review.
• unclebob/ub-mode
  ub-mode is an instruction skill for developers using coding agents, not a standalone application or model API. It addresses code changes that appear complete without demonstrating behavior, controlling complexity or examining weak tests. Inputs are a change request and repository context, while intended outputs are verified small changes and an explanation of the work. Its workflow starts with a failing test and a minimal working change, then calls for root-cause repair and behavior-preserving restructuring. The skill links separate tools for complexity and coverage, structural duplication, and mutation testing, which deliberately changes code to see whether tests detect the change. The skill's CRAP limit combines complexity and test coverage, and its duplication rule is a project policy rather than proof that similar code is wrong. Use requires a compatible agent skill loader plus separately available tools and the target project's test environment; the companion mutator declares Python 3.11 or later. Loading the text alone does not install or execute those tools, and neither metric thresholds nor agent instructions establish correctness or safe permission handling.

Only repositories in the ranked Trendshift lists are included, and the lists are used only to find candidates. We do not copy their ranks. Descriptions, licenses and star counts come from each GitHub repository. The notes are our own reading. We have not tested these projects, and a place on a trending list does not prove quality.