Skip to content
Back to skills

Nano Remove Startup Task

ASecurity

Remove a Startup Task from a Nano application - deletes the BaseStartupTask-derived class. Use when the user asks to remove a startup task, cache warm-up, or one-time initialization from a Nano API, Web, or Console application.

  • 5 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added October 4, 2026
content-marketingapi

Works with

  • api

Security analysis

A100/100

Scanned October 4, 2026

npx -y skills add Nano-Core/Nano.Templates --skill nano-remove-startup-task --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Nano Remove Startup Task?

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

Security grade badge for Nano Remove Startup Task
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/nano-core-nano-remove-startup-task/badge)](https://www.skillsdirectory.com/skills/nano-core-nano-remove-startup-task)

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: nano-remove-startup-task
description: Remove a Startup Task from a Nano application - deletes the BaseStartupTask-derived class. Use when the user asks to remove a startup task, cache warm-up, or one-time initialization from a Nano API, Web, or Console application.
---

# Nano remove startup task

Removes a Startup Task from an existing Nano API, Web, or Console application — the counterpart
to `nano-add-startup-task`.

## Before making any change, determine

1. **Which task?** Confirm the class name/file if the project has more than one — check
   `Startup/` (or search for `BaseStartupTask`/`IStartupTask` if not in the conventional
   location).
2. **Behavior change to flag, not a crash risk.** Nothing else in the app takes a required
   dependency on a startup task's existence, so removal never breaks compilation or DI. The one
   real effect: if [Health Checks](nano-add-health-checks) are enabled, the app's readiness gate
   no longer waits on whatever this task was checking/warming — readiness becomes available
   sooner, and whatever the task guaranteed (a warm cache, a verified dependency) is no longer
   guaranteed before traffic is accepted. Tell the user this plainly if it seems load-bearing.

## Startup task class

Delete the file. No config, no registration, no other references to clean up — discovery is by
type, so removing the class is the entire change.

## After making the change

- Show the user the file removed.
- Restate step 2 if the removed task looked like it was guarding something meaningful (an
  external dependency check, a required warm-up) rather than being purely cosmetic.

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…