Golden Man Agent Skill
Use when testing the man golden build
Install
one command, takes just this skill from the repositorynpx skills add https://github.com/yusufkaraaslan/Skill_Seekers --skill golden-manWhat comes with it
6 067 bytes besides the instructionThe instruction itself
16 sections, as written by the authorGolden_Man Man Pages Skill
Use when testing the man golden build
When to Use This Skill
Use this skill when you need to:
- Understand golden_man command-line tools and their options
- Look up command syntax and usage patterns
- Find examples of common command invocations
- Review available flags and environment variables
- Explore related commands via SEE ALSO references
Quick Command Reference
git-log
git log [<options>] [<revision-range>] [[--] <path>...]
git-diff
git diff [<options>] [<commit>] [--] [<path>...]
Man Page Overview
Total Man Pages: 3
Content Breakdown:
- Git: 2 man page(s)
- Curl: 1 man page(s)
Common Options
*3 options extracted across all man pages*
git-log
-p-- Generate patch output.--max-count=<number>-- Limit the number of commits to output, interacting subtly with pathspec filtering, history simplification, and the --fol...
curl
-s, --silent-- Silent mode.
Examples
*3 example(s) extracted from man pages*
git-log
Show the last three commits
git log -3
git-log
Prose-only example with no command
curl
Fetch a page
curl https://example.com
Related Commands (SEE ALSO)
git-diffgit-loggitk
Documentation Statistics
- Total Man Pages: 3
- Total Options: 3
- Total Examples: 3
- Cross-references: 3
Navigation
Reference Files:
references/git_01.md-- Gitreferences/curl_02.md-- Curl
See references/index.md for complete reference structure.
Generated by Skill Seekers | Man Page Scraper
Other skills for the same job
different authors, same section of the catalogue
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup
Use when implementing any feature or bugfix, before writing implementation code
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always
Expert guidance for systematic backtesting of trading strategies. Use when developing, testing, stress-testing, or validating quantitative trading strategies. Covers "beating ideas to death" methodology, parameter robustness testing, slippage modeling, bias prevention, and interpreting backtest results. Applicable when user asks about backtesting, strategy validation, robustness testing, avoiding overfitting, or systematic trading development.
Cloud laboratory platform for automated protein testing and validation. Use when designing proteins and needing experimental validation including binding assays, expression testing, thermostability measurements, enzyme activity assays, or protein sequence optimization. Also use for submitting experiments via API, tracking experiment status, downloading results, optimizing protein sequences for better expression using computational tools (NetSolP, SoluProt, SolubleMPNN, ESM), or managing protein design workflows with wet-lab validation.
This skill should be used for time series machine learning tasks including classification, regression, clustering, forecasting, anomaly detection, segmentation, and similarity search. Use when working with temporal data, sequential patterns, or time-indexed observations requiring specialized algorithms beyond standard ML approaches. Particularly suited for univariate and multivariate time series analysis with scikit-learn compatible APIs.
How to use it
Take yusufkaraaslan/golden-man from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
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.