starred/planning-with-files

Fork 0

mirror of https://github.com/OthmanAdi/planning-with-files.git synced 2026-04-25 16:06:02 +03:00

[PR #83] [MERGED] feat: improve skill metadata and description for better discoverability #83

New issue

Closed

opened 2026-03-03 18:50:29 +03:00 by kerem · 0 comments

kerem commented

2026-03-03 18:50:29 +03:00

Owner

📋 Pull Request Information

Original PR: https://github.com/OthmanAdi/planning-with-files/pull/83
Author: @popey
Created: 2/25/2026
Status: ✅ Merged
Merged: 2/25/2026
Merged by: @OthmanAdi

Base: master ← Head: improve/skill-review-optimization

📝 Commits (1)

428728f feat: improve skill metadata and description for better discoverability

📊 Changes

1 file changed (+4 additions, -11 deletions)

View changed files

📝 skills/planning-with-files/SKILL.md (+4 -11)

📄 Description

👋 hullo @OthmanAdi

I ran your skills through a tessl skill review and found some ways to improve discoverability and usability. I hope this is welcome, and helpful.

Summary:

Area	Before	After
Description score	0% (blocked)	100%
Content score	0% (blocked)	100%
allowed-tools format	YAML list (invalid)	comma-separated string (valid)
trigger terms	limited	added "plan out", "break down", "organize", "track progress"

Details:

Fixed allowed-tools from YAML list to string format (was causing validation failure)
Moved version from top-level frontmatter to metadata.version (standard location)
Enriched description with natural trigger terms for better skill matching
No changes to skill behaviour, templates, scripts, or content

These were pretty straightforward changes to bring the skill in line with what performs well against Anthropic's best practices. Full disclosure, I work at @tesslio where we build tooling around this. Not a pitch, just fixes that were not time consuming to make, so I thought I'd offer them as a PR.

Of course, if you'd like to get all your skills to 100%, click here to trigger the evals and iterate some more, otherwise I'm happy to offer more improvements as I find them.

Thanks in advance! Have a great day! 😸

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/OthmanAdi/planning-with-files/pull/83 **Author:** [@popey](https://github.com/popey) **Created:** 2/25/2026 **Status:** ✅ Merged **Merged:** 2/25/2026 **Merged by:** [@OthmanAdi](https://github.com/OthmanAdi) **Base:** `master` ← **Head:** `improve/skill-review-optimization` --- ### 📝 Commits (1) - [`428728f`](https://github.com/OthmanAdi/planning-with-files/commit/428728f5f2e2a127656ecd4c1f99b7d2782e655e) feat: improve skill metadata and description for better discoverability ### 📊 Changes **1 file changed** (+4 additions, -11 deletions) <details> <summary>View changed files</summary> 📝 `skills/planning-with-files/SKILL.md` (+4 -11) </details> ### 📄 Description 👋 hullo @OthmanAdi I ran your skills through a `tessl skill review` and found some ways to improve discoverability and usability. I hope this is welcome, and helpful. Summary: | Area | Before | After | |------|--------|-------| | Description score | 0% (blocked) | 100% | | Content score | 0% (blocked) | 100% | | allowed-tools format | YAML list (invalid) | comma-separated string (valid) | | metadata.version | missing | added (2.10.0) | | trigger terms | limited | added "plan out", "break down", "organize", "track progress" | Details: - Fixed `allowed-tools` from YAML list to string format (was causing validation failure) - Moved `version` from top-level frontmatter to `metadata.version` (standard location) - Enriched description with natural trigger terms for better skill matching - No changes to skill behaviour, templates, scripts, or content These were pretty straightforward changes to bring the skill in line with what performs well against Anthropic's best practices. Full disclosure, I work at @tesslio where we build tooling around this. Not a pitch, just fixes that were not time consuming to make, so I thought I'd offer them as a PR. Of course, if you'd like to get all your skills to 100%, click [here](https://tessl.io/registry/skills/submit) to trigger the evals and iterate some more, otherwise I'm happy to offer more improvements as I find them. Thanks in advance! Have a great day! 😸 --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>

kerem

2026-03-03 18:50:29 +03:00

closed this issue
added the
pull-request
label

No labels

bug

pull-request

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

starred/planning-with-files#83

No description provided.

Rows
Columns