hashnode-api
Provides comprehensive guidance on using the Hashnode GraphQL API for blog management and content creation.
Install this skill
or
86/100
Security score
The hashnode-api skill was audited on Feb 12, 2026 and we found 10 security issues across 2 threat categories. Review the findings below before installing.
Categories Tested
Security Issues
medium line 341
Webhook reference - potential data exfiltration
SourceSKILL.md
| 341 | 4. **Webhook integration:** Handle Hashnode webhook events |
low line 27
External URL reference
SourceSKILL.md
| 27 | - **Endpoint:** `https://gql.hashnode.com` (POST only) |
low line 29
External URL reference
SourceSKILL.md
| 29 | - **Legacy API:** `https://api.hashnode.com` is discontinued - migrate to new endpoint |
low line 36
External URL reference
SourceSKILL.md
| 36 | - **Get your PAT:** https://hashnode.com/settings/developer → "Generate New Token" |
low line 323
External URL reference
SourceSKILL.md
| 323 | 1. **API Endpoint:** Test queries in the playground at https://gql.hashnode.com |
low line 324
External URL reference
SourceSKILL.md
| 324 | 2. **Authentication:** Generate your PAT at https://hashnode.com/settings/developer |
low line 347
External URL reference
SourceSKILL.md
| 347 | - **Test in playground:** Use https://gql.hashnode.com to test queries before implementing |
low line 383
External URL reference
SourceSKILL.md
| 383 | - **API Docs:** https://apidocs.hashnode.com |
low line 384
External URL reference
SourceSKILL.md
| 384 | - **Playground:** https://gql.hashnode.com |
low line 429
External URL reference
SourceSKILL.md
| 429 | This skill was automatically generated from official Hashnode documentation. To refresh with updated documentation, regenerate the skill using the latest docs from https://apidocs.hashnode.com. |
Scanned on Feb 12, 2026
View Security DashboardGitHub Stars 2
Rate this skill
Categorymarketing
UpdatedMay 21, 2026
openclawapicontent-marketerproduct-marketergrowth-marketermarketing-analystsocial-media-managermarketing
majiayu000/claude-skill-registry-data