[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6D6E8FAMYV8KCD141FREQ3F":3,"skill-same:01M6D6E8FAMYV8KCD141FREQ3F":69},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":28,"publishedAt":40,"linkOnly":41,"markdownContent":42,"markdownBody":43,"frontMatter":44,"refName":45,"commitSha":46,"skillDirectory":47,"forksCount":48,"repositoryHtmlUrl":49,"repositoryHomepageUrl":50,"ownerHtmlUrl":51,"ownerBlogUrl":52,"ownerDescription":53,"updatedAt":54,"install":55,"resources":68},"01M6D6E8FAMYV8KCD141FREQ3F","devto-publish",null,"Use this skill when you need to publish articles to Dev.to via their API, format markdown content for Dev.to, or manage blog posts programmatically.","javimosch\u002Fsupercli","javimosch","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F12900508?v=4","01M6D3F2AS6PV75ET9PZ1QGP8J","Javier Leandro Arancibia","01M6D3F2EBNWNJ358Q90P5YQR1",57,"MIT","https:\u002F\u002Fgithub.com\u002Fjavimosch\u002Fsupercli\u002Fblob\u002Fmaster\u002Fplugins\u002Fdevto-publish\u002Fskills\u002Fquickstart\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000018","写作与文案","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000036","内容创作者","PROFESSION","适用职业",[29,30,31,32,33,34,35,36,37,38,39],"publish","devto publish","dev","content","api","markdown","format","blog","markdown content","use","manage","2026-11-10 10:12:30",false,"---\nname: devto-publish\ndescription: Use this skill when you need to publish articles to Dev.to via their API, format markdown content for Dev.to, or manage blog posts programmatically.\n---\n\n# Dev.to Publish Plugin\n\nPublish articles to Dev.to (https:\u002F\u002Fdev.to) via their REST API. Requires a Dev.to API key for authentication.\n\n## Commands\n- `devto-publish \u003Cresource> \u003Caction>` — Execute devto-publish commands\n- `devto article publish` — Publish an article to Dev.to\n\n## Setup\n\n1. Get your Dev.to API key:\n   - Go to https:\u002F\u002Fdev.to\u002Fsettings\u002Faccount\n   - Scroll to \"API Keys\"\n   - Click \"Generate new API key\"\n   - Copy the key\n\n2. Install the plugin:\n   ```bash\n   sc plugins install .\u002Fplugins\u002Fdevto-publish --on-conflict replace --json\n   ```\n\n## Publishing Articles\n\n### Basic Publish\n\n```bash\nsc devto article publish --api-key \"your-api-key\" --title \"My Article Title\" --body-markdown \"# Content here\" --tags \"javascript,nodejs\"\n```\n\n### Publish with Draft Mode\n\nSave as draft instead of publishing immediately:\n\n```bash\nsc devto article publish --api-key \"your-api-key\" --title \"Draft Article\" --body-markdown \"# Content\" --published false --tags \"webdev\"\n```\n\n### Publish from File\n\nPublish an existing markdown file:\n\n```bash\nsc devto article publish --api-key \"your-api-key\" --title \"Article from File\" --body-markdown \"$(cat my-article.md)\" --tags \"tutorial\"\n```\n\n## Input Parameters\n\n| Parameter | Type | Required | Description |\n|-----------|------|----------|-------------|\n| `api_key` | string | Yes | Dev.to API key from https:\u002F\u002Fdev.to\u002Fsettings\u002Faccount |\n| `title` | string | Yes | Article title |\n| `body_markdown` | string | Yes | Article content in Markdown format |\n| `published` | boolean | No | `true` to publish immediately, `false` to save as draft (default: `true`) |\n| `tags` | string | No | Comma-separated tags (max 4) for categorization |\n\n## Response\n\nThe command returns the published article object including:\n- `id`: Article ID\n- `url`: Published article URL (e.g., `https:\u002F\u002Fdev.to\u002Fusername\u002Farticle-slug`)\n- `slug`: URL-friendly identifier\n- `published_timestamp`: When it was published\n- `reading_time_minutes`: Estimated reading time\n\n## Agent Usage Pattern\n\nWhen writing an article for a user:\n\n1. **Draft the content** in Markdown format\n2. **Choose appropriate tags** (max 4) relevant to the content\n3. **Publish** using the command:\n   ```bash\n   sc devto article publish --api-key \"your-api-key\" --title \"Article Title\" --body-markdown \"\u003Cmarkdown content>\" --tags \"tag1,tag2,tag3,tag4\"\n   ```\n4. **Verify** by checking the returned URL\n\n## Best Practices\n\n- **Tag selection**: Use relevant, popular tags to increase visibility\n- **Title quality**: Make titles descriptive and engaging\n- **Markdown formatting**: Use proper Markdown syntax for code blocks, links, images\n- **Content length**: Dev.to recommends articles between 3-15 minutes reading time\n- **Preview**: Use `--published false` to save as draft first, then publish after review\n\n## Example: Publishing Technical Article\n\n```bash\nsc devto article publish \\\n  --api-key \"your-api-key\" \\\n  --title \"How to Build a REST API with Node.js\" \\\n  --body-markdown '# Introduction\\n\\nThis article shows how to build a REST API...\\n\\n```javascript\\nconst express = require(\"express\");\\nconst app = express();\\n```\\n\\n## Conclusion\\n\\n...' \\\n  --tags \"javascript,nodejs,api,webdev\"\n```\n\n## Critical Caveats and Pitfalls\n\n### API Key Security\n- **NEVER commit API keys to git** - they grant full access to your Dev.to account\n- Treat API keys as secrets - rotate if compromised\n- Store in environment variables or secret management systems\n- Do not share in public repositories or issue comments\n\n### Common Publishing Pitfalls\n\n**1. Markdown escaping issues**\n- When passing markdown via command line, escape special characters properly\n- Use single quotes for shell: `--body-markdown '# Title\\n\\nContent'`\n- For complex markdown, write to a file first: `--body-markdown \"$(cat article.md)\"`\n\n**2. Tag format errors**\n- Tags must be comma-separated string, not array: `--tags \"javascript,nodejs\"`\n- Dev.to rejects arrays or space-separated tags\n- Maximum 4 tags - excess tags are ignored or cause errors\n\n**3. Title duplication**\n- Dev.to prevents duplicate titles within 5 minutes\n- If you get this error, wait 5 minutes or modify the title slightly\n- Add unique qualifiers: \"How to Build X (2026 Edition)\"\n\n**4. Content length limits**\n- Dev.to doesn't enforce strict character limits, but very long articles (>15 min read time) may have poor engagement\n- Consider splitting very long content into series\n- Use code blocks judiciously - they count toward reading time\n\n**5. Image handling**\n- Dev.to supports image uploads via web interface\n- External image links work but may break over time\n- For production articles, upload images through Dev.to dashboard first\n\n**6. Code block formatting**\n- Use triple backticks with language: ````javascript` or ````python`\n- Ensure proper indentation in code blocks\n- Dev.to's markdown parser is strict about code block syntax\n\n**7. Draft vs Published confusion**\n- Default is `--published true` - article goes live immediately\n- Use `--published false` for drafts to preview before publishing\n- Drafts are visible only to you in dashboard\n\n**8. Rate limiting**\n- Dev.to may rate limit rapid successive publishes\n- If you get 429 errors, wait 60 seconds before retrying\n- Space out bulk publishes by at least 30 seconds\n\n**9. Character encoding**\n- Ensure UTF-8 encoding for special characters\n- Non-ASCII characters may display incorrectly if not properly encoded\n- Test special characters in draft mode first\n\n**10. URL and link validation**\n- Test all links before publishing\n- Broken links hurt article credibility\n- Use descriptive anchor text, not \"click here\"\n\n## Troubleshooting\n\n**Error: \"unauthorized\" or 401**\n- Ensure the API key is correct and passed via `--api-key` flag\n- Get a new key from https:\u002F\u002Fdev.to\u002Fsettings\u002Faccount\n- Verify no extra spaces in API key\n\n**Error: \"Tag list exceed the maximum of 4 tags\"**\n- Dev.to limits to 4 tags per article\n- Use comma-separated string: `--tags \"tag1,tag2,tag3,tag4\"`\n\n**Error: \"Title has already been used in the last five minutes\"**\n- Dev.to prevents duplicate titles within 5 minutes\n- Wait 5 minutes or modify title slightly\n\n**Error: 429 Too Many Requests**\n- Rate limit exceeded - wait 60 seconds before retrying\n- Space out publishes to avoid hitting limits\n\n**Error: 400 Bad Request**\n- Check JSON formatting in body_markdown\n- Ensure no unescaped quotes in markdown\n- Validate tag format (comma-separated string)\n\n## Dev.to API Limits\n\n- 4 tags maximum per article\n- Title must be unique within 5 minutes\n- Rate limits may apply for rapid publishing\n- API key grants full access to your Dev.to account\n- No hard character limit, but very long articles discouraged\n\n## Related Commands\n\n- View your articles: Visit https:\u002F\u002Fdev.to\u002Fdashboard\n- Edit published articles: Use Dev.to web interface\n- Delete articles: Use Dev.to web interface\n","# Dev.to Publish Plugin\n\nPublish articles to Dev.to (https:\u002F\u002Fdev.to) via their REST API. Requires a Dev.to API key for authentication.\n\n## Commands\n- `devto-publish \u003Cresource> \u003Caction>` — Execute devto-publish commands\n- `devto article publish` — Publish an article to Dev.to\n\n## Setup\n\n1. Get your Dev.to API key:\n   - Go to https:\u002F\u002Fdev.to\u002Fsettings\u002Faccount\n   - Scroll to \"API Keys\"\n   - Click \"Generate new API key\"\n   - Copy the key\n\n2. Install the plugin:\n   ```bash\n   sc plugins install .\u002Fplugins\u002Fdevto-publish --on-conflict replace --json\n   ```\n\n## Publishing Articles\n\n### Basic Publish\n\n```bash\nsc devto article publish --api-key \"your-api-key\" --title \"My Article Title\" --body-markdown \"# Content here\" --tags \"javascript,nodejs\"\n```\n\n### Publish with Draft Mode\n\nSave as draft instead of publishing immediately:\n\n```bash\nsc devto article publish --api-key \"your-api-key\" --title \"Draft Article\" --body-markdown \"# Content\" --published false --tags \"webdev\"\n```\n\n### Publish from File\n\nPublish an existing markdown file:\n\n```bash\nsc devto article publish --api-key \"your-api-key\" --title \"Article from File\" --body-markdown \"$(cat my-article.md)\" --tags \"tutorial\"\n```\n\n## Input Parameters\n\n| Parameter | Type | Required | Description |\n|-----------|------|----------|-------------|\n| `api_key` | string | Yes | Dev.to API key from https:\u002F\u002Fdev.to\u002Fsettings\u002Faccount |\n| `title` | string | Yes | Article title |\n| `body_markdown` | string | Yes | Article content in Markdown format |\n| `published` | boolean | No | `true` to publish immediately, `false` to save as draft (default: `true`) |\n| `tags` | string | No | Comma-separated tags (max 4) for categorization |\n\n## Response\n\nThe command returns the published article object including:\n- `id`: Article ID\n- `url`: Published article URL (e.g., `https:\u002F\u002Fdev.to\u002Fusername\u002Farticle-slug`)\n- `slug`: URL-friendly identifier\n- `published_timestamp`: When it was published\n- `reading_time_minutes`: Estimated reading time\n\n## Agent Usage Pattern\n\nWhen writing an article for a user:\n\n1. **Draft the content** in Markdown format\n2. **Choose appropriate tags** (max 4) relevant to the content\n3. **Publish** using the command:\n   ```bash\n   sc devto article publish --api-key \"your-api-key\" --title \"Article Title\" --body-markdown \"\u003Cmarkdown content>\" --tags \"tag1,tag2,tag3,tag4\"\n   ```\n4. **Verify** by checking the returned URL\n\n## Best Practices\n\n- **Tag selection**: Use relevant, popular tags to increase visibility\n- **Title quality**: Make titles descriptive and engaging\n- **Markdown formatting**: Use proper Markdown syntax for code blocks, links, images\n- **Content length**: Dev.to recommends articles between 3-15 minutes reading time\n- **Preview**: Use `--published false` to save as draft first, then publish after review\n\n## Example: Publishing Technical Article\n\n```bash\nsc devto article publish \\\n  --api-key \"your-api-key\" \\\n  --title \"How to Build a REST API with Node.js\" \\\n  --body-markdown '# Introduction\\n\\nThis article shows how to build a REST API...\\n\\n```javascript\\nconst express = require(\"express\");\\nconst app = express();\\n```\\n\\n## Conclusion\\n\\n...' \\\n  --tags \"javascript,nodejs,api,webdev\"\n```\n\n## Critical Caveats and Pitfalls\n\n### API Key Security\n- **NEVER commit API keys to git** - they grant full access to your Dev.to account\n- Treat API keys as secrets - rotate if compromised\n- Store in environment variables or secret management systems\n- Do not share in public repositories or issue comments\n\n### Common Publishing Pitfalls\n\n**1. Markdown escaping issues**\n- When passing markdown via command line, escape special characters properly\n- Use single quotes for shell: `--body-markdown '# Title\\n\\nContent'`\n- For complex markdown, write to a file first: `--body-markdown \"$(cat article.md)\"`\n\n**2. Tag format errors**\n- Tags must be comma-separated string, not array: `--tags \"javascript,nodejs\"`\n- Dev.to rejects arrays or space-separated tags\n- Maximum 4 tags - excess tags are ignored or cause errors\n\n**3. Title duplication**\n- Dev.to prevents duplicate titles within 5 minutes\n- If you get this error, wait 5 minutes or modify the title slightly\n- Add unique qualifiers: \"How to Build X (2026 Edition)\"\n\n**4. Content length limits**\n- Dev.to doesn't enforce strict character limits, but very long articles (>15 min read time) may have poor engagement\n- Consider splitting very long content into series\n- Use code blocks judiciously - they count toward reading time\n\n**5. Image handling**\n- Dev.to supports image uploads via web interface\n- External image links work but may break over time\n- For production articles, upload images through Dev.to dashboard first\n\n**6. Code block formatting**\n- Use triple backticks with language: ````javascript` or ````python`\n- Ensure proper indentation in code blocks\n- Dev.to's markdown parser is strict about code block syntax\n\n**7. Draft vs Published confusion**\n- Default is `--published true` - article goes live immediately\n- Use `--published false` for drafts to preview before publishing\n- Drafts are visible only to you in dashboard\n\n**8. Rate limiting**\n- Dev.to may rate limit rapid successive publishes\n- If you get 429 errors, wait 60 seconds before retrying\n- Space out bulk publishes by at least 30 seconds\n\n**9. Character encoding**\n- Ensure UTF-8 encoding for special characters\n- Non-ASCII characters may display incorrectly if not properly encoded\n- Test special characters in draft mode first\n\n**10. URL and link validation**\n- Test all links before publishing\n- Broken links hurt article credibility\n- Use descriptive anchor text, not \"click here\"\n\n## Troubleshooting\n\n**Error: \"unauthorized\" or 401**\n- Ensure the API key is correct and passed via `--api-key` flag\n- Get a new key from https:\u002F\u002Fdev.to\u002Fsettings\u002Faccount\n- Verify no extra spaces in API key\n\n**Error: \"Tag list exceed the maximum of 4 tags\"**\n- Dev.to limits to 4 tags per article\n- Use comma-separated string: `--tags \"tag1,tag2,tag3,tag4\"`\n\n**Error: \"Title has already been used in the last five minutes\"**\n- Dev.to prevents duplicate titles within 5 minutes\n- Wait 5 minutes or modify title slightly\n\n**Error: 429 Too Many Requests**\n- Rate limit exceeded - wait 60 seconds before retrying\n- Space out publishes to avoid hitting limits\n\n**Error: 400 Bad Request**\n- Check JSON formatting in body_markdown\n- Ensure no unescaped quotes in markdown\n- Validate tag format (comma-separated string)\n\n## Dev.to API Limits\n\n- 4 tags maximum per article\n- Title must be unique within 5 minutes\n- Rate limits may apply for rapid publishing\n- API key grants full access to your Dev.to account\n- No hard character limit, but very long articles discouraged\n\n## Related Commands\n\n- View your articles: Visit https:\u002F\u002Fdev.to\u002Fdashboard\n- Edit published articles: Use Dev.to web interface\n- Delete articles: Use Dev.to web interface\n",{"name":5,"description":7},"master","d362369a98edfcc6356f3bb152db470c34f08a46","plugins\u002Fdevto-publish\u002Fskills\u002Fquickstart",5,"https:\u002F\u002Fgithub.com\u002Fjavimosch\u002Fsupercli","https:\u002F\u002Fjavimosch.github.io\u002Fsupercli\u002F","https:\u002F\u002Fgithub.com\u002Fjavimosch","intrane.fr","Building robust, open-source infrastructure for the commons. AI-leveraged, self-hosted, built to last.","2026-11-02 18:24:17",{"source":8,"skillName":5,"commands":56,"prompt":66,"zipAvailable":67},[57,60,63],{"tool":58,"command":59},"npx","npx skills add javimosch\u002Fsupercli --skill devto-publish",{"tool":61,"command":62},"bunx","bunx skills add javimosch\u002Fsupercli --skill devto-publish",{"tool":64,"command":65},"pnpm","pnpm dlx skills add javimosch\u002Fsupercli --skill devto-publish","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjavimosch\u002Fsupercli\u002Fblob\u002Fmaster\u002Fplugins\u002Fdevto-publish\u002Fskills\u002Fquickstart\u002FSKILL.md",true,[],[70,81,101,113,126,133],{"skillNo":71,"name":72,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":78,"publishedAt":40},"01M6G7YFZVHRYAY51J0YG9SDNJ","sc-machin-mcp","https:\u002F\u002Fgithub.com\u002Fjavimosch\u002Fsupercli\u002Fblob\u002Fmaster\u002Fsupercli-machin-cli\u002Fskills\u002Fsc-machin-mcp\u002FSKILL.md",[75],{"categoryNo":76,"categoryName":77,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",[79,80],"sc machin mcp","MCP",{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":88,"publishedAt":40},"01M6G7YB179MQMSHZBJDC8TZA8","supercli.quickstart","SuperCLI capability router — discover and execute CLI commands through namespace.resource.action interface","https:\u002F\u002Fgithub.com\u002Fjavimosch\u002Fsupercli\u002Fblob\u002Fmaster\u002Fskills\u002Fsupercli\u002FSKILL.md",[87],{"categoryNo":76,"categoryName":77,"taxonomyType":21,"taxonomyTypeDesc":22},[89,90,91,92,93,94,95,96,97,98,99,100],"supercli quickstart","quickstart","cli","capability router","plugin","discovery","execute","router","discover","commands","interface","supercli,cli,plugin,capability,discovery,agent",{"skillNo":102,"name":103,"nameZh":6,"description":104,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":105,"categories":106,"keywords":107,"publishedAt":40},"01M6G7Y734QS3793YMS5PR146J","zzdoc","Use this skill to compile scdoc manpages with a fast Zig-based compiler.","https:\u002F\u002Fgithub.com\u002Fjavimosch\u002Fsupercli\u002Fblob\u002Fmaster\u002Fplugins\u002Fzzdoc\u002Fskills\u002Fquickstart\u002FSKILL.md",[],[103,108,38,109,110,111,112],"with","zig","fast","compiler","compile",{"skillNo":114,"name":115,"nameZh":6,"description":116,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":117,"categories":118,"keywords":119,"publishedAt":40},"01M6G7Y2WX56K2QJQ9RV2ZKEV7","zx","Use this skill when the user wants to a tool for writing better scripts using node.js.","https:\u002F\u002Fgithub.com\u002Fjavimosch\u002Fsupercli\u002Fblob\u002Fmaster\u002Fplugins\u002Fzx\u002Fskills\u002Fquickstart\u002FSKILL.md",[],[115,120,38,121,122,123,124,125],"scripts","user","node","tool","js","writing",{"skillNo":127,"name":128,"nameZh":6,"description":129,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":130,"categories":131,"keywords":132,"publishedAt":40},"01M6G7Y0M792DGW31HN4TEQT10","zvm","Use this skill when the user wants to manage multiple Zig compiler versions.","https:\u002F\u002Fgithub.com\u002Fjavimosch\u002Fsupercli\u002Fblob\u002Fmaster\u002Fplugins\u002Fzvm\u002Fskills\u002Fquickstart\u002FSKILL.md",[],[128,109,39,38,121,111],{"skillNo":134,"name":90,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":135,"categories":136,"keywords":137,"publishedAt":40},"01M6G7XX51W5HJW09DYXBK92TJ","https:\u002F\u002Fgithub.com\u002Fjavimosch\u002Fsupercli\u002Fblob\u002Fmaster\u002Fplugins\u002Fzstdmt\u002Fskills\u002Fquickstart\u002FSKILL.md",[],[90]]