Propose tests

The user brings the data and a worry; the skill turns the worry into a few tests that earn their run. Every fact is on the documentation page it links; the same page as markdown is at the URL with index.md appended, which is the form to read when your fetch tool summarizes HTML.

Look before you propose

Read the project first: its data sources and the tests it already has, including the ones a Get list of tests from entry points at. Existing tests are not a constraint, they are the conventions: reuse their suites, tags and naming when a new test fits them, and only then. A project with no tests is the common case and needs nothing more than the data sources.

Then look at the data through the project's own connection, so what you propose exists:

catcli exec -d <name> -c "<a statement in the provider's language>"