Token导航 LogoToken导航

Agent Skill · 前端设计

tumblr(tumblr 搜索)

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

tumblr 是前端设计类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为接触敏感数据;许可证为 MIT,第三方扫描有提醒项,按安装量在前端设计类的 10,216 个 Skill 里排第 5,707。

总安装 618周安装 25GitHub Stars 31下载 194核验 2026-05-01

安装说明

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

安装方式

通过对话安装

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

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

命令行安装

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

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

这个 Skill 是做什么的

前端设计类 Skill 关注页面结构、视觉规范和组件写法,输出通常是可运行的界面代码。

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

安装方式:通过 GitHub 仓库安装,命令为 npx skills add https://github.com/rawveg/skillsforge-marketplace --skill tumblr。适用宿主:Codex、Claude、Cursor、Gemini CLI。

来源仓库内路径:skills/tumblr

上手步骤

4 步
  1. 1

    确认自己的宿主工具

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

  2. 2

    拿到安装命令

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

  3. 3

    安装后重启宿主

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

  4. 4

    按最小权限试用

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

常见问题

6 条

tumblr 怎么安装?

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

tumblr 支持哪些 AI 工具?

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

tumblr 需要什么权限?

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

tumblr 是免费的吗?

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

tumblr 用的人多吗?

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

tumblr 安全吗?

第三方扫描有提醒项,说明存在需要人工确认的行为。安装前请打开源码看清它读了什么、联网到哪里。

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

值得选的地方

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

先想清楚的地方

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

适不适合你

更适合

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

不太适合

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

前端设计类 Skill 对比

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

前端设计 · Codex、Claude

8,823,360126,072只读MIT通过
vercel-composition-patterns

Vercel 组合模式 · Codex、Claude

3,858,81625,893需要联网MIT通过
vercel-react-native-skills

Vercel React native skills 前端 · Codex、Claude

2,468,66425,878只读MIT通过
adapt

adapt 搜索 · Codex、Claude

2,027,04023,125操作浏览器未明确通过
bolder

bolder 分析 · Codex、Claude

2,004,28823,130只读未明确通过
tumblr

tumblr 搜索 · 本页

61831接触敏感数据MIT有提醒

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

SKILL.md 原文

Tumblr API Skill

Comprehensive assistance with Tumblr API development, authentication, and integration. This skill provides practical guidance for building applications that interact with Tumblr's platform.

When to Use This Skill

This skill should be triggered when:

  • Integrating with the Tumblr API (any version)
  • Implementing OAuth 1.0a or OAuth 2.0 authentication for Tumblr
  • Working with Tumblr blog data, posts, likes, or followers
  • Building Tumblr clients, dashboard tools, or analytics applications
  • Debugging Tumblr API requests or responses
  • Understanding Tumblr's Neue Post Format (NPF) or legacy post types
  • Managing rate limits or API quotas
  • Handling Tumblr webhooks or real-time updates

Quick Reference

1. Fetch Blog Information

Retrieve basic blog metadata including title, description, and post count:

curl -H 'User-Agent: MyApp/1.0' \
  'https://api.tumblr.com/v2/blog/staff.tumblr.com/info?api_key=YOUR_API_KEY'

Response includes: Blog title, URL, post count, description, avatar, theme settings.

2. Get Recent Posts

Retrieve the 5 most recent posts from a blog:

curl -H 'Authorization: Bearer YOUR_ACCESS_TOKEN' \
  'https://api.tumblr.com/v2/blog/staff.tumblr.com/posts?limit=5'

Query parameters:

  • limit: 1-20 posts per request
  • offset: Pagination offset
  • tag: Filter by tag
  • npf=true: Request Neue Post Format

3. OAuth 2.0 Token Exchange

Exchange authorization code for access token:

curl -X POST https://api.tumblr.com/v2/oauth2/token \
  -F grant_type=authorization_code \
  -F code=YOUR_AUTH_CODE \
  -F client_id=YOUR_CONSUMER_KEY \
  -F client_secret=YOUR_CONSUMER_SECRET

Scopes: basic, write, offline_access

4. Get Blog Avatar

Fetch blog avatar image URL:

curl 'https://api.tumblr.com/v2/blog/staff.tumblr.com/avatar/128'

