attachments

Move bytes between Gini upload space, external URLs, and workspace files. Used by every attachment / file-upload / file-download flow regardless of the target system (Linear, GitHub, S3, Notion, etc.).

Quality

76%

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/attachments/SKILL.md

Quality

Content

82%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 body is highly actionable with complete executable examples and clearly sequenced recipes, well-structured for navigation, with only minor conciseness redundancy and a dangling ADR reference.

Suggestions

Fold the repeated 'Only https URLs accepted' and 'workspace-relative and escape-protected' notes into a single shared constraints section to reduce redundancy.

Embed explicit validation checkpoints inside the 3-step Linear recipe (e.g., verify PUT status before finalizing) rather than relying only on the Rules section.

Either add the referenced 'chat-file-attachments.md' ADR to references/ or drop the dangling 'See ADR' pointer.

Dimension	Reasoning	Score
Conciseness	Largely lean and purposeful with executable examples and no padding about basic concepts, but repeated phrases ('Only https URLs accepted', 'workspace-relative and escape-protected') and per-script 'Used to/when' prose could be trimmed slightly.	4 / 5
Actionability	Every script ships a complete, copy-paste-ready skill_run call with concrete args and expected output shapes, and the recipe patterns give exact numbered tool invocations covering the common cases.	5 / 5
Workflow Clarity	Multi-step recipes are clearly sequenced (e.g., Prepare → PUT bytes → Finalize) with an error-recovery note (re-run prepare on stale signed URL), but validation is conveyed as rules rather than explicit checkpoints embedded in each workflow.	4 / 5
Progressive Disclosure	Well-organized single-file structure (When to use, four scripts, recipes, rules) with bundle scripts appropriately invoked via skill_run, but the passing 'See ADR chat-file-attachments.md' reference points to a non-existent file in the empty references/ directory.	4 / 5
	Total	17 / 20 Passed

Description

70%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 clearly scopes a distinctive niche (byte movement across Gini uploads, external URLs, and workspace files) with usable trigger terms, but it states only a single generic action and uses passive rather than explicit 'Use when' trigger guidance.

Suggestions

Enumerate the four concrete operations (signed-upload, signed-download, promote-file, materialize) instead of the single 'Move bytes' verb to raise specificity.

Rewrite the trigger as an explicit 'Use when...' clause (e.g., 'Use when an attachment / file-upload / file-download flow needs to move bytes between...').

Add standalone synonyms ('upload', 'download', 'attach') alongside the hyphenated 'file-upload' / 'file-download' forms.

Dimension	Reasoning	Score
Specificity	Names the three byte-movement domains ('Gini upload space, external URLs, and workspace files') and target systems, but the only stated action is the generic 'Move bytes between' rather than enumerating the four distinct operations (upload, download, promote, materialize).	3 / 5
Completeness	Provides a clear 'what' ('Move bytes between...') and a 'when' ('Used by every attachment / file-upload / file-download flow'), but the 'when' is phrased passively rather than as an explicit 'Use when...' clause and could be more specific.	4 / 5
Trigger Term Quality	Includes natural trigger terms ('attachment', 'file-upload', 'file-download') a user would actually say, but misses standalone synonyms like 'upload'/'download'/'send a file' and any file extensions.	4 / 5
Distinctiveness Conflict Risk	The three-place byte-movement model and 'Gini upload space' framing carve a clear niche, though the broad 'file-upload / file-download' phrasing carries minor overlap risk with general file-handling skills.	4 / 5
	Total	15 / 20 Passed

Validation

75%

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 — 12 / 16 Passed

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning
metadata_field	'metadata' should map string keys to string values	Warning
relative_links	Relative link issues: 2 missing	Warning
referenced_paths_exist	Referenced path issues: 2 missing	Warning

	Total	12 / 16 Passed

Repository: Open-Curiosity/gini-agent
Path: skills/attachments/SKILL.md
Commit: 6c5d85e

Reviewed: 3 days 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.