How do I install the New Source skill?

Run npx skillmds@latest add mampfes/new-source in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is New Source safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with New Source?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is New Source free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published New Source?

mampfes (@mampfes) published this skill. Their other Agent Skills are listed on their SkillMD profile.

New Source by mampfes — Agent Skill

Name: New Source
Author: mampfes

New Source

Investigate and implement support for a new waste-collection provider in hacs_waste_collection_schedule. Use when a contributor wants a council, municipality, or provider added, including shared-platform and ICS options.

mampfes d720929 2 files · 2.2 KB Updated Sep 17, 2026

File contents

Add a waste-collection source

Gather inputs

Establish whether the user is a contributor or an upstream maintainer if that is not already known.
Obtain the provider name, country, resident schedule URL, and one public known-working example input. Never request or expose the user's home address.

Investigate

Spawn the source-investigator custom agent with the gathered inputs.
Ask it to return its complete Investigation Report and make no filesystem changes.
Present the report to the user.
If the provider is already supported, offer the exact shared-config change. If it is not feasible, explain the blocker and alternatives from the report.
For a new source, confirm the recommended ICS, API, HTML, or PDF approach before implementation when the choice is materially uncertain.

Implement

Spawn the source-implementer custom agent with the full Investigation Report and any user decisions.
Tell it to write the source or shared-config change, create required documentation, lint every changed Python file, run structural tests, and live-test real TEST_CASES where applicable.
Present its Implementation Report and resolve test failures before submission.

Prepare submission

Encourage SOURCE_CODEOWNERS = ["@handle"] for Python or codeowners: for ICS YAML.
Inspect the diff and remove generated files listed in AGENTS.md from the proposed change. Never run update_docu_links.py.
Run the required lint and tests from AGENTS.md for every changed file.
Guide contributor-owned branch, commit, push, and PR steps. Do not perform remote actions unless the user explicitly asks.
Target mampfes/hacs_waste_collection_schedule:master and use Add source: <Provider Name> (<module>) as the PR-title pattern.

---name: new-sourcedescription: Investigate and implement support for a new waste-collection provider in hacs_waste_collection_schedule. Use when a contributor wants a council, municipality, or provider added, including shared-platform and ICS options.---# Add a waste-collection source## Gather inputs1. Establish whether the user is a contributor or an upstream maintainer if that is not already known.2. Obtain the provider name, country, resident schedule URL, and one public known-working example input. Never request or expose the user's home address.## Investigate1. Spawn the `source-investigator` custom agent with the gathered inputs.2. Ask it to return its complete Investigation Report and make no filesystem changes.3. Present the report to the user.4. If the provider is already supported, offer the exact shared-config change. If it is not feasible, explain the blocker and alternatives from the report.5. For a new source, confirm the recommended ICS, API, HTML, or PDF approach before implementation when the choice is materially uncertain.## Implement1. Spawn the `source-implementer` custom agent with the full Investigation Report and any user decisions.2. Tell it to write the source or shared-config change, create required documentation, lint every changed Python file, run structural tests, and live-test real `TEST_CASES` where applicable.3. Present its Implementation Report and resolve test failures before submission.## Prepare submission1. Encourage `SOURCE_CODEOWNERS = ["@handle"]` for Python or `codeowners:` for ICS YAML.2. Inspect the diff and remove generated files listed in `AGENTS.md` from the proposed change. Never run `update_docu_links.py`.3. Run the required lint and tests from `AGENTS.md` for every changed file.4. Guide contributor-owned branch, commit, push, and PR steps. Do not perform remote actions unless the user explicitly asks.5. Target `mampfes/hacs_waste_collection_schedule:master` and use `Add source: <Provider Name> (<module>)` as the PR-title pattern.

Frequently asked questions