SkillAgentSearch skills...

ss

💼 Barqly Vault — an open-source desktop app to encrypt sensitive documents and Bitcoin metadata. Built with Tauri, Rust & React. Cross-platform, strong age encryption, intuitive UX, no cloud dependencies. Alpha preview available.

Install / Use

npx skills add Barqly/barqly-vault

Installs into whichever agent you are using.

About this skill
⚡

Claude Commands

Claude Code slash commands

Quality Score

68/100

Supported Platforms

Claude Code

Our assessment of ss

ss scores 68/100 on our quality scale, 1089th of 1,185 Content & Media skills we index.

Its Claude Commands is 3.3 KB long, well organised into 23 sections with 1 code example: a solid amount of guidance for an agent.

It has no GitHub stars yet, so there is no community track record; judge it on its content.

Substance
26/30
Structure
17/20
Description
15/15
Adoption
0/20
Freshness
11/15

Maintenance, license and trust

  • The repository was last updated about 11 months ago. That is recent enough to be usable, but agent tooling moves fast, so check the instructions against your agent's current version.
  • No license is declared. By default that means all rights are reserved: you can read it, but reusing or redistributing it is not clearly permitted. Ask the author before building on it commercially.
  • Its trust signals score 74/100, with 3 cautions from licensing, adoption, age or documentation. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

ss compared with similar skills

All 4 of these similar skills score higher than ss; compare them before choosing.

SkillScoreStarsUpdatedFormat
ss (this skill)by Barqly68011mo agoClaude Commands
claude-memby thedotmack100100.6ktodayCLAUDE.md
Agent-Reachby Panniantong10097.2k6d agoCLAUDE.md
taste-skillby Leonxlnx10096.0ktodayCLAUDE.md
Understand-Anythingby Egonex-AI10086.2k2d agoCLAUDE.md

Frequently asked questions

How do I install ss?
Run npx skills add Barqly/barqly-vault. The install tabs above show the steps for each supported agent.
Which AI agents does ss work with?
It is written for Claude Code, as a Claude Commands file. Other agents that read the same format can often use it too.
Is ss safe to use?
It declares no license and scores 74/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is ss still maintained?
The repository was last updated about 11 months ago. That is recent enough to be usable, but agent tooling moves fast, so check the instructions against your agent's current version.

Save this file as: .claude/commands/session-summary.md

Create a comprehensive session summary document to preserve context before clearing the chat.

Instructions

Please create a session summary file with the following specifications:

  1. Filename Format: ss{DD}{MM}.{n}.md where:

    • DD = day of month (01-31)
    • MM = month (01-12)
    • n = counter (1, 2, 3...) for multiple summaries in a day
  2. Location: Save in ./handoff/ folder (create if it doesn't exist)

  3. Template Structure - Include these sections:

Session Summary Template

# Session Summary
**Date:** [Current date and time]
**Session ID:** [Filename]
**Project:** [Project name]

## 🎯 Primary Objective
[What was the main goal of this session?]

## 📁 Files Modified/Referenced
- List all files we worked on or discussed
- Include their paths relative to project root
- Note which ones were modified vs just referenced

## 🔍 Problem Statement
### Initial Issue:
[Describe the original problem]

### Root Cause (if identified):
[What was causing the issue]

## ✅ Solutions Attempted
[Document each attempt with:]
- Approach taken
- Why we thought it would work
- Result/outcome
- Code snippets if relevant

## 🎉 Working Solution
[If found, document the final working solution]
- Implementation details
- Why it works
- Key code changes

## 🔧 Current State
- **Resolved Issues:**
  - List what's been fixed
  
- **Pending Issues:**
  - List what still needs work
  
- **Blockers:**
  - Any blockers identified

## 💡 Observations & Insights
- Key learnings from this session
- Patterns noticed
- Gotchas discovered

## 🔄 Refactoring Opportunities
[Things to improve when time permits]
- Component/file name
- What could be improved
- Priority level

## 📝 Code Context
[Preserve important code snippets]

### Key Configuration:
[Any config changes or important settings]

### Critical Functions/Methods:
[Core logic we worked on]

### Environment/Dependencies:
[Package versions, env vars, etc.]

## 🚀 Next Steps
1. Clear action items for next session
2. What to tackle first
3. Any research needed

## 🔗 Related Resources
- Previous session: [Link to previous summary if exists]
- Documentation: [Any docs referenced]
- Issues/PRs: [Related tickets]

## 💭 Additional Notes
[Any other context that might be helpful]

## 🤖 Context for Claude
[Special section for Claude-specific context]
- Understanding of the problem domain
- Approaches that definitely don't work
- User preferences discovered
- Technical constraints identified

Execution Steps

When this command is invoked:

  1. Check current date and determine the filename (ss{DD}{MM}.{n}.md)

  2. Create the handoff directory if it doesn't exist

  3. Find the next available counter for today

  4. Create the file with the filled template based on our current conversation

  5. Include:

    • All files we've discussed or modified
    • All error messages encountered
    • All solutions attempted with their outcomes
    • Current working solution if any
    • Any patterns or insights discovered
    • Clear next steps
  6. After creating, show me the file path and key sections of the summary

  7. Remind me that I can share this file in a new chat to continue where we left off

Please execute this now and create a comprehensive summary of our current session.

Related Skills

View on GitHub
GitHub Stars0
CategoryContent
Updated10mo ago
Forks0

Trust signals

74/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

1 medium2 low
ss — Claude Commands: Install & Safety Check | SkillAgent