Slack Team Chat Retrieval Skill
Find solutions, code snippets, decisions, and troubleshooting details in a Slack chat archive.
The skill exposes only static references to a one-message Slack export and shows no external actions, credential access, or data mutation, which limits immediate risk. It does not document sensitive-data handling, access boundaries, user confirmation, source validation, or rollback, so points are deducted.
SKILL.md, index.md, and main.md agree on message counts, users, channel, date, and reference paths. However, this is a tiny generated fixture with no abnormal-input handling, failure feedback, dependency guidance, or key-path reproduction evidence, so points are deducted and the static ceiling keeps the score below 10.
The intended use is narrowly stated as searching a single Slack chat for solutions, decisions, snippets, troubleshooting, and links, giving some trigger clarity. The actual content contains only “Welcome aboard!”, with no declared non-fit boundaries, input requirements, output boundaries, or Chinese/network-environment support, so substantial points are deducted.
The material has headings, statistics, navigation, and a references directory; MIT licensing and repository version context are present in the supplied repository files. The selected skill itself lacks installation notes, versioning, changelog, maintenance ownership, troubleshooting, and limitation disclosure, so points are deducted.
It can directly locate and display one chat message in a readable format. However, it does not match the candidate description of converting websites, GitHub repositories, and PDFs into Claude skills with conflict detection, and the single welcome message has almost no practical knowledge value, so points are deducted.
The SKILL.md statistics and reference target can be partially cross-checked against index.md and main.md, providing limited auditable static evidence. There is no independent execution result, CI coverage of this skill’s key path, or third-party validation, so only a low score is justified.
- This path appears to be a generated test artifact, not the documentation/GitHub/PDF conversion skill described by the candidate; do not treat it as an executable converter.
- It contains Slack chat data but provides no privacy, authorization, redaction, or retention guidance.
- A one-message fixture cannot substantiate search, conflict detection, failure handling, or large-input capability.
What it does & when to use it
This is a test skill in the Skill Seekers repository for the golden_chat_single golden build. It targets retrieval from a Slack chat source at fixtures/slack-export/. The supplied content contains one message, one user, and the #general channel. It exposes one main reference file plus an index for navigating the General Discussion section.
Uses fixtures/slack-export/ as the Slack chat source and organizes the content into one General Discussion section. It points users to references/main.md and references/index.md to find solutions, shared code snippets, team decisions, troubleshooting steps, and shared links from the chat history. The current dataset contains no threads, code snippets, or shared links.
- A team member needs to locate a solution discussed in the golden_chat_single history.
- An engineer needs to review an architectural discussion or decision from the chat.
- A support user needs to look up troubleshooting guidance from past messages.
- A user needs to find a resource link shared by the team, although the current dataset contains none.
Pros & cons
- Its scope is clearly limited to the golden_chat_single Slack build.
- It provides navigation through references/main.md and references/index.md.
- Its intended retrieval tasks cover solutions, decisions, troubleshooting, and shared resources.
- The supplied dataset contains only one message and one user, so coverage is very limited.
- It contains no threads, code snippets, or shared links.
- Standalone installation, client placement, and trigger syntax are undocumented.
- It is a golden-build test skill; the source provides no evidence of production-scale knowledge coverage.
How to install
The README documents installation of the full Skill Seekers collection with pip install skill-seekers. It does not document standalone installation of tests/golden/phase2/chat_single/SKILL.md or a destination path for this individual skill.
How to use
Provide the skill directory, including SKILL.md and its references files, to an Agent Skills-compatible client, then ask it to find solutions, code snippets, team decisions, or troubleshooting steps in the golden_chat_single Slack history. The source does not specify a client-specific trigger syntax.