Primary finding
Exit-code table contradicts step 2's 'gated' filter assumption
lowbuglow
- skills/huggingface-trending/SKILL.md:56-66
The HF list endpoints (/api/models, /api/datasets, /api/spaces) do not include a top-level `gated` boolean by default for every entry; that field commonly only appears on the per-item detail endpoint. The skill instructs the agent to filter on `gated: true` from the list payload extracted in step 1, but step 1 never lists `gated` among the extracted fields. The filter rule is effectively unreachable unless an extra detail fetch is added — a subtle correctness gap that will silently let gated drafts through.
Recommendation
Either add `gated` to the step-1 extraction list (and document a per-item fetch if needed) or remove the gated-filter rule to avoid promising filtering the code can't perform.