Skip to content
TrustedSkillsbeta
Back to all skills

Pyrefly Type Coverage

Official
pytorch·vlatest·backend

Pyrefly Type Coverage analyzes your code to identify all used types and their dependencies, boosting understanding & debugging efficiency.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add pytorch/pytorch --skill pyrefly-type-coverage -a claude-code

  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

pytorch

Matched to the vendor's own GitHub organisation.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned pytorch/pytorch at edd4fc2d34.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
edd4fc2d34
Manifest
.claude/skills/pyrefly-type-coverage/SKILL.md
Scanned
1 file, 236 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

This skill helps you improve type coverage in your Python code using Pyrefly, Meta's type checker. It guides you through a structured process of removing error suppression directives, configuring stricter type checking within your pyrefly.toml file, running the type checker to identify missing annotations, and then adding those annotations. The goal is to systematically resolve all identified type errors in your Python files or directories.

When to use it

  • When you want to improve the robustness and maintainability of your Python code through better type hinting.
  • During refactoring efforts where increased type safety is desired.
  • To address specific type checking errors flagged by Pyrefly.
  • For projects already using a pyrefly.toml configuration file.

Key capabilities

  • Provides step-by-step instructions for improving type coverage with Pyrefly.
  • Guides users on removing error suppression directives (pyre-ignore-all-errors).
  • Explains how to configure stricter type checking within pyrefly.toml.
  • Instructs users on running the Pyrefly type checker and interpreting its output.
  • Offers examples of common annotation patterns for function signatures, class attributes, and complex types.

Example prompts

  • "Guide me through improving type coverage in my Python file."
  • "How do I configure stricter type checking using pyrefly?"
  • "What are some common annotation patterns I can use with Pyrefly?"

Tips & gotchas

  • Prerequisites: This skill requires that your project already has a pyrefly.toml configuration file.
  • The skill focuses on resolving errors; suppressing them with # pyrefly: ignore[...] should be a last resort after attempting to fix the underlying issue.
  • Type annotations may require Python 3.10 or later syntax for complex types.