gitea-wiki
Manage Gitea wiki pages. Use when working with wiki content, creating documentation, or updating wiki pages.
What this skill does
# Gitea Wiki Manager
## Overview
Manage Gitea wiki pages using MCP tools. Wiki content is base64 encoded - use shell commands to decode/encode, avoiding large base64 strings in LLM context.
## MCP Tools Reference
### mcp__gitea__list_wiki_pages
List all wiki pages in a repository.
**Parameters:**
- `owner` (required): repository owner
- `repo` (required): repository name
**Response:** Array of page objects with `title`, `sub_url`
---
### mcp__gitea__get_wiki_page
Get wiki page content and metadata.
**Parameters:**
- `owner` (required): repository owner
- `repo` (required): repository name
- `pageName` (required): wiki page name
**Response:**
```json
{
"title": "Home",
"sub_url": "Home",
"content_base64": "IyBIb21lCg==", // <-- base64 encoded content
"commit_count": 5,
"last_commit": {...}
}
```
---
### mcp__gitea__create_wiki_page
Create a new wiki page.
**Parameters:**
- `owner` (required): repository owner
- `repo` (required): repository name
- `title` (required): page title
- `content_base64` (required): page content as base64
- `message` (optional): commit message
---
### mcp__gitea__update_wiki_page
Update an existing wiki page.
**Parameters:**
- `owner` (required): repository owner
- `repo` (required): repository name
- `pageName` (required): current page name
- `content_base64` (required): new content as base64
- `title` (optional): new page title
- `message` (optional): commit message
---
### mcp__gitea__delete_wiki_page
Delete a wiki page.
**Parameters:**
- `owner` (required): repository owner
- `repo` (required): repository name
- `pageName` (required): page name to delete
---
### mcp__gitea__get_wiki_revisions
Get revision history of a wiki page.
**Parameters:**
- `owner` (required): repository owner
- `repo` (required): repository name
- `pageName` (required): wiki page name
## Workflows
### Reading a Wiki Page
```
Step 1: Call MCP tool
mcp__gitea__get_wiki_page(owner="user", repo="myrepo", pageName="Home")
Step 2: Response contains content_base64 field
Extract the base64 string from response
Step 3: Decode using Bash (NOT in LLM context)
echo "<content_base64_value>" | base64 -d > /tmp/wiki-page.md
Step 4: Read decoded file
Use Read tool on /tmp/wiki-page.md
```
### Creating a Wiki Page
```
Step 1: Write content to temp file
Use Write tool to create /tmp/new-page.md with content
Step 2: Encode to base64 using Bash
base64 < /tmp/new-page.md | tr -d '\n'
Step 3: Call MCP tool with base64 output
mcp__gitea__create_wiki_page(
owner="user",
repo="myrepo",
title="API Docs",
content_base64="<output_from_step_2>"
)
```
### Updating a Wiki Page
```
Step 1: Get current content
mcp__gitea__get_wiki_page(owner="user", repo="myrepo", pageName="Home")
Step 2: Decode to temp file
echo "<content_base64>" | base64 -d > /tmp/edit-page.md
Step 3: Edit the temp file
Use Edit tool on /tmp/edit-page.md
Step 4: Re-encode
base64 < /tmp/edit-page.md | tr -d '\n'
Step 5: Call MCP update
mcp__gitea__update_wiki_page(
owner="user",
repo="myrepo",
pageName="Home",
content_base64="<output_from_step_4>"
)
```
## Guidelines
### Do
- Use temp files (`/tmp/wiki-*.md`) for content manipulation
- Use `tr -d '\n'` when encoding - API requires no line breaks
- Clean up temp files after operations
- Decode content via Bash before reading
### Don't
- Include raw base64 content in LLM responses
- Skip the decode step when reading wiki pages
- Forget to encode content before creating/updating pages
- Leave temp files after operations complete
## Examples
### Example: Read Home page
```
1. mcp__gitea__get_wiki_page(owner="acme", repo="docs", pageName="Home")
→ Response: {"content_base64": "IyBXZWxjb21l..."}
2. Bash: echo "IyBXZWxjb21l..." | base64 -d > /tmp/wiki-home.md
3. Read: /tmp/wiki-home.md
→ Shows: "# Welcome..."
```
### Example: Create new page
```
1. Write /tmp/new-wiki.md:
# Installation
Run `npm install`
2. Bash: base64 < /tmp/new-wiki.md | tr -d '\n'
→ Output: IyBJbnN0YWxsYXRpb24KUnVuIGBucG0gaW5zdGFsbGA=
3. mcp__gitea__create_wiki_page(
owner="acme",
repo="docs",
title="Installation",
content_base64="IyBJbnN0YWxsYXRpb24KUnVuIGBucG0gaW5zdGFsbGA="
)
```
Related in Writing & Docs
jax-development
IncludedUse this skill when the user is writing, debugging, profiling, refactoring, reviewing, benchmarking, parallelising, exporting, or explaining JAX code, or when they mention JAX, jax.numpy, jit, grad, value_and_grad, vmap, scan, lax, random keys, pytrees, jax.Array, sharding, Mesh, PartitionSpec, NamedSharding, pmap, shard_map, Pallas, XLA, StableHLO, checkify, profiler, or the JAX repo. It helps turn NumPy or PyTorch-style code into pure functional JAX, fix tracer/control-flow/shape/PRNG bugs, remove recompiles and host-device syncs, choose transforms and sharding strategies, inspect jaxpr/lowering/IR, and benchmark compiled code correctly.
nature-article-writer
IncludedDrafts, rewrites, diagnostically critiques, and style-calibrates primary research manuscripts for Nature and Nature Portfolio journals. Use when the user wants a Nature-style title, summary paragraph or abstract, introduction, results, discussion, methods, figure legends, presubmission enquiry, cover letter, reviewer response, or when a scientific draft sounds generic, jargon-heavy, structurally weak, or AI-ish and needs precise, broad-reader-friendly prose without inventing data, analyses, or references. Best for primary research articles and letters rather than reviews or press releases unless explicitly adapting one.
deckrd
IncludedDocument-driven framework that derives requirements, specifications, implementation plans, and executable tasks from goals through structured AI dialogue. Use when user says "write requirements", "create spec", "plan implementation", "derive tasks", "structure this feature", "break down into tasks", or "document this module". Also use for reverse engineering existing code into docs (/deckrd rev). Do NOT use for direct code writing — use /deckrd-coder after tasks are generated. Do NOT use when the user only wants to run or fix existing code without planning.
clinical-decision-support
IncludedGenerate professional clinical decision support (CDS) documents for pharmaceutical and clinical research settings, including patient cohort analyses (biomarker-stratified with outcomes) and treatment recommendation reports (evidence-based guidelines with decision algorithms). Supports GRADE evidence grading, statistical analysis (hazard ratios, survival curves, waterfall plots), biomarker integration, and regulatory compliance. Outputs publication-ready LaTeX/PDF format optimized for drug development, clinical research, and evidence synthesis.
handling-sf-data
IncludedSalesforce data operations with 130-point scoring. Use this skill to create, update, delete, bulk import/export, generate test data, and clean up org records using sf CLI and anonymous Apex. TRIGGER when: user creates test data, performs bulk import/export, uses sf data CLI commands, needs data factory patterns for Apex tests, or needs to seed/clean records in a Salesforce org. DO NOT TRIGGER when: SOQL query writing only (use querying-soql), Apex test execution (use running-apex-tests), or metadata deployment (use deploying-metadata).
accelint-ac-to-playwright
IncludedConvert and validate acceptance criteria for Playwright test automation. Use when user asks to (1) review/evaluate/check if AC are ready for automation, (2) assess if AC can be converted as-is, (3) validate AC quality for Playwright, (4) turn AC into tests, (5) generate tests from acceptance criteria, (6) convert .md bullets or .feature Gherkin files to Playwright specs, (7) create test automation from requirements. Handles both bullet-style markdown and Gherkin syntax with JSON test plan generation and validation.