Description
plugins/skyscanner/README.md:13-15 documents the command as:
| Command |
Description |
skyscanner flights <origin> <destination> |
Visible round-trip flight results from a warmed browser session |
But --depart-date and --return-date are both required (plugins/skyscanner/flights.js:169-170):
{ name: 'depart-date', required: true, help: 'Outbound date as YYYY-MM-DD' },
{ name: 'return-date', required: true, help: 'Return date as YYYY-MM-DD' },
Copying the table row as-is fails with a missing-argument error. Only the Examples block below it (README.md:20) is runnable.
Impact
Small, but this is the one community plugin surfaced in the root README.md community table, so it is the reference example for future plugin READMEs.
Suggested fix
Change the table row to skyscanner flights <origin> <destination> --depart-date <YYYY-MM-DD> --return-date <YYYY-MM-DD>.
Minor related nit: the example uses --depart-date 2026-08-01, a date now in the past. A relative or clearly-future date ages better.
Description
plugins/skyscanner/README.md:13-15documents the command as:skyscanner flights <origin> <destination>But
--depart-dateand--return-dateare both required (plugins/skyscanner/flights.js:169-170):Copying the table row as-is fails with a missing-argument error. Only the Examples block below it (
README.md:20) is runnable.Impact
Small, but this is the one community plugin surfaced in the root
README.mdcommunity table, so it is the reference example for future plugin READMEs.Suggested fix
Change the table row to
skyscanner flights <origin> <destination> --depart-date <YYYY-MM-DD> --return-date <YYYY-MM-DD>.Minor related nit: the example uses
--depart-date 2026-08-01, a date now in the past. A relative or clearly-future date ages better.