Available sizes: 16, 24, 30, 40, 48, 64, 96, 128, 512 (default: 64)

5. Retrieve Liked Posts

Get posts liked by a blog:

curl -H 'Authorization: Bearer YOUR_ACCESS_TOKEN' \
  'https://api.tumblr.com/v2/blog/staff.tumblr.com/likes?limit=20&offset=0'

Parameters: limit, offset, before (timestamp), after (timestamp)

6. Queue Management

Retrieve queued posts:

curl -H 'Authorization: Bearer YOUR_ACCESS_TOKEN' \
  'https://api.tumblr.com/v2/blog/myblog.tumblr.com/posts/queue'

Reorder queue:

curl -X POST https://api.tumblr.com/v2/blog/myblog.tumblr.com/posts/queue/reorder \
  -H 'Authorization: Bearer YOUR_ACCESS_TOKEN' \
  -d 'post_id=123456789'

7. Get Followers

Retrieve blog followers:

curl -H 'Authorization: Bearer YOUR_ACCESS_TOKEN' \
  'https://api.tumblr.com/v2/blog/myblog.tumblr.com/followers'

Response includes: Total follower count, follower blog objects with names and URLs.

8. Filter Posts by Tag

Retrieve posts with specific tag:

curl -H 'User-Agent: MyApp/1.0' \
  'https://api.tumblr.com/v2/blog/staff.tumblr.com/posts?api_key=YOUR_KEY&tag=photography&limit=10'

9. Standard API Response Format

All Tumblr API responses follow this structure:

{
  "meta": {
    "status": 200,
    "msg": "OK"
  },
  "response": {
    "blog": { },
    "posts": [ ]
  }
}

10. Working with Blog Identifiers

Three interchangeable identifier formats:

# Blog name
/v2/blog/staff/info

# Hostname
/v2/blog/staff.tumblr.com/info

# UUID (stable, persistent)
/v2/blog/t:0aY0xL2Fi1OFJg4YxpmegQ/info

Recommendation: Use UUID for long-term stability (survives blog renames).

Key Concepts

Authentication Levels

  1. None - Public endpoints (blog info, public posts) require no authentication
  2. API Key - Use OAuth Consumer Key as api_key query parameter
  3. OAuth - Signed requests using OAuth 1.0a or OAuth 2.0 for user-specific data

Rate Limits

Per IP Address:

  • 300 calls/minute
  • 18,000 calls/hour
  • 432,000 calls/day

Per Consumer Key:

  • 1,000 calls/hour
  • 5,000 calls/day

Action Limits:

  • 250 posts/day
  • 200 follows/day
  • 1,000 likes/day

Post Formats

Legacy Post Types:

  • Text, Photo, Quote, Link, Chat, Audio, Video, Answer

Neue Post Format (NPF):

  • Modern block-based format
  • Posts with type: blocks or is_blocks_post_format: true
  • Request with npf=true parameter
  • Contains content (blocks), layout (specifications), trail (reblog chain)

Post IDs

Post IDs are 64-bit integers. Important: Use id_string field for JavaScript or languages with unsafe integer handling.

Required Headers

User-Agent: Mandatory for all requests. Must be consistent. Format: AppName/Version

Content-Type: Required for POST/PUT with body. Accepted:

  • application/json
  • application/x-www-form-urlencoded
  • multipart/form-data

Reference Files

This skill includes comprehensive documentation in references/:

  • api.md - Complete Tumblr API documentation including:

- All authentication methods (OAuth 1.0a, OAuth 2.0, API key) - Blog endpoints (info, posts, avatar, likes, following, followers) - User endpoints (dashboard, likes, following) - Post creation and management - Queue and draft management - Neue Post Format (NPF) specification - Legacy post type fields - Rate limits and best practices - Response format documentation

Use the view command to read specific reference files when detailed information is needed.

Working with This Skill

For Beginners

  1. Start with public endpoints - No authentication needed:

- Fetch blog info: /v2/blog/{blog}/info?api_key={key} - Get public posts: /v2/blog/{blog}/posts?api_key={key}

  1. Register your application:

- Visit https://www.tumblr.com/oauth/apps - Get OAuth Consumer Key and Secret - Use Consumer Key as api_key for public endpoints

  1. Test with API Console:

