Token导航 LogoToken导航

Agent Skill · 开发

writeas(writeas 命令行)

writeas 用于处理 GitHub 仓库、Issue、Pull Request 和代码协作信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要围绕仓库状态、代码变更或协作事项进行整理时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

writeas 是开发类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为接触敏感数据;许可证为 MIT,第三方扫描有未通过项,按安装量在开发类的 21,746 个 Skill 里排第 15,714。

总安装 569周安装 23GitHub Stars 31下载 178核验 2026-05-01

安装说明

本站只整理中文说明,不托管安装包,也不代用户安装。
GitHub
许可证
MIT

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:writeas(writeas 命令行)
来源仓库:https://github.com/rawveg/skillsforge-marketplace
仓库路径:skills/writeas
安装命令:
npx skills add https://github.com/rawveg/skillsforge-marketplace --skill writeas
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。不同来源提供的安装方式可能略有差异;本站展示可直接复制的安装命令,安装前请核对来源页面。

skills.shnpx skills
npx skills add https://github.com/rawveg/skillsforge-marketplace --skill writeas

这个 Skill 是做什么的

开发类 Skill 面向写代码、改代码和排查问题,一般会读写仓库文件,部分还会执行构建或测试命令。

writeas 用于处理 GitHub 仓库、Issue、Pull Request 和代码协作信息,适合围绕仓库状态或协作事项进行整理。适用于代码协作与项目管理场景,可结合来源仓库和原始 README 核验具体用法。通过 npx skills add 命令从指定 GitHub 仓库安装,需确认权限范围和维护状态。

安装前建议确认是否会触发联网、命令执行或文件读写,避免误操作生产数据。writeas 属于开发类 Skill,可作为该场景下的辅助能力补充。

来源仓库内路径:skills/writeas

上手步骤

4 步
  1. 1

    确认自己的宿主工具

    公开资料标注支持 Codex、Claude、Cursor、Gemini CLI;先确认自己用的是其中之一,再按对应工具的 Skills 目录放置。

  2. 2

    拿到安装命令

    可以直接复制的命令是 npx skills add https://github.com/rawveg/skillsforge-marketplace --skill writeas;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

    命令执行完要完全退出宿主工具再打开,让新装的 Skill 被重新扫描到,否则列表里可能看不到。

  4. 4

    按最小权限试用

    它需要接触敏感数据,先在测试目录或测试账号里跑,确认没问题再放到正式项目。

常见问题

6 条

writeas 怎么安装?

在终端执行 npx skills add https://github.com/rawveg/skillsforge-marketplace --skill writeas。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

writeas 支持哪些 AI 工具?

公开资料标注支持 Codex、Claude、Cursor、Gemini CLI。其他工具只要能读取本地 Skill 目录,一般也能手动放进去,但要自己确认触发方式是否一致。

writeas 需要什么权限?

权限级别是接触敏感数据。该 Skill 可能接触密钥、Token、环境变量或敏感配置,应进入高风险复核队列,默认不自动发布。

writeas 是免费的吗?

来源标注的许可证是 MIT。本站不代收任何费用,也不托管安装包;能否商用、要不要署名,以许可证原文为准。

writeas 用的人多吗?

公开数据是累计安装 569 次,近一周安装 23 次,下载 178 次,GitHub 31 星。这些数字来自第三方目录统计,只能当作热度参考,不代表质量或安全性。

writeas 安全吗?

第三方扫描有未通过项,风险较高。除非你确认过源码,否则不建议直接安装到常用环境。

值得选的地方和要先想清楚的地方

值得选的地方

  • 同时适配 4 种工具,换客户端不用重新找替代品。
  • 3 个目录同时收录,说明这个 Skill 流传比较广。
  • 许可证明确为 MIT,商用和分发边界好判断。

先想清楚的地方

  • 需要接触敏感数据,装到常用环境前要先评估影响面。
  • 第三方扫描存在提醒项或未通过项,需要人工逐条确认。
  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 Codex,想直接扩展它能力的人。
  • 需要处理开发类任务、又不想每次都手写提示词的人。

不太适合

  • 环境里有大量密钥、凭证,不方便给第三方 Skill 读取的人。
  • 需要厂商级技术支持和 SLA 的生产系统。

开发类 Skill 对比

6 个同类
Skill总安装GitHub 星权限许可证扫描
skill-vetter

技能审查员 · OpenClaw

8,779,018986操作浏览器MIT-0通过
ontology

本体论 · OpenClaw

6,636,960576只读MIT-0通过
entra-app-registration

内部应用程序注册 · Codex、Claude

6,631,872764接触敏感数据未明确通过
entra-app-registration

内部应用程序注册 · Codex、Claude

3,757,680201接触敏感数据未明确通过
nano-banana-pro

