mcpbeat

Golden Chat

yusufkaraaslan/golden-chat

Use when testing the golden_chat golden build

2k tokens
context cost
the whole folder, loaded on every use
4
files
instructions only
0
copies elsewhere
how many repositories repackaged it
14681
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository
npx skills add https://github.com/yusufkaraaslan/Skill_Seekers --skill golden-chat

What comes with it

2 960 bytes besides the instruction
references/engineering_s1-s2.md
references/index.md
references/random_s3-s3.md

The instruction itself

11 sections, as written by the author

Golden_Chat Slack Chat Skill

Use when testing the golden_chat golden build

📋 Slack Chat Information

Platform: Slack

Source: fixtures/slack-export/

Total Messages: 6

Unique Users: 3

Channels: #engineering, #random

💡 When to Use This Skill

Use this skill when you need to:

  • Find solutions discussed in golden_chat chat history
  • Reference code snippets shared by team members
  • Understand team decisions and architectural discussions
  • Look up troubleshooting steps from past conversations
  • Find shared links and resources from the team

📖 Content Overview

Total Sections: 3

Content Breakdown:

  • #engineering: 2 sections
  • #random: 1 sections

🔑 Key Discussion Topics

*Topics frequently discussed in chat*

  • Troubleshooting: 1 conversations
  • Setup: 1 conversations

📝 Top Code Snippets

*High-quality code shared in chat*

Python (2 snippets)

Snippet 1 (by bob) (Quality: 9.5/10):

def long_helper():
    y0 = 0
    y1 = 1
    y2 = 2
    y3 = 3
    y4 = 4
    y5 = 5
    y6 = 6
    y7 = 7
    y8 = 8
    y9 = 9
    y10 = 10
    y11 = 11
    y12 = 12
    y13 = 13
    y14 = 14
    y15 = 15
    y16 = 16
    y17 = 17
    y18 = 18
    y19 = 19
    y20 = 20
    y21 = 21
    y22 = 22
    y23 = 23
    y24 = 24
    y25 = 25
    y26 = 26
    y27 = 27
    y28 = 28
    y29 = 29
    y30 = 30
    y31 = 31
    y32 = 32
    y33 = 33
    y34 = 34
    y35 = 35
    y36 = 36
    y37 = 37
    y38
...

Snippet 2 (by bob) (Quality: 7.0/10):

print('patched')

Unknown (1 snippets)

Snippet 1 (by alice) (Quality: 4.0/10):

kubectl get pods

*Key resources shared in chat*

  • https://example.com/resource/0 (by alice, in #engineering)
  • https://example.com/resource/1 (by carol, in #random)
  • https://example.com/resource/2 (by alice, in #engineering)
  • https://example.com/resource/3 (by carol, in #random)
  • https://example.com/resource/4 (by alice, in #engineering)
  • https://example.com/resource/5 (by carol, in #random)
  • https://example.com/resource/6 (by alice, in #engineering)
  • https://example.com/resource/7 (by carol, in #random)
  • https://example.com/resource/8 (by alice, in #engineering)
  • https://example.com/resource/9 (by carol, in #random)
  • https://example.com/resource/10 (by alice, in #engineering)
  • https://example.com/resource/11 (by carol, in #random)
  • https://example.com/resource/12 (by alice, in #engineering)
  • https://example.com/resource/13 (by carol, in #random)
  • https://example.com/resource/14 (by alice, in #engineering)
  • https://example.com/resource/15 (by carol, in #random)
  • https://example.com/resource/16 (by alice, in #engineering)
  • https://example.com/resource/17 (by carol, in #random)
  • https://example.com/resource/18 (by alice, in #engineering)
  • https://example.com/resource/19 (by carol, in #random)

*... and 1 more links*

📊 Chat Statistics

  • Total Messages: 6
  • Total Threads: 1
  • Code Snippets: 3
  • Shared Links: 21
  • Unique Users: 3
  • Channels: 2

Channel Activity:

  • #engineering: 5 messages, 2 users
  • #random: 1 messages, 1 users

Reference Files:

  • references/engineering_s1-s2.md - #engineering
  • references/random_s3-s3.md - #random

See references/index.md for complete chat structure.


Generated by Skill Seeker | Slack Chat Scraper

How to use it

Copy the folder

Take yusufkaraaslan/golden-chat from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.