Skip to content
Back to skills

Extension Review Guidelines

ASecurity

- Module-scope instances or signals - Process isolation violations (Gtk in shell, St in prefs) - Deprecated imports (`imports.misc.lang` etc.) - Missing cleanup (objects created in `enable()` not destroyed in `disable()`) - CSS line comments (`//`) - GObject constructor with JS-only properties

  • 14 stars
  • 0 votes
  • 0 copies
  • 3 views
  • Added September 19, 2026
toolsgoshellapi

Works with

  • api

Security analysis

A100/100

Scanned September 19, 2026

npx -y skills add itsnin/spotlight --skill extension-review-guidelines --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Extension Review Guidelines?

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

Security grade badge for Extension Review Guidelines
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/itsnin-extension-review-guidelines/badge)](https://www.skillsdirectory.com/skills/itsnin-extension-review-guidelines)

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
# extension-review-guidelines

## Hard Rejections
- Module-scope instances or signals
- Process isolation violations (Gtk in shell, St in prefs)
- Deprecated imports (`imports.misc.lang` etc.)
- Missing cleanup (objects created in `enable()` not destroyed in `disable()`)
- CSS line comments (`//`)
- GObject constructor with JS-only properties

## Metadata Rules
- UUID must be valid email-like format
- Shell version must be valid GNOME versions
- Version name max 16 characters

## Legal
- Code and assets must be compatible with the declared license
- No trademark or copyright violations

## EGO Verified Rules
No `imports.gi` — use ESM `import gi://Name` instead. Console API with appropriate levels like `debug`, `warn` and `error` rather than bare `log`. No `run_dispose` unless absolutely necessary. Optional chaining only for genuinely potentially-null objects, never for guaranteed objects. No `try`/`catch` around standard API calls, only for file I/O, JSON parsing, and genuinely external data. CSS uses only `/* */` block comments, never `//` line comments. No defensive null checks that mask bugs.

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.