# cleanuptool

> Program to clean up you Alexa dev skill list, lambda function and logs after a skill is no longer neeeded.

Latest version **1.2.2** (published 2018-10-15) · ISC license · 0 weekly downloads

## Install

```sh
npm install cleanuptool
pnpm add cleanuptool
yarn add cleanuptool
bun add cleanuptool
```

Provides the command `cleanUp`.

## Health

**Score 15/100 (F)** — status: abandoned.

Positive: no vulnerabilities.

Warnings: low downloads; no types; no esm support.

Negative: abandoned; low maintenance score.

## Facts

| | |
|---|---|
| Version | 1.2.2 |
| Published | 2018-10-15 |
| First published | 2018-08-16 |
| Weekly downloads | 0 |
| License | ISC |
| TypeScript types | none |
| Module format | CommonJS |
| Dependencies | 1 |
| Unpacked size | 43.9 KB |
| Known vulnerabilities | 0 |
| Install scripts | no |
| Author | Bernardo Bezerra |
| Maintainers | bbezerra |
| Keywords | alexa, skills, ask-cli, awscli |

## Links

- npm: https://www.npmjs.com/package/cleanuptool
- npm.io page: https://npm.io/package/cleanuptool

## Dependencies (1)

- [shelljs](https://npm.io/package/shelljs.md) ^0.8.2

## Alternatives

- [@opentelemetry/exporter-zipkin](https://npm.io/package/@opentelemetry/exporter-zipkin.md) — 14.8M weekly downloads
- [pusher-js](https://npm.io/package/pusher-js.md) — 2.0M weekly downloads
- [browserify](https://npm.io/package/browserify.md) — 1.7M weekly downloads
- [sqs-consumer](https://npm.io/package/sqs-consumer.md) — 1.7M weekly downloads
- [@sanity/eventsource](https://npm.io/package/@sanity/eventsource.md) — 930.8K weekly downloads

## Recent versions

- 1.2.2 (latest) — 2018-10-15
- 1.2.1 — 2018-08-24
- 1.2.0 — 2018-08-24
- 1.1.1 — 2018-08-24
- 1.1.0 — 2018-08-16
- 1.0.4 — 2018-08-16

## README

# CleanUp - A tool to help cleaning up after an Alexa Skill has served its purpose
As an Alexa Skills enthusiast, I am constantly creating skills to try out new features. Because of this, there is always a large number of skills, lambda functions and log groups that are left behind in my developer account. 

I created this small script in order to help mitigate this issue. After creating, deploying, modifying, logging, breaking, fixing and breaking again (basic developer life, amirite??) all you have to do is execute this script in the skill's root folder. It will delete the skill, the lambda function associated with it and the logs associated with the lambda function. However, the files will still be in your local server, in case you wish to deploy the skill again.

The behavior explained above is the default one. This script has a set of options that will allow you to choose what to delete.

## Installing
Via npm:

``` bash
$ npm install cleanuptool
```

## Usage
While in the skill's root folder (the folder that contains at least the folders **lambda**, **models** and the file **skill.json**, but mainly the hidden **.ask** folder), execute:

``` bash
$ cleanUp
```
and your account will get cleared of the skill and it's appendages.

**BUT WAIT!!** That is not all! Let's say you only want to remove the skill, but leave the lambda function and the logs alone. All you have to do is use the -s flag followed by your skillID :
``` bash
$ cleanUp -s [skillID]
```
There are 3 other flags:
* -g [functionName]: this flag, followed by the functionName will delete the log groups associated with the function name;
* -l [functionName]: this flag, followed by the functionName will delete the lambda function;
* -h: this will print out a help message;

---
_Source: https://npm.io/package/cleanuptool · Machine-readable twin of the npm.io package page. Health data is recomputed on every publish._