Please describe the changes this PR makes and why it should be merged, as well as any and all proof of successful tests:

Semantic versioning classification:

• [x] This PR changes the framework's interface (methods or parameters added)
  • [ ] This PR includes breaking changes (methods removed or renamed, parameters moved or removed)
• [ ] This PR only includes non-code changes, like changes to README, etc.

In this PR I coded a function to change large numbers to a K notation (69420 = 69.4k) and removed duplicate stats on /bot command (like servers and total servers) #103

Some changes influenced by discord are there like:

putting the deploy command functionality in ready.js. Why? Because when trying to setup I needed to /deploy to show all slash commands... but I didn't have any slash commands to use /deploy checking if some value is undefined in a file I forgot

Please describe the changes this PR makes and why it should be merged, as well as any and all proof of successful tests: This PR adds a sample task list command, allowing users to view and edit the state of tasks related to the skills they've started. This PR also removes ambiguity from field names in the skill struct, as well as adds extra documentation for them. Semantic versioning classification:

• [x] This PR changes the framework's interface (methods or parameters added)
  • [x] This PR includes breaking changes (methods removed or renamed, parameters moved or removed)
• [ ] This PR only includes non-code changes, like changes to README, etc.

Please describe the changes this PR makes and why it should be merged, as well as any and all proof of successful tests: This PR aims to delete Yarn's lockfile from the codebase. As Yarn is not used with this project, it's fine to delete it. Yarn's lockfile can also cause useless merge conflicts during PRs, which must be resolved manually.
Semantic versioning classification:

• [ ] This PR changes the framework's interface (methods or parameters added)
  • [ ] This PR includes breaking changes (methods removed or renamed, parameters moved or removed)
• [x] This PR only includes non-code changes, like changes to README, etc.

Please describe the changes this PR makes and why it should be merged, as well as any and all proof of successful tests:

Weekly report fully works with error handling at every stage

Semantic versioning classification:

• [x] This PR changes the framework's interface (methods or parameters added)
  • [ ] This PR includes breaking changes (methods removed or renamed, parameters moved or removed)
• [ ] This PR only includes non-code changes, like changes to README, etc.

• Must be able to view tree and figure out a way to let the user jump around easily (it shouldn't take 6 clicks to reach Fitness VI etc. Just think of a suitable format and make it work

Please describe the changes this PR makes and why it should be merged, as well as any and all proof of successful tests:

Semantic versioning classification:

• [x] This PR changes the framework's interface (methods or parameters added)
  • [ ] This PR includes breaking changes (methods removed or renamed, parameters moved or removed)
• [ ] This PR only includes non-code changes, like changes to README, etc.

On /bot now users are called registered users Instead of client.cache.whatever changed to totalGuilds All functions are now arrow functions

Please describe the changes this PR makes and why it should be merged, as well as any and all proof of successful tests: This is a potential fix to #82

I reviewed the cron config and found a potential error in it. I removed the date checking code and replaced it with some that changes the cron time to GMT + 12 and then checks every hour from sunday 12AM to Monday 12AM. This will make sure that it runs at every possible hour on Sunday.

Semantic versioning classification: ???

• [ ] This PR changes the framework's interface (methods or parameters added)
  • [ ] This PR includes breaking changes (methods removed or renamed, parameters moved or removed)
• [ ] This PR only includes non-code changes, like changes to README, etc.

Is your feature request related to a problem? Please describe. Where will we send weekly reports in servers?

Describe the solution you'd like Simple setup command for server admins to determine where bot messages will be sent

Please describe the changes this PR makes and why it should be merged, as well as any and all proof of successful tests:

Semantic versioning classification:

• [x] This PR changes the framework's interface (methods or parameters added)
  • [ ] This PR includes breaking changes (methods removed or renamed, parameters moved or removed)
• [ ] This PR only includes non-code changes, like changes to README, etc.

Is your feature request related to a problem? Please describe. A clear and concise description of what the problem is. Ex. I'm always frustrated when [...] We have two lockfiles on the repository, Updating with NPM changes Yarn's lockfile as well, causing conflicts that must be solved manually.

Describe the solution you'd like A clear and concise description of what you want to happen. A decision on which one package manager we start using.

Describe alternatives you've considered A clear and concise description of any alternative solutions or features you've considered. N/A

Additional context Add any other context or screenshots about the feature request here. N/A

Please describe the changes this PR makes and why it should be merged, as well as any and all proof of successful tests:

Semantic versioning classification:

• [x] This PR changes the framework's interface (methods or parameters added)
  • [x] This PR includes breaking changes (methods removed or renamed, parameters moved or removed)
• [ ] This PR only includes non-code changes, like changes to README, etc.

Please describe the changes this PR makes and why it should be merged, as well as any and all proof of successful tests:

Semantic versioning classification:

• [ ] This PR changes the framework's interface (methods or parameters added)
  • [ ] This PR includes breaking changes (methods removed or renamed, parameters moved or removed)
• [ ] This PR only includes non-code changes, like changes to README, etc.

Please describe the changes this PR makes and why it should be merged, as well as any and all proof of successful tests:

Semantic versioning classification:

• [ ] This PR changes the framework's interface (methods or parameters added)
  • [ ] This PR includes breaking changes (methods removed or renamed, parameters moved or removed)
• [x] This PR only includes non-code changes, like changes to README, etc.