Skip to content
Back to skills

Annotate What Crosses A Module Boundary

ASecurity

When adding a function other modules will call, annotate its parameters and return

  • 2 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added October 17, 2026
ai-agents

Security analysis

A100/100

Scanned October 17, 2026

npx -y skills add samugit83/cortex --skill annotate-what-crosses-a-module-boundary --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Annotate What Crosses A Module Boundary?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Annotate What Crosses A Module Boundary
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/samugit83-annotate-what-crosses-a-module-boundary/badge)](https://www.skillsdirectory.com/skills/samugit83-annotate-what-crosses-a-module-boundary)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: annotate-what-crosses-a-module-boundary
description: When adding a function other modules will call, annotate its parameters and return
---

# Annotations

Annotate what crosses a module boundary; leave local helpers alone if the
annotation would only repeat the name.

- Every parameter and the return of a public function get an annotation.
- Prefer the abstract collection in a parameter (`Iterable`, `Mapping`) and the
  concrete one in a return (`list`, `dict`): be liberal in what you accept.
- `None` in a union is written `X | None`, never bare `Optional` half of the
  file and `| None` the other half.

An annotation that has to be read twice is worse than none: give the shape a
name instead.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.