Our take
Quietno commits in the last 90 days and no release in a year- Activity
- 19
- Community
- 4
- Issues
- 21
- Pull requests
- 20
+0 stars in the last 30 days
- Fewer contributors than 91% of the projects we track
This is a narrowly scoped OpenCode-to-SkillHub workflow with useful validation steps, but its quiet status and dependence on a single contributor make it an early-stage choice to verify before relying on it.
Good fit if
- You use OpenCode and can provide a valid shared-session URL.
- You want to derive a publishable skill from an existing conversation and are prepared to review the generated files.
- You are comfortable evaluating a project with no recent commits or releases and one contributor responsible for the project.
Look elsewhere if
- You need a session-to-skill workflow that works independently of OpenCode sharing links or is aimed at a different publishing platform.
- Your adoption policy requires a declared license, which the supplied repository metadata does not provide.
- You need evidence of ongoing maintenance, broader contributor support, or a recent release before adopting a tool.
All health signals
| Last commit | 2026-06-09 (4 months ago) |
|---|---|
| Commits, last 90 days | 0 |
| Releases, last 12 months | 0 |
| Contributors | 1 |
| Issues closed, last 90 days | 0 |
| Pull requests merged, last 90 days | 0 |
| Project age | 4 months |
Checked on 2026-10-13 with the GitHub API.
Project history
Daily GitHub snapshots since Oct 7, 2026. History covers stars and forks; health signals are not tracked historically.
Stars
0Forks
0Change since Nov 13, 2026: 0 stars·0 forks
Overview
session-to-skill is an OpenCode skill that takes a shared session URL, identifies reusable patterns, and generates a SKILL.md with a README in a ZIP package. Its TRACE validation and security checks are intended to help prepare the result for publication on SkillHub.
It is useful when a valuable agent workflow lives in a conversation rather than in a maintained skill. It is not a general-purpose session archive or a standalone skill authoring application: its workflow depends on OpenCode sharing links and is designed around SkillHub publishing.
Key Features
- Accepts OpenCode shared session URLs, including
opencode.ai/s/*andopncd.ai/share/*links. - Analyzes session content for patterns that can be reused as a skill.
- Generates a
SKILL.mdand a README for the resulting skill. - Runs TRACE self-checks and a three-line security review before packaging.
- Creates a ZIP containing the two generated files without a parent directory.
- Supports Windows packaging with
Compress-Archiveand macOS/Linux packaging withzip. - Offers a suggested skill name that users can change during generation.
Use Cases
- An OpenCode user wants to turn a successful troubleshooting conversation into a repeatable skill for future sessions.
- A skill author has a shared session demonstrating a useful workflow and wants a starting point for SkillHub publication.
- A team wants to extract reusable procedures from an agent session, then review the generated content before sharing it.
- A user needs a quick ZIP of a session-derived skill rather than manually assembling the expected files.
Getting Started
Install the session-to-skill/ directory in your project at .opencode/skills/session-to-skill/ or globally at ~/.config/opencode/skills/session-to-skill/, then allow the skill in opencode.json:
{
"permission": {
"skill": {
"session-to-skill": "allow"
}
}
}
Share a session with /share, then paste its link into a new OpenCode session. See the README for usage details.
License in Plain Words
No standard license was detected. Without a license, the default copyright rules apply: you may read the code, but not reuse it. Check the repository or ask the authors.
Alternatives
- skill-recorder: Captures desktop work and uses GitHub Copilot CLI to create skills, rather than extracting reusable patterns from shared OpenCode sessions.
| Project | Language | License | Stars | Status |
|---|---|---|---|---|
| session-to-skill | – | – | 0 | Quiet |
| skill-recorder | TypeScript | MIT | 4.2k | New |
Considerations
The repository is quiet: it has no commits in the last 90 days and no release in over a year. The available history shows that most of the work comes from one person, so maintenance continuity is a consideration. The README sets a 1 MB limit for fetched session content and a 500 KB limit for generated content, with oversized output automatically truncated. Shared links can expire, and failed retrieval depends on network access. The project also does not specify a license in the provided repository metadata, so clarify reuse and distribution terms before adopting or republishing it.
Found this useful?
Share it with someone who would like session-to-skill.