Name: gitea
Rating: 63.2 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

gitea

Gitea integration. Manage Repositories, Organizations, Users. Use when the user wants to interact with Gitea data.

Quality

75%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/gitea/SKILL.md

Quality

Content

68%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is highly actionable with copy-paste commands and a solid connection-state feedback loop, but loses points for an unnecessary introductory concept explanation and a lack of validation checkpoints around the destructive actions it advertises. It is well-structured for a single-file skill though some reference material is inlined.

Suggestions

Trim the opening paragraph explaining what Gitea is (Claude already knows) and the "focus on integration logic rather than auth plumbing" phrasing to improve conciseness.

Add an explicit validate-before-act step for destructive operations (e.g., confirm owner/repo and run a read-only `get-repository` before `delete-repository`) so workflow clarity can exceed the destructive-action cap of 3.

Fix the step numbering (label Step 1a and the referenced "Step 2") or relabel the flow as a flat sequence so readers are not sent to a non-existent step label.

Dimension	Reasoning	Score
Conciseness	Most of the body is lean executable commands and tables, but it opens with a concept explanation Claude already knows ("Gitea is a self-hosted Git repository management solution. It's similar to GitHub…") plus mild fluff ("so you can focus on the integration logic rather than auth plumbing"), placing it at the mostly-efficient score-3 anchor rather than the trimmed score-4.	3 / 5
Actionability	It provides copy-paste-ready commands for every phase ("npm install -g @membranehq/cli@latest", "membrane connection ensure …", "membrane action run <actionId> …", "membrane request CONNECTION_ID /path/to/endpoint") plus a Popular actions key table, fully covering the common cases per the score-5 anchor.	5 / 5
Workflow Clarity	The connection-readiness flow has a real poll/feedback loop (BUILDING → CLIENT_ACTION_REQUIRED → poll again → READY), but destructive operations listed in the actions table ("Delete Repository", "Update Repository") have no validation/verification checkpoint, which caps workflow clarity at 3 per the rubric; step numbering is also loose ("skip to Step 2" and "1b" without a labeled Step 1a/2).	3 / 5
Progressive Disclosure	The body is organized into clear, logically ordered sections (Overview, Working with Gitea, Popular actions, Proxy requests, Best practices) with no nested references — good structure with only minor gaps such as the 20-row actions catalog and proxy-options table being inlined reference material rather than split into a separate file, so it sits at score-4 rather than the cleanly-split score-5.	4 / 5
	Total	15 / 20 Passed

Description

82%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is concise, third-person, and answers both what and when with an explicit "Use when…" clause and a distinct Gitea niche. Its main weakness is the single generic verb "Manage", which undersells the specific capabilities the skill exposes.

Suggestions

Replace or expand the generic verb "Manage" with specific concrete actions (e.g., "Create and list repositories, issues, and pull requests; manage organizations and users") to lift specificity toward 5.

Add a couple of natural synonyms or file/protocol terms users might say (e.g., "Gitea API", "self-hosted Git") to round out trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Quotes "Manage Repositories, Organizations, Users" name three concrete domain objects but rely on a single generic verb ("Manage"), so actions are minimal rather than a comprehensive set; fits the score-3 anchor (names domain and 1-2 concrete actions) and is below 4 which requires several distinct specific actions.	3 / 5
Completeness	It states what ("Gitea integration. Manage Repositories, Organizations, Users.") and when ("Use when the user wants to interact with Gitea data.") with an explicit "Use when…" trigger clause, matching the score-5 anchor that requires both answered concretely.	5 / 5
Trigger Term Quality	Natural terms present include "Gitea", "interact with Gitea data", and "Repositories, Organizations, Users" — good coverage a user would say — but it lacks synonyms or file extensions, so it stops short of the comprehensive score-5 anchor.	4 / 5
Distinctiveness Conflict Risk	"Gitea integration" carves out a clear, app-specific niche with distinct triggers (Gitea data) and minimal overlap risk with other skills, matching the score-5 anchor.	5 / 5
	Total	17 / 20 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: membranedev/application-skills
Path: skills/gitea/SKILL.md
Commit: f484c82

Reviewed: ~20 hours ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.