메뉴
Interact with the Pagecord API for a blog. Use when the user wants to inspect posts or pages, publish content through the API, check API connectivity, or inspect the home page.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | pagecord |
| description | Interact with the Pagecord API for a blog. Use when the user wants to inspect posts or pages, publish content through the API, check API connectivity, or inspect the home page. |
| allowed-tools | Bash, Read, Glob |
Use the public API at https://api.pagecord.com.
/Users/olly/dev/pagecord/.env.PAGECORD_API_KEY for the default blog.PAGECORD_{BLOG}_API_KEY with the subdomain uppercased and hyphens replaced by underscores.Settings > API.Authorization: Bearer {API_KEY}. Never print the raw key.Use GET /posts or GET /pages. Status may be published, draft, or all.
For all, make one published request and one ?status=draft request, then combine results. Paginate using page=N or Link headers until exhausted. Display a concise table with token, slug, title, status, and published date.
Use GET /posts/{token} or GET /pages/{token}. Show token, title, slug, status, published date, canonical URL, tags, hidden state, locale, created/updated dates, and a short content preview.
When publishing a local markdown file as a post:
published: true to status: published and published: false to status: draft.# Heading..md links to /slug format.POST /posts with the full markdown content and content_format=markdown.Preserve front matter when sending markdown to the API.
Use GET /home_page. Show all fields. If the response is 404, report that no home page is set.
Check API connectivity by fetching page and post counts from X-Total-Count, then report the key env var in use, published post count, and page count.
Interact with the Fizzy tracker for Pagecord work. Use when the user asks to list, create, update, move, close, comment on, or inspect Fizzy cards, boards, tags, users, steps, pins, or notifications.
Apply core Ruby on Rails best practices for architecture, naming, RESTful routing, authorisation, safety, and maintainability. Use by default for Rails coding, refactoring, debugging, feature implementation, migrations, controller/model changes, and code review tasks so baseline standards stay consistent.
Run the local CI sequence for this repo. Use when the user asks to run CI, verify a branch before push, or check code quality with the full local pipeline.
Review Ruby and Rails code as a principal engineer. Use when the user asks for a code review, PR review, diff review, or wants risks, regressions, security issues, Rails idiom problems, UI state issues, or test gaps identified before merging.
Interact with Cloudflare R2 buckets used by Pagecord. Use when the user wants to list objects, inspect bucket stats, fetch files, or check backup integrity in R2.
Investigate and fix a Sentry issue in this codebase. Use when the user provides a Sentry issue URL or ID and wants diagnosis, a fix, verification, or a PR.