- https://api.tumblr.com/console - Interactive testing environment

For OAuth Implementation

  1. Choose OAuth version:

- OAuth 2.0: Modern, simpler, bearer tokens - OAuth 1.0a: Legacy, more complex, signed requests

  1. OAuth 2.0 flow:

- Redirect user to authorization URL with scopes - Exchange authorization code for access token - Use token in Authorization: Bearer {token} header

  1. OAuth 1.0a flow:

- Request temporary credentials - Redirect user to authorize - Exchange verifier for access token - Sign all requests with token

For Advanced Features

  1. Neue Post Format (NPF):

- Add npf=true to any post-returning endpoint - Work with content blocks and layout objects - Access full reblog trail

  1. Pagination:

- Use offset for numeric pagination - Use before/after with timestamps for chronological navigation - Check _links object for next/previous URLs

  1. Partial responses:

- Use fields parameter to specify blog object fields - Reduces response size and improves performance

  1. JSONP support:

- Add jsonp=callbackName to GET requests - Useful for client-side JavaScript

Common Patterns

Authentication Flow (OAuth 2.0)

# Step 1: Redirect user to authorization URL
https://www.tumblr.com/oauth2/authorize?client_id={key}&response_type=code&scope=basic%20write&state={random}

# Step 2: User authorizes, Tumblr redirects back with code
# Your redirect URL receives: ?code={auth_code}

# Step 3: Exchange code for access token
curl -X POST https://api.tumblr.com/v2/oauth2/token \
  -F grant_type=authorization_code \
  -F code={auth_code} \
  -F client_id={consumer_key} \
  -F client_secret={consumer_secret}

# Step 4: Use access token in requests
curl -H 'Authorization: Bearer {access_token}' \
  'https://api.tumblr.com/v2/user/info'

Error Handling

{
  "meta": {
    "status": 401,
    "msg": "Unauthorized"
  },
  "response": [ ],
  "errors": [
    {
      "title": "Unauthorized",
      "code": 401,
      "detail": "OAuth authentication required"
    }
  ]
}

Common status codes:

  • 200: Success
  • 401: Unauthorized (missing/invalid credentials)
  • 404: Not Found (blog or post doesn't exist)
  • 429: Rate Limit Exceeded
  • 503: Service Temporarily Unavailable

Handling Large Post Counts

# Fetch all posts using pagination
offset=0
limit=20

while true; do
  curl "https://api.tumblr.com/v2/blog/staff.tumblr.com/posts?api_key={key}&limit=${limit}&offset=${offset}"
  offset=$((offset + limit))
  # Check if response contains fewer than 'limit' posts, then break
done

Resources

Official Links

Official Clients

  • JavaScript: tumblr.js
  • Ruby: tumblr_client
  • PHP: tumblr/tumblr
  • Python: pytumblr
  • Java: jumblr
  • Objective-C: TMTumblrSDK
  • Go: tumblr/tumblr.go

Best Practices

  1. Always include User-Agent header - Inconsistent or missing User-Agent may result in suspension
  2. Respect rate limits - Implement exponential backoff for 429 responses
  3. Use UUIDs for blog identifiers - More stable than blog names (survive renames)
  4. Cache blog info - Reduce API calls by caching static blog data
  5. Use NPF for new integrations - Legacy formats may be deprecated
  6. Handle 64-bit integers carefully - Use id_string for JavaScript
  7. Validate responses - Check meta.status before processing response

Notes

  • This skill was generated from official Tumblr API documentation
  • All endpoints use base URL: https://api.tumblr.com
  • API version is included in path: /v2/
  • HTTPS is required for all API requests
  • Reference files preserve structure and examples from source docs
  • Code examples include language detection for better syntax highlighting

Updating

To refresh this skill with updated documentation:

  1. Re-run the scraper with the same configuration
  2. The skill will be rebuilt with the latest information from the official GitHub repository

平台分布

Claude Code

27.88%
按下载量换算54

Antigravity

20.45%
按下载量换算40

windsurf

18.25%
按下载量换算35

trae

12.98%
按下载量换算25

Codex

7.85%
按下载量换算15

OpenCode

3.41%
按下载量换算7

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

可疑

权限和风险

接触敏感数据

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

安装前确认

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

继续浏览同类 Skills