New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Gitea Workflow

by jwynia in jwynia/agent-skills

Orchestrate agile development workflows for Gitea repositories using the tea CLI.

MITAuto-check passedProduct & Project Management

Install Gitea Workflow

skills CLI
$ npx skills add jwynia/agent-skills --skill gitea-workflow -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install jwynia/agent-skills gitea-workflow --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/jwynia/agent-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/tech/development/workflow/gitea-workflow .claude/skills/gitea-workflow && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
gitea-workflow
GitHub stars
169
Token cost
~3.8k tokens
SKILL.md length
921 words
Files
25 (incl. scripts, references, assets)
Skills in repo
111
Repo updated
First seen
Licence
MIT

At a glance

Orchestrate agile development workflows for Gitea repositories using the tea CLI.

  • Works in 8 steps: Sync Reality → Select Task → Implement → …
  • Working with Gitea-hosted repos and asking to run the workflow
  • SKILL.md covers When to Use This Skill, Prerequisites, Workflow Types Overview and State Detection, plus 8 more sections
  • Calls git; needs GITEA_TOKEN

What it does

Gitea Workflow is an agent skill from jwynia/agent-skills. Orchestrate agile development workflows for Gitea repositories using the tea CLI. Use when working with Gitea-hosted repos and asking to 'run the workflow', 'continue working', 'what's next', 'complete the task cycle', 'start my day', 'end the sprint', 'implement the next task', or wanting guided step-by-step development assistance. Keywords: workflow, orchestrate, agile, task cycle, sprint, daily, implement, review, PR, standup, retrospective, gitea, tea.

Its SKILL.md is about 3.8k tokens, which your agent loads only when the skill is triggered. The skill folder holds 27 other files, including scripts, reference files and assets (for example `assets/state-matrix.md`, `assets/workflow-diagrams.md` and `references/checkpoint-handling.md`). Compatibility notes: Requires git, Gitea Tea CLI (tea), and a context network with backlog structure.

It sits in Product & Project Management, covering Pull requests, Meeting notes and agendas and Retrospectives. It works with Git. The licence is MIT.

When your agent uses it

  • Working with Gitea-hosted repos and asking to run the workflow
  • Continue working
  • Complete the task cycle
  • Implement the next task

Example prompts

  • “run the workflow”
  • “continue working”
  • “s next”
  • “/gitea-workflow”

Requirements

  • A credential in GITEA_TOKEN
  • Compatibility (from SKILL.md): Requires git, Gitea Tea CLI (tea), and a context network with backlog structure.

Workflow steps

8 steps, taken from the step headings in SKILL.md.

  1. Sync Reality
  2. Select Task
  3. Implement
  4. Review
  5. Apply Recommendations (Conditional)
  6. Prepare PR
  7. Complete PR
  8. Update Backlog and Project Status

What it can do on your machine

Read from SKILL.md and the folder at commit e02ec7e. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Ships 1 file in scripts/, which the agent can run.

    Shell commands in SKILL.md call:

    • git

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names these keys or tokens, usually read from environment variables:

    • GITEA_TOKEN

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

  • Compatibility

    Requires git, Gitea Tea CLI (tea), and a context network with backlog structure.

    From compatibility in the SKILL.md frontmatter.

Context cost

Gitea Workflow loads about 3.8k tokens when it runs, and up to ~30k if it reads all its reference files. Until then it costs about 119 tokens; SKILL.md has 921 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~119
When it runs · the whole SKILL.md, loaded when a task matches
~3.8k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~30k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.

SKILL.md

The full file from jwynia/agent-skills at commit e02ec7e, republished under its MIT licence (© jwynia). 921 words, ~3,788 tokens.

