feat: improve github-explorer skill score (90% → 94%)#2
Open
rohan-tessl wants to merge 1 commit intoblessonism:mainfrom
Open
feat: improve github-explorer skill score (90% → 94%)#2rohan-tessl wants to merge 1 commit intoblessonism:mainfrom
rohan-tessl wants to merge 1 commit intoblessonism:mainfrom
Conversation
Hey @blessonism 👋 I ran your skills through `tessl skill review` at work and found some targeted improvements. Here's the full before/after: | Skill | Before | After | Change | |-------|--------|-------|--------| | github-explorer | 90% | 94% | +4% | <details> <summary>Changes summary</summary> - **Fixed frontmatter description format**: Converted chevron (`>`) syntax to standard quoted string for better parser compatibility - **Improved progressive disclosure**: Extracted the detailed output template, formatting rules, and self-check checklist into `references/output-template.md` — keeps the main SKILL.md scannable while preserving all report structure - **Extracted search-layer patterns**: Moved the full intent-based search command table and intent type reference to `references/search-patterns.md`, with a concise default command + link in the main skill - **Fixed source table contradiction**: The GitHub Repo row recommended `web_fetch`, contradicting the mandatory rule above it to use GitHub API — corrected to reference the API section - **Reduced redundancy in Execution Notes**: Removed duplicated search-layer and content-extract descriptions already covered in Phase 2 - **Trimmed Dependencies section**: Consolidated the full table into a compact two-line summary (tools already appear in the workflow) **Net result**: SKILL.md went from 221 lines → 92 lines while all content is preserved in referenced files. Content score improved from 77% → 85% (progressive disclosure: 2/3 → 3/3). </details> Honest disclosure — I work at @tesslio where we build tooling around skills like these. Not a pitch - just saw room for improvement and wanted to contribute. Want to self-improve your skills? Just point your agent (Claude Code, Codex, etc.) at [this Tessl guide](https://docs.tessl.io/evaluate/optimize-a-skill-using-best-practices) and ask it to optimize your skill. Ping me - [@rohan-tessl](https://github.com/rohan-tessl) - if you hit any snags. Thanks in advance 🙏
📝 WalkthroughWalkthroughDocumentation consolidation: SKILL.md is simplified by removing inline specifications for output templates and search-layer command patterns, externalizing these details to two new reference files ( Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes Poem
🚥 Pre-merge checks | ✅ 2 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (2 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment Warning |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
🧹 Nitpick comments (2)
references/output-template.md (1)
22-90: Consider adding Telegram spacing pattern in the template.The template includes sections that will contain lists (e.g., "精选 Issue", "竞品对比", "社区声量"), but doesn't demonstrate where to insert the U+2800 braille blank for Telegram rendering. Users might forget to add it when filling in the template.
♻️ Suggested template enhancement
Add a comment or example showing where to insert the braille blank:
**🔥 精选 Issue** -{Top 3-5 高质量 Issue，每条包含标题、链接、核心讨论点。如无高质量 Issue 则注明。} +- [`#123` Issue标题](链接): 核心讨论点 +- [`#456` Issue标题](链接): 核心讨论点 +- [`#789` Issue标题](链接): 核心讨论点 + +⠀ **✅ 适用场景**This provides a concrete example of the Telegram spacing pattern in context.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@references/output-template.md` around lines 22 - 90, Add an explicit example/comment in the template showing where to insert the U+2800 braille blank for Telegram spacing so contributors won't forget; update the markdown near the list sections (e.g., the "🔥 精选 Issue", "🆚 竞品对比", and "📰 社区声量" headings) to include a short inline note or example line demonstrating the braille blank insertion (for example: "在此处插入 U+2800 以在 Telegram 上保持行距: <braille blank>"). Ensure the note is brief, localized, and clearly labeled so people filling the template can copy/paste the character.references/search-patterns.md (1)
5-11: Consider consistent flag ordering for readability.The command examples use varying flag orders (e.g.,
--queriesappears before--modein some commands but the position varies). While functionally equivalent, consistent ordering improves documentation scanability.♻️ Suggested consistent ordering
-| **Project research (default)** | `python3 skills/search-layer/scripts/search.py --queries "<project> review" "<project> 评测" --mode deep --intent exploratory --num 5` | Multi-query parallel, authority-ranked | +| **Project research (default)** | `python3 skills/search-layer/scripts/search.py --mode deep --intent exploratory --queries "<project> review" "<project> 评测" --num 5` | Multi-query parallel, authority-ranked | -| **Latest updates** | `python3 skills/search-layer/scripts/search.py "<project> latest release" --mode deep --intent status --freshness pw --num 5` | Freshness-prioritized, past-week filter | +| **Latest updates** | `python3 skills/search-layer/scripts/search.py --mode deep --intent status --freshness pw --num 5 "<project> latest release"` | Freshness-prioritized, past-week filter | -| **Competitor comparison** | `python3 skills/search-layer/scripts/search.py --queries "<project> vs <competitor>" "<project> alternatives" --mode deep --intent comparison --num 5` | Comparison intent, keyword+authority weighted | +| **Competitor comparison** | `python3 skills/search-layer/scripts/search.py --mode deep --intent comparison --queries "<project> vs <competitor>" "<project> alternatives" --num 5` | Comparison intent, keyword+authority weighted | -| **Quick link lookup** | `python3 skills/search-layer/scripts/search.py "<project> official docs" --mode fast --intent resource --num 3` | Exact match, fastest | +| **Quick link lookup** | `python3 skills/search-layer/scripts/search.py --mode fast --intent resource --num 3 "<project> official docs"` | Exact match, fastest | -| **Community discussion** | `python3 skills/search-layer/scripts/search.py "<project> discussion experience" --mode deep --intent exploratory --domain-boost reddit.com,news.ycombinator.com --num 5` | Community site boosting | +| **Community discussion** | `python3 skills/search-layer/scripts/search.py --mode deep --intent exploratory --domain-boost reddit.com,news.ycombinator.com --num 5 "<project> discussion experience"` | Community site boosting |Pattern:
--mode→--intent→ optional flags →--num→ query/queries🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@references/search-patterns.md` around lines 5 - 11, Summary: The example commands use inconsistent flag ordering which harms readability; standardize them. Fix: reorder the flags in every example command so they follow the suggested pattern: --mode → --intent → any optional flags (e.g., --freshness, --domain-boost) → --num → query/queries; update each line that currently places --queries or query text before --mode (e.g., the entries with --queries, the single-query examples and the community-boost example) to follow this order and keep the same flag values and query strings; ensure all examples consistently use the flags in the same sequence (--mode, --intent, optional flags, --num, then the query/queries).
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Nitpick comments:
In `@references/output-template.md`:
- Around line 22-90: Add an explicit example/comment in the template showing
where to insert the U+2800 braille blank for Telegram spacing so contributors
won't forget; update the markdown near the list sections (e.g., the "🔥 精选
Issue", "🆚 竞品对比", and "📰 社区声量" headings) to include a short inline note or
example line demonstrating the braille blank insertion (for example: "在此处插入
U+2800 以在 Telegram 上保持行距: <braille blank>"). Ensure the note is brief,
localized, and clearly labeled so people filling the template can copy/paste the
character.
In `@references/search-patterns.md`:
- Around line 5-11: Summary: The example commands use inconsistent flag ordering
which harms readability; standardize them. Fix: reorder the flags in every
example command so they follow the suggested pattern: --mode → --intent → any
optional flags (e.g., --freshness, --domain-boost) → --num → query/queries;
update each line that currently places --queries or query text before --mode
(e.g., the entries with --queries, the single-query examples and the
community-boost example) to follow this order and keep the same flag values and
query strings; ensure all examples consistently use the flags in the same
sequence (--mode, --intent, optional flags, --num, then the query/queries).
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro
Run ID: 05d1ab53-3814-49e3-a1b6-ac7491e0b4b8
📒 Files selected for processing (3)
SKILL.mdreferences/output-template.mdreferences/search-patterns.md
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Hey @ALBEDO-TABAI 👋
I ran your skills through
tessl skill reviewat work and found some targeted improvements. Here's the full before/after:Changes summary
references/bot-reporting-rules.md— keeps SKILL.md lean while preserving all original guidancereferences/platform-setup.md— defers advanced setup details for progressive disclosure (progressive disclosure: 2/3 → 3/3)Honest disclosure — I work at @tesslio where we build tooling around skills like these. Not a pitch - just saw room for improvement and wanted to contribute.
Want to self-improve your skills? Just point your agent (Claude Code, Codex, etc.) at this Tessl guide and ask it to optimize your skill. Ping me - @rohan-tessl - if you hit any snags.
Thanks in advance 🙏
Summary by CodeRabbit