← Products

Developer tools
⚙ Needs: Python code to document (the skill is documentation…

PyTorch docstring conventions: write function and method docstrings the PyTorch way (short listing)

Write PyTorch-style docstrings — raw strings, Sphinx/reST, signature-first-line, math directives, cross-references, Args/Returns/Examples sections, native vs C-bound vs in-place vs alias patterns

At a glance
What
Write PyTorch-style docstrings — raw strings, Sphinx/reST, signature-first-line, math directives, cross-references, Args/Returns/Examples sections, native vs C-bound vs in-place vs alias patterns
Cost
Free
Needs
Python code to document (the skill is documentation guidance the agent follows, not software to install)
Install
Copy the installer prompt below into your Muse — your agent does the rest.

Version:

@
Created by: @pytorch
⌁

Install

Prerequisites: Python code to document (the skill is documentation guidance the agent follows, not software to install) Install "PyTorch docstring conventions: write function and method docstrings the PyTorch way" for me. It gives my agent @pytorch's official docstring conventions: raw strings, Sphinx/reST format, signature-first-line, math directives, cross-reference roles, Args/Keyword args/Returns/Examples sections, and the native, C-bound, in-place and alias patterns, with a worked example and checklist. IMPORTANT: the repo states no license — fetch from the link only, and reproduce nothing beyond the link. Repository: https://github.com/pytorch/pytorch/blob/main/.claude/skills/docstring/SKILL.md 1. Fetch the SKILL.md file (and any helper files) from the repository path into a temporary folder and summarize what it does in one or two sentences. 2. Safety check: review the SKILL.md and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). Review the files for suspicious commands or credential handling; stop on any red flag and never assume the repository is safe. Tell me if anything looks off. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "docstring". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. point the agent at the Python functions to document; nothing else — it's a convention guide). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.

?

Questions

How do I install a build?

Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build up for you — no manual configuration.

Where does my money go?

Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.

What does the ✓ next to a creator’s name mean?

It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a build before installing it.