Skip to content

feat: optimize notebooklm-research skill (76% → 94%) - #12

Closed
rohan-tessl wants to merge 2 commits into
claude-world:mainfrom
rohan-tessl:improve/skill-review-optimization
Closed

feat: optimize notebooklm-research skill (76% → 94%)#12
rohan-tessl wants to merge 2 commits into
claude-world:mainfrom
rohan-tessl:improve/skill-review-optimization

Conversation

@rohan-tessl

Copy link
Copy Markdown

Hey @claude-world 👋

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
notebooklm-research 76% 94% +18%

This PR covers your 1 skill in the repo.

What changed in notebooklm-research
  • Reduced from 1023 to 311 lines by eliminating duplicated CLI/wrapper/Python API examples — one primary interface per operation, alternatives linked to existing references/
  • Added explicit validation gates between phases: source readiness polling (status=2), research completion checks, artifact wait_for_completion() before download
  • Removed trigger patterns from body (already captured in frontmatter description)
  • Consolidated artifact options into a quick-reference table, with detailed enums linked to references/api_surface.md
  • Condensed rate limits and error handling to compact actionable tables
  • Improved progressive disclosure with contextual links to api_surface.md, pipeline_recipes.md, and output_formats.md

Score breakdown:

  • Description: 100% → 100% (unchanged)
  • Content: 42% → 85% (+43 points)
    • Conciseness: 1/3 → 2/3
    • Actionability: 3/3 → 3/3
    • Workflow clarity: 2/3 → 3/3
    • Progressive disclosure: 1/3 → 3/3

Tessl Skill Review GitHub Action ✅

I've also included a GitHub Action (.github/workflows/skill-review.yml) that automatically reviews any SKILL.md changed in future PRs and posts scores as a PR comment.

What this gives you:

  • 🔍 Automatic tessl skill review runs on every PR touching SKILL.md
  • 💬 One updated PR comment with scores and improvement feedback
  • 🔓 Zero extra accounts — contributors don't need a Tessl login; only GITHUB_TOKEN is used
  • Non-blocking by default — feedback-only, no surprise red CI (add fail-threshold: 70 later if you want a hard gate)
  • 📈 Covers future skills incrementally as contributors edit them

Want automatic AI optimization on every SKILL.md change? 🚀

The action I've added gives you review scores on PRs. We also have a more powerful variant — tesslio/skill-review-and-optimize — that can:

  • Run AI-powered optimization suggestions on every SKILL.md PR (requires adding TESSL_API_TOKEN as a repo secret)
  • Let contributors accept suggested improvements by commenting /apply-optimize
  • Still works in review-only mode with zero secrets

Interested? Tick the box and I'll raise a follow-up PR:

  • Yes please! Add the tesslio/skill-review-and-optimize action so every SKILL.md PR gets AI optimization suggestions + the /apply-optimize flow
  • No thanks — the review scores action is enough for now

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 🙏

Restructured SKILL.md for better conciseness and progressive disclosure
while preserving all domain expertise and the 4-phase architecture.

Changes:
- Reduced from 1023 to 311 lines by eliminating duplicated CLI/wrapper/Python
  API examples — show one primary interface per operation, link alternatives
  to existing references/
- Added explicit validation gates between phases (source readiness polling,
  research completion checks, artifact wait_for_completion)
- Removed trigger patterns section from body (already in frontmatter)
- Consolidated artifact options into quick reference table, detailed enums
  linked to references/api_surface.md
- Condensed rate limits and error handling to actionable tables
- Improved progressive disclosure with contextual links to api_surface.md,
  pipeline_recipes.md, and output_formats.md

Score breakdown:
- Description: 100% → 100% (unchanged)
- Content: 42% → 85% (+43 points)
  - Conciseness: 1/3 → 2/3
  - Actionability: 3/3 → 3/3
  - Workflow clarity: 2/3 → 3/3
  - Progressive disclosure: 1/3 → 3/3
@rohan-tessl
rohan-tessl marked this pull request as ready for review April 24, 2026 09:03
@rohan-tessl
rohan-tessl requested a review from gn00295120 as a code owner April 24, 2026 09:03
@gn00295120

Copy link
Copy Markdown
Contributor

Thank you. However, after reviewing it, I’ve decided to close this PR, as we’ve already completed a new round of updates. Thank you for your suggestions.

@gn00295120 gn00295120 closed this Jul 18, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants