复制安装命令
用 Codex 或 Claude 安装复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它先审查 Skill 页面再帮你安装。
复制前请先查看来源、License 和安全提示。
A curated library of reusable Codex skills for developers, individuals, and teams.
用 Codex 或 Claude 安装复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它先审查 Skill 页面再帮你安装。
复制前请先查看来源、License 和安全提示。
来源文件:README.md
A curated library of reusable Codex skills for developers, individuals, and teams.
This repository helps you turn OpenAI Codex into a consistent, reliable AI assistant by packaging common workflows into reusable skills instead of repeating prompts.
Codex Skills Library is a collection of focused skills for common developer workflows:
Each skill is small, focused, triggered by natural language, and designed for progressive disclosure.
Skills are organized by domain under skills/. Each skill is a folder with a SKILL.md that includes frontmatter (name, description) and a short workflow.
codebase-orientation: Map entry points, key modules, and build/run paths; include local setup commands, env vars, and a safe starter task.git-basic-helper: Provide minimal, safe git commands with clear intent and warnings for destructive actions.debugging-checklist: Give a prioritized checklist from repro to isolation, logging, and hypothesis validation.error-message-explainer: Translate compiler/runtime errors into plain language, likely root causes, and targeted fixes.linter-fix-guide: Explain lint rules, show the expected pattern, and propose the smallest fix.config-file-explainer: Summarize purpose, key sections, defaults, and which settings are safe to change.data-structure-chooser: Recommend a structure based on operations and constraints, with time/space tradeoffs.dependency-install-helper: List required runtimes, install steps by platform, and verification commands.small-script-generator: Generate tiny automation scripts with safe defaults and a usage example.ticket-breakdown: Turn a request into small, testable steps with dependencies and validation checks.log-summarizer: Group errors, identify the first failure, and propose concrete next actions.readme-polish: Add missing setup details, env vars, and troubleshooting guidance while keeping it concise.function-docstrings: Document purpose, parameters, return values, and error conditions in project style.release-notes-drafter: Group changes by feature/fix/breaking, translate to user impact, and add migration notes.team-onboarding-guide: Provide access/setup steps, key services, and a first-week learning plan.unit-test-starter: Draft tests around core behavior, edge cases, and failure paths with run instructions.integration-test-planner: Identify integration points, scenarios, data flows, and needed fixtures/mocks.bug-repro-plan: Produce a minimal repro with exact steps, environment details, and expected vs actual.buffer-api: Build Buffer GraphQL API integrations for auth, channel discovery, post creation, pagination, errors, and rate limits.api-request-builder: Build curl/fetch requests with auth, headers, and response inspection tips.api-contract-checker: Compare endpoints and payloads, flag breaking changes, and suggest versioning.api-error-taxonomy: Standardize error codes, payload shape, and logging guidance.graphql-query-optimizer: Reduce query depth and N+1 patterns using batching, caching, and pagination.accessibility-basic-check: Check contrast, labels, focus order, and keyboard navigation for regressions.css-layout-helper: Diagnose layout intent and provide minimal flex/grid fixes with rationale.cli-ux-improver: Improve CLI defaults, help text, and errors with actionable next steps.caching-strategy-helper: Choose cache type, TTLs, and invalidation triggers based on freshness needs.queue-processing-patterns: Define idempotency, retries, visibility timeouts, and dead-letter routing.feature-flag-playbook: Plan targeting, rollout phases, monitoring, and cleanup criteria.system-design-draft: Outline components, data flow, storage, and tradeoffs with open questions.sql-query-starter: Build SELECT queries with filters, ordering, limits, and parameter placeholders.db-migration-reviewer: Check lock risk, backfills, ordering, and rollback safety.data-governance-check: Map data sensitivity, retention, access, and audit requirements.ci-failure-triage: Classify failures, identify flake sources, and propose stabilizing fixes.observability-setup: Define key metrics, add correlation IDs, and set alert thresholds.iac-reviewer: Validate security groups, IAM rules, state changes, and deletion risk.platform-migration-plan: Create phased migration steps with compatibility and rollback.multi-region-strategy: Choose active-active or active-passive with data consistency tradeoffs.cross-service-debugger: Correlate logs/traces across services and isolate the failing hop.zero-downtime-migration: Plan dual writes, cutover checks, and rollback triggers.security-quick-scan: Check auth, input validation, secrets, and risky dependencies.threat-modeling: Identify assets, trust boundaries, threats, and mitigations.dependency-risk-audit: Review licenses, vulnerabilities, and maintainer health.compliance-readiness: Map controls to evidence, highlight gaps, and assign remediation.config-hardening: Enforce safer defaults, validation, and secret handling.performance-trace-guide: Capture stable traces, identify hotspots, and propose fixes.scalability-assessment: Estimate growth, find bottlenecks, and suggest scale strategies.performance-budgeting: Set budgets, thresholds, and CI or release enforcement.cost-optimization-review: Identify cost drivers, right-sizing, and savings estimates.reliability-slo-sla: Define SLIs, error budgets, and alert thresholds tied to impact.incident-postmortem: Create a timeline, root cause analysis, and action items.architecture-review: Evaluate assumptions, bottlenecks, and failure modes with tradeoffs.domain-modeling: Identify entities, invariants, and bounded contexts with interfaces.refactor-roadmap: Sequence refactors with tests, flags, and checkpoints.tech-debt-portfolio: Catalog debt, estimate impact, and prioritize with ROI.roadmap-prioritization: Score initiatives by impact, effort, and dependencies.org-standardization: Propose minimal standards and adoption enforcement.vendor-evaluation: Compare vendors by security, integration, cost, and risks.dependency-upgrade-plan: Order upgrades, note breaking changes, and plan rollback.simple-refactor: Improve naming and structure without behavior changes.pr-reviewer: Identify logic bugs, edge cases, and missing tests with severity.skills/ and open a SKILL.md that matches your task.Step-by-step tutorial: https://proflead.dev/posts/codex-skills-explained-101/
Video tutorial: https://youtu.be/d3Ydt6LyGeY
Contributions are welcome. Please open an issue for ideas or send a PR with new skills, improvements, or fixes. If this library is useful, please star the repo and share it with your team.
name: buffer-api
description: Manage Buffer content via the GraphQL API. Use when creating, scheduling, editing, or deleting posts, saving ideas, reading scheduled queues, or pulling post analytics. Not for general API debugging.Create, schedule, edit, and analyze social media content through Buffer's GraphQL API at https://api.buffer.com.
| Goal | API call |
|---|---|
| Create / schedule a post | createPost mutation |
| Save a post as draft | createPost with saveToDraft: true |
| Edit an existing post | editPost mutation |
| Delete a post | deletePost mutation |
| List scheduled / sent posts | posts query with filter: { status: [scheduled] } |
| Get a single post | post query by ID |
| Read post metrics | post { metrics } or aggregatedPostMetrics query |
| Save a content idea | createIdea mutation |
| Find channel IDs | channels query by organization ID |
| Find organization ID | account { organizations { id } } query |
All requests need Authorization: Bearer $BUFFER_API_KEY and Content-Type: application/json.
For personal scripts and automations: use an API key from https://publish.buffer.com/settings/api.
For multi-user apps: use OAuth 2.0 with PKCE — authorize at https://auth.buffer.com/auth, exchange at https://auth.buffer.com/token. Refresh tokens are single-use; always save the new one immediately after refresh.
Get your organization ID (first time only):
query { account { organizations { id name } } }
Get channel IDs for your target platforms:
query GetChannels($orgId: String!) {
channels(input: { organizationId: $orgId }) {
id name service
}
}
Create or schedule the post using the relevant example below.
Check the response — the mutation returns a union type. PostActionSuccess means it worked; MutationError carries the reason it failed. GraphQL always responds with HTTP 200, so always inspect the response body.
Edit or delete if needed using the post id returned in step 3.
Pull analytics after the post publishes (metrics are refreshed daily; allow up to 24 hours after publish).
mutation CreatePost($input: CreatePostInput!) {
createPost(input: $input) {
... on PostActionSuccess {
post { id text status dueAt }
}
... on MutationError { message }
}
}
{
"input": {
"text": "Your post content here",
"channelId": "$CHANNEL_ID",
"schedulingType": "automatic",
"mode": "addToQueue"
}
}
{
"input": {
"text": "Your post content here",
"channelId": "$CHANNEL_ID",
"schedulingType": "automatic",
"mode": "customScheduled",
"dueAt": "2026-07-01T14:00:00.000Z"
}
}
{
"input": {
"text": "Draft content here",
"channelId": "$CHANNEL_ID",
"schedulingType": "automatic",
"mode": "addToQueue",
"saveToDraft": true
}
}
{
"input": {
"text": "Your caption here",
"channelId": "$CHANNEL_ID",
"schedulingType": "automatic",
"mode": "addToQueue",
"assets": [{ "image": { "url": "https://your-public-image-url.jpg" } }]
}
}
Image URL must be publicly accessible. Each asset entry specifies exactly one type: image, video, document, or link.
mutation EditPost($input: EditPostInput!) {
editPost(input: $input) {
... on PostActionSuccess {
post { id text status dueAt }
}
... on MutationError { message }
}
}
{ "input": { "id": "$POST_ID", "text": "Updated content here" } }
mutation DeletePost {
deletePost(input: { id: "$POST_ID" }) {
... on PostActionSuccess { post { id } }
... on MutationError { message }
}
}
query GetScheduledPosts($orgId: String!) {
posts(input: {
organizationId: $orgId,
filter: { status: [scheduled] },
sort: [{ field: dueAt, direction: asc }]
}) {
edges {
node { id text dueAt channelId }
}
pageInfo { hasNextPage endCursor }
}
}
For more pages, add after: "$endCursor" to input. Page size: 20–50 items.
query GetPostMetrics {
post(input: { id: "$POST_ID" }) {
id text metricsUpdatedAt
metrics { type name value unit }
}
}
Available metric types (varies by network): reactions, reposts, comments, shares, impressions, reach, views, saves, follows, likes. Metrics appear up to ~24 hours after publish.
mutation CreateIdea($input: CreateIdeaInput!) {
createIdea(input: $input) {
... on MutationError { message }
}
}
{
"input": {
"organizationId": "$ORG_ID",
"content": { "title": "Optional title", "text": "Idea content here" }
}
}
Ideas are org-level (not tied to a channel). Promote to a post by using the idea's text in createPost.
Buffer enforces three time windows. On HTTP 429, read retryAfter (seconds) from the response body.
| Plan | 15-min | 24-hr | 30-day |
|---|---|---|---|
| Free | 100 | 100 | 3,000 |
| Essentials | 100 | 250 | 7,500 |
| Team | 100 | 500 | 15,000 |
post field in mutation response → MutationError fired; log data.<mutationName>.message.UNAUTHORIZED → check Authorization: Bearer $BUFFER_API_KEY header is present and token is valid.FORBIDDEN → token lacks the right scope (e.g., posts:write needed for create/edit/delete).metricsUpdatedAt.... on MutationError { message } in every mutation.
评论 (0)
暂无评论,成为第一个评论者吧!