Download SKILL.mdSave it as .claude/skills/gitea-workflow/SKILL.md (or your agent's skills folder). This skill also uses 24 other files; get the full folder from GitHub.
name
gitea-workflow
description
Orchestrate agile development workflows for Gitea repositories using the tea CLI. Use when working with Gitea-hosted repos and asking to 'run the workflow', 'continue working', 'what's next', 'complete the task cycle', 'start my day', 'end the sprint', 'implement the next task', or wanting guided step-by-step development assistance. Keywords: workflow, orchestrate, agile, task cycle, sprint, daily, implement, review, PR, standup, retrospective, gitea, tea.
compatibility
Requires git, Gitea Tea CLI (tea), and a context network with backlog structure.
license
MIT
metadata.author
agent-skills
metadata.version
1.0
metadata.type
orchestrator
metadata.mode
generative
metadata.domain
agile-software

Gitea Workflow Orchestrator

A skill that guides agents through structured agile development workflows for Gitea repositories by intelligently invoking commands in sequence. Uses checkpoint-based flow control to auto-progress between steps while pausing at key decision points.

When to Use This Skill

Use this skill when:

  • Working with a Gitea-hosted repository
  • Starting work for the day ("run morning standup", "start my day")
  • Working on a task ("implement next task", "continue working")
  • Completing a development cycle ("finish this task", "prepare PR")
  • Running sprint ceremonies ("start sprint", "end sprint", "retrospective")
  • Resuming interrupted work ("what's next", "where was I")

Do NOT use this skill when:

  • Working with GitHub repositories (use agile-workflow instead)
  • Running a single specific command (use that command directly)
  • Just checking status (use /status directly)
  • Only doing code review without full cycle (use /review-code directly)
  • Researching or planning without implementation

Prerequisites

Before using this skill:

  • Git repository initialized with worktree support
  • Gitea Tea CLI installed and authenticated (tea login)
  • Context network with backlog structure at context-network/backlog/
  • Task status files at context-network/backlog/by-status/*.md
  • GITEA_URL environment variable set (or configured in tea)
  • GITEA_TOKEN environment variable set for API scripts

Workflow Types Overview

WORKFLOW TYPES
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

TASK CYCLE (Primary)     DAILY                SPRINT
──────────────────────   ──────────────────   ──────────────────
sync                     Morning:             Start:
  ↓                        sync --last 1d       sync --all
next → [CHECKPOINT]        status --brief       groom --all
  ↓                        groom --ready        plan sprint-goals
implement                                       status
  ↓                      Evening:
[CHECKPOINT]               checklist          End:
  ↓                        discovery            sync --sprint
review-code                sync --last 1d       retrospective
review-tests                                    audit --sprint
  ↓                                             maintenance --deep
[CHECKPOINT]
  ↓
apply-recommendations (if issues)
  ↓
pr-prep → [CHECKPOINT]
  ↓
pr-complete
  ↓
update-backlog & status
  ↓
END
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

State Detection

The skill determines current workflow state automatically. No manual tracking needed.

Detection Signals
SignalHow to CheckIndicates
Worktree existsgit worktree listTask in progress
Task branch activegit branch --show-current matches task/*Active implementation
Uncommitted changesgit status --porcelainActive coding
PR existstea pulls list --state openIn review
PR mergedtea pulls + check stateReady for cleanup
State Matrix
STATE DETECTION LOGIC
─────────────────────────────────────────────────────────────
Check                           → State           → Next Step
─────────────────────────────────────────────────────────────
No worktree, no in-progress     → IDLE            → sync, next
Worktree exists, uncommitted    → IMPLEMENTING    → continue implement
Worktree exists, all committed  → READY_REVIEW    → review-code
PR open, CI pending             → AWAITING_CI     → wait or address
PR open, CI pass                → READY_MERGE     → pr-complete
PR merged, worktree exists      → CLEANUP         → pr-complete
─────────────────────────────────────────────────────────────

For detailed detection algorithms, see references/state-detection.md.

Invocation Patterns

bash
# Auto-detect state and continue from where you are
/gitea-workflow

# Start specific workflow phase
/gitea-workflow --phase task-cycle
/gitea-workflow --phase daily-morning
/gitea-workflow --phase daily-evening
/gitea-workflow --phase sprint-start
/gitea-workflow --phase sprint-end

# Resume work on specific task
/gitea-workflow --task TASK-123

# Preview what would happen without executing
/gitea-workflow --dry-run

Task Cycle Phase

The primary workflow for completing a single task from selection to merge.

Step 1: Sync Reality

Ensure context network matches actual project state.

Run: sync --last 1d --dry-run
Purpose: Detect drift between documented and actual state
Output: Sync report showing completions, partial work, divergences
Step 2: Select Task

Identify the next task to work on.

Run: next
Purpose: Find highest priority ready task
Output: Task ID, title, branch name suggestion

CHECKPOINT: TASK_SELECTED

  • Pause to confirm task selection
  • User can accept or choose different task
  • On accept: continue to implementation
Step 3: Implement

Test-driven development in isolated worktree.

Run: implement [TASK-ID]
Purpose: Create worktree, write tests first, implement, verify
Output: Working implementation with passing tests

CHECKPOINT: IMPL_COMPLETE

  • Pause after implementation completes
  • Show test results and coverage
  • On success: continue to review
Step 4: Review

Quality validation of implementation.

Run: review-code --uncommitted
Run: review-tests --uncommitted
Purpose: Identify quality issues, security concerns, test gaps
Output: Review reports with issues and recommendations

CHECKPOINT: REVIEWS_DONE

  • Display combined review results
  • If critical issues: must address before continuing
  • If no issues: auto-continue to PR prep
  • User decides: apply recommendations now or defer
Step 5: Apply Recommendations (Conditional)

Address review findings intelligently.

Run: apply-recommendations [review-output]
Purpose: Apply quick fixes now, defer complex changes to tasks
Output: Applied fixes + created follow-up tasks
Step 6: Prepare PR

Create pull request with full documentation.

Run: pr-prep
Purpose: Validate, document, and create PR
Output: PR created with description, tests verified

CHECKPOINT: PR_CREATED

  • Display PR URL and CI status
  • Wait for CI checks to complete (verify manually or via API script)
  • On CI pass + approval: continue to merge
  • On CI fail: stop, address issues
Step 7: Complete PR

Merge and cleanup.

Run: pr-complete [PR-NUMBER]
Purpose: Merge PR, delete branch, remove worktree, update status
Output: Task marked complete, cleanup done
Step 8: Update Backlog and Project Status

Persist progress to source-of-truth documentation.

Run: Part of pr-complete (Phase 6)
Purpose: Update epic file (task → complete), unblock dependents, update project status
Output: Backlog and project status reflect actual progress

Why this step matters: Without it, completed tasks remain marked "ready" in backlog files and project status stays stale. Internal tracking files are session-scoped; the backlog and status files are the persistent source of truth.

For detailed task-cycle instructions, see references/phases/task-cycle.md.

Daily Phase

Quick sequences for start and end of workday.

Morning Standup (~5 min)
Run sequence:
1. sync --last 1d --dry-run   # What actually happened yesterday
2. status --brief --sprint    # Current sprint health
3. groom --ready-only         # What's ready to work on

Output: Clear picture of today's priorities
Evening Wrap-up (~10 min)
Run sequence:
1. checklist                  # Ensure nothing lost
2. discovery                  # Capture learnings
3. sync --last 1d            # Update task statuses

Output: Knowledge preserved, state synchronized

For detailed daily instructions, see references/phases/daily.md.

Sprint Phase

Ceremonies for sprint boundaries.

Sprint Start (~60 min)
Run sequence:
1. sync --all                 # Full reality alignment
2. groom --all               # Comprehensive grooming
3. plan sprint-goals         # Architecture and goals
4. status --detailed         # Baseline metrics

Output: Sprint plan with groomed, ready backlog
Sprint End (~90 min)
Run sequence:
1. sync --sprint             # Final sprint sync
2. retrospective             # Capture learnings
3. audit --scope sprint      # Quality review
4. status --metrics          # Sprint metrics
5. maintenance --deep        # Context network cleanup

Output: Sprint closed, learnings captured, ready for next

For detailed sprint instructions, see references/phases/sprint.md.

Checkpoint Handling

Checkpoints are pauses for human decision-making.

Checkpoint Behavior

At each checkpoint:

  1. Summarize what just completed
  2. Show key results and any issues
  3. Present next steps
  4. Wait for user input
Show full SKILL.md (357 more words)Show less
Checkpoint Responses
ResponseAction
"continue" / "proceed" / "yes"Move to next step
"stop" / "pause"Save state, exit workflow
"back"Re-run previous step
"skip"Skip current step (use cautiously)
Custom inputMay adjust next step parameters
Auto-Continue Conditions

Some checkpoints can auto-continue when conditions are met:

CheckpointAuto-Continue If
IMPL_COMPLETEAll tests pass, build succeeds
REVIEWS_DONENo critical or high severity issues
PR_CREATEDCI passes (verified via API), required approvals obtained

For detailed checkpoint handling, see references/checkpoint-handling.md.

Command Reference

Each workflow step uses embedded command instructions:

CommandReferencePurpose
syncreferences/commands/sync.mdReality synchronization
groomreferences/commands/groom.mdTask refinement
nextreferences/commands/next.mdTask selection
implementreferences/commands/implement.mdTDD implementation
review-codereferences/commands/review-code.mdCode quality review
review-testsreferences/commands/review-tests.mdTest quality review
apply-recommendationsreferences/commands/apply-recommendations.mdTriage and apply fixes
pr-prepreferences/commands/pr-prep.mdPR creation
pr-completereferences/commands/pr-complete.mdPR merge and cleanup
discoveryreferences/commands/discovery.mdLearning capture
retrospectivereferences/commands/retrospective.mdPost-work analysis
maintenancereferences/commands/maintenance.mdContext network cleanup

Example: Complete Task Cycle

Scenario: Start of day, implement next available task

Invocation:

/gitea-workflow --phase task-cycle

Flow:

Agent: Detecting current state...
       No worktree found, checking ready tasks...

Agent: Running sync --last 1d --dry-run
       [Sync output: 0 tasks completed but undocumented]

Agent: Running next
       Found: TASK-042 - Add user preferences endpoint
       Priority: High | Size: Small | Branch: task/TASK-042-preferences

       ╔═══════════════════════════════════════════╗
       ║  CHECKPOINT: Task Selection               ║
       ╠═══════════════════════════════════════════╣
       ║  Selected: TASK-042                       ║
       ║  Proceed with implementation?             ║
       ║                                           ║
       ║  [continue] [stop] [other task]           ║
       ╚═══════════════════════════════════════════╝

User: continue

Agent: Creating worktree at .worktrees/TASK-042/
       Running implement TASK-042
       [Implementation proceeds with TDD...]

       Tests: 12 passing
       Coverage: 87%
       Build: Success

       ╔═══════════════════════════════════════════╗
       ║  CHECKPOINT: Implementation Complete      ║
       ╠═══════════════════════════════════════════╣
       ║  All tests passing, ready for review      ║
       ║  Proceed to code review?                  ║
       ║                                           ║
       ║  [continue] [stop]                        ║
       ╚═══════════════════════════════════════════╝

[Flow continues through review, PR, merge...]

Gitea-Specific Notes

CI Status Checking

Gitea uses external CI systems (Drone, Woodpecker, Jenkins, etc.). To check CI status:

  1. Via API Script: Use scripts/gitea-ci-status.sh to query commit statuses
  2. Manual Verification: Check your CI dashboard directly
  3. PR Mergeability: Check if PR shows as mergeable in Gitea UI
Tea CLI Command Reference
OperationTea CLI Command
List open PRstea pulls list --state open
Create PRtea pulls create --title "..." --description "..." --base main --head branch
View PRtea pulls
Merge PR (squash)tea pulls merge --style squash
Merge PR (merge)tea pulls merge --style merge
Merge PR (rebase)tea pulls merge --style rebase
Approve PRtea pulls approve
List issuestea issues list
API Scripts

For operations not available in the tea CLI, use the provided API scripts:

  • scripts/gitea-ci-status.sh - Check CI status via Gitea API
  • scripts/gitea-pr-checks.sh - Get PR review/approval status

Limitations

  • Requires context network with specific backlog structure
  • Gitea-centric (uses tea CLI for PR operations)
  • Single-task focus (parallel task work not orchestrated)
  • Manual CI verification may be needed (Gitea uses external CI)
  • Some features depend on Gitea version and configuration
  • skill-maker - Create new skills following agentskills.io spec
  • research-workflow - For research tasks before implementation
  • gitea-coordinator - For multi-task orchestration with Gitea

© jwynia, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 24 other files (scripts, references, assets) in skills/tech/development/workflow/gitea-workflow of jwynia/agent-skills.

  • SKILL.md
  • assets/state-matrix.md
  • assets/workflow-diagrams.md
  • references/checkpoint-handling.md
  • references/commands/apply-recommendations.md
  • references/commands/discovery.md
  • references/commands/groom.md
  • references/commands/implement.md
  • references/commands/maintenance.md
  • references/commands/next.md
  • references/commands/pr-complete.md
  • references/commands/pr-prep.md
  • references/commands/retrospective.md
  • references/commands/review-code.md
  • references/commands/review-tests.md
  • references/commands/status.md
  • references/commands/sync.md
  • references/phases
  • … and 7 more

Open the folder on GitHubat commit e02ec7e

Compare with similar skills

Gitea Workflow next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Gitea Workflow compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Gitea Workflow this skilljwynia/agent-skills169—~3.8kAutomated safety check: PassMIT
Weekly Engineering Retrogarrytan/gstack136k—~2.4kAutomated safety check: PassMIT
Badstephenleo/bmad-autonomous-development107—~7.7kAutomated safety check: PassMIT
Daily Meeting Updatedavila7/claude-code-templates32k2 repos~3kAutomated safety check: PassMIT
Engineering RetroMathews-Tom/armory328—~2.3kAutomated safety check: PassMIT
Acceptance Criteria Checkshopsys/shopsys350—~1kAutomated safety check: PassCustom licence

Similar skills

  • Weekly Engineering Retro

    garrytan/gstack

    Builds a weekly engineering retrospective from git history: commit counts, per-person contributions, work patterns and code quality numbers over a chosen window.

    136k GitHub stars~2.4k tokensUpdated today
    Product & Project ManagementAuto-check passed

  • Bad

    stephenleo/bmad-autonomous-development

    BMad Autonomous Development — orchestrates parallel story implementation pipelines.

    107 GitHub stars~7.7k tokensUpdated 5 mo ago
    Agent WorkflowsAuto-check passed

  • Daily Meeting Update

    davila7/claude-code-templates

    Interactive daily standup/meeting update generator. An agent skill from davila7/claude-code-templates.

    32k GitHub starsUsed in 2 repos~3k tokens
    Product & Project ManagementAuto-check passed

  • Engineering Retro

    Mathews-Tom/armory

    Git-based engineering retrospective analyzing commits, PRs, and velocity over configurable windows with monorepo path scoping.

    328 GitHub stars~2.3k tokensUpdated 3 days ago
    Product & Project ManagementAuto-check passed

  • Acceptance Criteria Check

    shopsys/shopsys

    Checks a pull request against the acceptance criteria of its Jira issue by driving the deployed review environment with Playwright.

    350 GitHub stars~1k tokensUpdated today
    Product & Project ManagementAuto-check passed

  • Dough Story Wrap Up

    terryyin/lizard

    Closes one completed feature story, bounded retrospective correction, or context-only planless execution using available execution context.

    2.6k GitHub stars~4.3k tokensUpdated 2 days ago
    Product & Project ManagementAuto-check passed

More from jwynia/agent-skills

All 111 skills in this repo

  • Devcontainer

    jwynia/agent-skills

    Diagnose devcontainer configuration problems and guide development environment setup.

    169 GitHub stars~1.2k tokensUpdated 7 mo ago
    Auto-check: notes

  • Frontend Design

    jwynia/agent-skills

    Create distinctive, production-grade frontend interfaces with high design quality.

    169 GitHub stars~3.2k tokensUpdated 7 mo ago
    Auto-check passed

  • Godot Asset Generator

    jwynia/agent-skills

    Generate game assets using AI image generation APIs (DALL-E, Replicate, fal.ai) and prepare them for Godot.

    169 GitHub stars~3.8k tokensUpdated 7 mo ago
    Auto-check passed

  • Mastra Hono

    jwynia/agent-skills

    Develop AI agents, tools, and workflows with Mastra v1 Beta and Hono servers.

    169 GitHub stars~2.9k tokensUpdated 7 mo ago
    Auto-check passed

  • PPTX Generator

    jwynia/agent-skills

    Create and manipulate PowerPoint PPTX files programmatically.

    169 GitHub stars~3.1k tokensUpdated 7 mo ago
    Auto-check passed

  • React Pwa

    jwynia/agent-skills

    Build Progressive Web Apps with React and Vite. An agent skill from jwynia/agent-skills.

    169 GitHub stars~4.4k tokensUpdated 7 mo ago
    Auto-check passed

Works with

Categories

Questions about Gitea Workflow

What does Gitea Workflow do?

Orchestrate agile development workflows for Gitea repositories using the tea CLI. Gitea Workflow is an agent skill from jwynia/agent-skills. Orchestrate agile development workflows for Gitea repositories using the tea CLI.

When should I use Gitea Workflow?

Gitea Workflow fits situations like: working with Gitea-hosted repos and asking to run the workflow; continue working; complete the task cycle; implement the next task.

How do I install Gitea Workflow in Claude Code?

Run `npx skills add jwynia/agent-skills --skill gitea-workflow -a claude-code`. Or copy the skill folder (skills/tech/development/workflow/gitea-workflow in jwynia/agent-skills) into .claude/skills/gitea-workflow in your project. Claude Code loads it when a task matches its description.

How do I install Gitea Workflow in Codex?

Run `npx skills add jwynia/agent-skills --skill gitea-workflow -a codex`. Or copy the skill folder (skills/tech/development/workflow/gitea-workflow in jwynia/agent-skills) into .agents/skills/gitea-workflow in your project. Codex loads it when a task matches its description.

Can I use Gitea Workflow in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add jwynia/agent-skills --skill gitea-workflow -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/gitea-workflow, .gemini/skills/gitea-workflow, .github/skills/gitea-workflow and .opencode/skills/gitea-workflow in your project.

What does Gitea Workflow need to run?

Going by SKILL.md and its folder, Gitea Workflow needs the command-line tools its instructions call (git) and credentials named GITEA_TOKEN. Our summary lists: A credential in GITEA_TOKEN. Compatibility (from SKILL.md): Requires git, Gitea Tea CLI (tea), and a context network with backlog structure..

Does Gitea Workflow access the network?

SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Gitea Workflow safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Gitea Workflow use?

Gitea Workflow is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Gitea Workflow use?

About 3.8k tokens (SKILL.md is roughly 15k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 26k tokens, read only when the agent opens those files.

What are the alternatives to Gitea Workflow?

Skills that share tags, products or a category with Gitea Workflow: Weekly Engineering Retro (garrytan/gstack, 136k stars), Bad (stephenleo/bmad-autonomous-development, 107 stars), Daily Meeting Update (davila7/claude-code-templates, 32k stars) and Engineering Retro (Mathews-Tom/armory, 328 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Gitea Workflow?

jwynia (a GitHub user) maintains it in jwynia/agent-skills, which has 169 GitHub stars. The repository holds 111 skills in this directory. The repository was last updated on February 24, 2026.

Source: jwynia/agent-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.