纳米香蕉专业版 · OpenClaw

3,526,898364接触敏感数据MIT-0有提醒
writeas

writeas 命令行 · 本页

56931接触敏感数据MIT未通过

按安装量取同分类前几名;数字来自第三方目录统计,只作热度参考,不代表质量结论。

SKILL.md 原文

Write.as Skill

Comprehensive assistance with Write.as and WriteFreely API development, based on official API documentation. This skill provides practical guidance for building applications around the Write.as blogging platform and its open-source WriteFreely implementation.

When to Use This Skill

This skill should be triggered when:

  • Working with the Write.as REST API (https://write.as/api/)
  • Building applications that interact with Write.as or WriteFreely
  • Implementing blog post creation, updates, or management
  • Setting up user authentication for Write.as accounts
  • Creating or managing collections (blogs)
  • Implementing crossposting to Twitter, Medium, or Tumblr
  • Integrating Markdown rendering for blog posts
  • Debugging Write.as API calls or authentication issues
  • Working with anonymous posts and post claiming
  • Building self-hosted WriteFreely instances

Key Concepts

Core Terminology

Posts: Markdown-based articles with metadata. Posts can be created anonymously or associated with a user account.

Collections: Known as "blogs" in the UI. Container for multiple posts with customizable settings. Creating collections requires a Pro account.

Users: Registered accounts with password, email, and resource access. Users can own multiple collections and posts.

Tokens: Used for authentication and post management. Anonymous posts return a token for later modifications, while user operations use access tokens via Authorization: Token {access_token} header.

Authentication

  • Anonymous: No authentication required. Store the returned token for later updates/deletions.
  • User-based: Login via /api/auth/login to get an access token, then pass it in the Authorization header.

Quick Reference

Creating an Anonymous Post

POST https://write.as/api/posts
Content-Type: application/json

{
  "body": "This is a post.",
  "title": "My First Post"
}

Response:

{
  "code": 201,
  "data": {
    "id": "rf3t35fkax0aw",
    "token": "ozPEuJWYK8L1QsysBUcTUKy9za7yqQ4M",
    "title": "My First Post",
    "body": "This is a post."
  }
}

Note: Save the token to update or delete this post later.

Updating a Post (Anonymous)

POST https://write.as/api/posts/{POST_ID}
Content-Type: application/json

{
  "token": "ozPEuJWYK8L1QsysBUcTUKy9za7yqQ4M",
  "body": "This is an updated post."
}

User Authentication

POST https://write.as/api/auth/login
Content-Type: application/json

{
  "alias": "username",
  "pass": "password"
}

Response:

{
  "code": 200,
  "data": {
    "access_token": "00000000-0000-0000-0000-000000000000",
    "user": {
      "username": "username"
    }
  }
}

Creating a Post as Authenticated User

POST https://write.as/api/posts
Authorization: Token 00000000-0000-0000-0000-000000000000
Content-Type: application/json

{
  "body": "# My authenticated post\n\nThis post is linked to my account.",
  "title": "Authenticated Post"
}

Styling Posts with Fonts

POST https://write.as/api/posts
Content-Type: application/json

{
  "body": "This is a monospace code post.",
  "font": "code"
}

Available fonts:

  • sans - Sans-serif with word wrap
  • serif or norm - Serif with word wrap
  • wrap - Monospace with word wrap
  • mono - Monospace without wrap
  • code - Syntax-highlighted monospace

Crossposting to Social Media

POST https://write.as/api/posts
Authorization: Token 00000000-0000-0000-0000-000000000000
Content-Type: application/json

{
  "body": "Check out my new post!",
  "title": "My Post",
  "crosspost": [
    {"twitter": "yourusername"},
    {"medium": "yourusername"}
  ]
}

Supported services: Twitter, Tumblr, Medium

Creating a Collection (Pro Feature)

POST https://write.as/api/collections
Authorization: Token 00000000-0000-0000-0000-000000000000
Content-Type: application/json

{
  "alias": "my-blog",
  "title": "My Blog"
}

Publishing to a Collection

POST https://write.as/api/collections/{ALIAS}/posts
Authorization: Token 00000000-0000-0000-0000-000000000000
Content-Type: application/json

{
  "body": "# First blog post\n\nWelcome to my blog!",
  "title": "Hello World"
}

Moving Anonymous Post to Collection

POST https://write.as/api/collections/{ALIAS}/collect
Authorization: Token 00000000-0000-0000-0000-000000000000
Content-Type: application/json

[
  {
    "id": "rf3t35fkax0aw",
    "token": "ozPEuJWYK8L1QsysBUcTUKy9za7yqQ4M"
  }
]

Rendering Markdown to HTML

POST https://write.as/api/markdown
Content-Type: application/json

{
  "raw_body": "# Hello\n\nThis is **Markdown**."
}

Response:

{
  "code": 200,
  "data": {
    "body": "<h1>Hello</h1>\n<p>This is <strong>Markdown</strong>.</p>"
  }
}

Error Handling

All API responses follow this structure:

{
  "code": 200,
  "data": {}
}

Common HTTP status codes:

  • 200 - Success
  • 201 - Created successfully
  • 400 - Bad request or malformed data
  • 401 - Missing or invalid authentication
  • 403 - Insufficient permissions (e.g., creating collection without Pro)
  • 404 - Resource not found
  • 410 - Post unpublished (may return later)
  • 429 - Rate limited

Reference Files

This skill includes comprehensive documentation in references/:

  • api.md - Complete Write.as API documentation including:

- All available endpoints (posts, collections, users, formatting) - Request/response examples - Authentication methods - Crossposting configuration - Error codes and handling

Use view to read the API reference file when detailed information is needed.

Working with This Skill

For Beginners

  1. Start with anonymous posts: No authentication required, perfect for testing
  2. Save the token: Always store the token returned when creating anonymous posts
  3. Test with single posts: Create, update, retrieve, and delete one post before scaling
  4. Read error responses: The API provides clear error messages in the response body

For Intermediate Users

  1. Implement user authentication: Use /api/auth/login to get access tokens
  2. Work with collections: Create blogs and organize posts into collections
  3. Enable crossposting: Automatically share posts to Twitter, Medium, or Tumblr
  4. Claim anonymous posts: Convert anonymous posts to user-owned posts with /api/posts/claim
  5. Use post styling: Apply different fonts (code, sans, mono) for various content types

For Advanced Users

  1. Build full applications: Leverage all endpoints for complete blog management
  2. Self-host WriteFreely: Deploy open-source WriteFreely instances
  3. Implement rate limiting: Respect API limits and handle 429 responses
  4. Use client libraries: Leverage official libraries (Go, Swift, Java) or community libraries (PHP, Python, JavaScript,.NET)
  5. Handle edge cases: Implement retry logic, token refresh, and error recovery

Navigation Tips

  • Authentication flow: See api.md → "Users" section
  • Post management: See api.md → "Posts" section
  • Collection setup: See api.md → "Collections" section
  • Crossposting: See api.md → "Crossposting" section
  • Error handling: See api.md → "Error Handling" section

API Best Practices

  1. Store tokens securely: Never commit access tokens or post tokens to version control
  2. Handle anonymous posts: Always save the token field when creating anonymous posts
  3. Respect rate limits: Implement exponential backoff on 429 responses
  4. Use HTTPS: All API endpoints require HTTPS
  5. Test with small datasets: Verify your integration with a few posts before scaling
  6. Check Pro status: Collection creation requires a Pro account
  7. Validate Markdown: Test Markdown rendering with /api/markdown before posting
  8. Handle 410 gracefully: Unpublished posts may return with 410 status

Common Use Cases

Building a Blog Publishing Tool

Use authenticated user endpoints to create collections, publish posts, and manage content.

Creating a Markdown Editor Integration

Implement post creation with Markdown preview using /api/markdown endpoint.

Social Media Cross-Poster

Leverage the crosspost parameter to automatically share posts to multiple platforms.

Anonymous Blogging Platform

Build an app using anonymous post creation, storing tokens locally for later management.

Content Migration Tool

Use /api/posts/claim to import anonymous posts into a user account.

Client Libraries

Official:

Community:

  • PHP, Python, JavaScript, Vala,.NET Core (see Write.as documentation)

Resources

Official Documentation

Key Features

  • Backwards compatibility: Endpoints rarely removed; new features added alongside existing
  • Flexible authentication: Works anonymously or with user tokens
  • Markdown-first: All content uses Markdown formatting
  • Self-hosting ready: WriteFreely powers Write.as and independent instances

Notes

  • All API requests must use HTTPS
  • Anonymous posts can be claimed by authenticated users
  • Collections (blogs) require a Pro subscription on Write.as
  • Post IDs are permanent and unique
  • Tokens are sensitive credentials - protect them like passwords
  • The API maintains backwards compatibility - old integrations continue working

Updating

This skill is based on the official Write.as API documentation. For the latest updates, refer to:

平台分布

Claude Code

29.63%
按下载量换算53

Antigravity

26.99%
按下载量换算48

windsurf

16.69%
按下载量换算30

trae

12.7%
按下载量换算23

Codex

7.27%
按下载量换算13

OpenCode

3.93%
按下载量换算7

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

未通过

权限和风险

接触敏感数据

该 Skill 可能接触密钥、Token、环境变量或敏感配置,应进入高风险复核队列,默认不自动发布。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。来源安全扫描存在提醒或未通过项,安装前请自行复核。

继续浏览同类 Skills