Swig Test
swig/swig
Run SWIG test suite for specific languages. An agent skill from swig/swig.
Agent skill
Adobe Advanced Troubleshooting
by jeremylongshore in jeremylongshore/tons-of-skills-marketplace
Isolate complex Adobe failures across DNS/TLS, auth, entitlement, schema, async state, storage, Runtime, and downstream layers without leaking credentials or content.
Install Adobe Advanced Troubleshooting
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill adobe-advanced-troubleshooting -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace adobe-advanced-troubleshooting --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/.curated/adobe-advanced-troubleshooting .claude/skills/adobe-advanced-troubleshooting && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "adobe-advanced-troubleshooting" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/adobe-advanced-troubleshooting into .claude/skills/adobe-advanced-troubleshooting/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "adobe-advanced-troubleshooting", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/adobe-advanced-troubleshootingType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill adobe-advanced-troubleshooting -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace adobe-advanced-troubleshooting --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/.curated/adobe-advanced-troubleshooting .agents/skills/adobe-advanced-troubleshooting && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "adobe-advanced-troubleshooting" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/adobe-advanced-troubleshooting into .agents/skills/adobe-advanced-troubleshooting/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "adobe-advanced-troubleshooting", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill adobe-advanced-troubleshooting -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace adobe-advanced-troubleshooting --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/.curated/adobe-advanced-troubleshooting .cursor/skills/adobe-advanced-troubleshooting && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "adobe-advanced-troubleshooting" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/adobe-advanced-troubleshooting into .cursor/skills/adobe-advanced-troubleshooting/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "adobe-advanced-troubleshooting", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/jeremylongshore/tons-of-skills-marketplace.git --path skills/.curated/adobe-advanced-troubleshooting--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill adobe-advanced-troubleshooting -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace adobe-advanced-troubleshooting --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/.curated/adobe-advanced-troubleshooting .gemini/skills/adobe-advanced-troubleshooting && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "adobe-advanced-troubleshooting" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/adobe-advanced-troubleshooting into .gemini/skills/adobe-advanced-troubleshooting/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "adobe-advanced-troubleshooting", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install jeremylongshore/tons-of-skills-marketplace adobe-advanced-troubleshootingInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill adobe-advanced-troubleshooting -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/.curated/adobe-advanced-troubleshooting .github/skills/adobe-advanced-troubleshooting && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "adobe-advanced-troubleshooting" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/adobe-advanced-troubleshooting into .github/skills/adobe-advanced-troubleshooting/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "adobe-advanced-troubleshooting", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill adobe-advanced-troubleshooting -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace adobe-advanced-troubleshooting --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/.curated/adobe-advanced-troubleshooting .opencode/skills/adobe-advanced-troubleshooting && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "adobe-advanced-troubleshooting" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/adobe-advanced-troubleshooting into .opencode/skills/adobe-advanced-troubleshooting/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "adobe-advanced-troubleshooting", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
adobe-advanced-troubleshooting- GitHub stars
- 2.8k
- Token cost
- ~1.1k tokens
- SKILL.md length
- 435 words
- Files
- 2 (incl. references)
- Skills in repo
- 3,342
- Repo updated
- First seen
- Licence
- MIT
At a glance
Isolate complex Adobe failures across DNS/TLS, auth, entitlement, schema, async state, storage, Runtime, and downstream layers without leaking credentials or content.
- Works in 6 steps: Freeze speculative retries and capture… → Check DNS/TLS/egress and service status… → Verify credential type,… → …
- The task requires adobe layered failure isolation
- SKILL.md covers Overview, Prerequisites, Current Contract and Authentication, plus 8 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Adobe Advanced Troubleshooting is an agent skill from jeremylongshore/tons-of-skills-marketplace. Isolate complex Adobe failures across DNS/TLS, auth, entitlement, schema, async state, storage, Runtime, and downstream layers without leaking credentials or content. Use when the task requires adobe layered failure isolation. Trigger with "deep debug Adobe", "Adobe job stuck", or "Adobe intermittent failure".
Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/official-docs.md`). Compatibility notes: Designed for Claude Code; live Adobe actions require network access, appropriate entitlement and authentication, and explicit approval
It sits in Testing & QA, covering Failing and flaky tests. The repository describes itself as: Model-agnostic agent-skills platform with a harness-free canonical layer, verified adapters, and the ccpi package manager. Explore at tonsofskills.com. The licence is MIT.
When your agent uses it
- The task requires adobe layered failure isolation
- With deep debug Adobe
- Adobe job stuck
- Adobe intermittent failure
Example prompts
- “deep debug Adobe”
- “Adobe job stuck”
- “Adobe intermittent failure”
- “/adobe-advanced-troubleshooting”
Requirements
- Compatibility (from SKILL.md): Designed for Claude Code; live Adobe actions require network access, appropriate entitlement and authentication, and explicit approval
- Pre-approved tools (allowed-tools): Read, Glob, Grep, Write, Edit
Workflow steps
6 steps, taken from the first numbered list in SKILL.md.
- Freeze speculative retries and capture one redacted failure envelope, topology, time window, and expected contract.
- Check DNS/TLS/egress and service status without sending customer data or credentials to unapproved tools.
- Verify credential type, organization/project/workspace, entitlement, scopes, profiles, host, method, version, and schema.
- Trace submission, returned status URL, polling, terminal state, storage access, webhook/activation, and downstream acknowledgement.
- Compare a synthetic control and the failing path one layer at a time while preserving request/job/activation IDs.
- State the isolated layer, falsified hypotheses, minimal remediation, verification, and Adobe escalation evidence.
What it can do on your machine
Read from SKILL.md and the folder at commit cfae287. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves these tools, so the agent can use them without asking each time:
ReadGlobGrepWriteEdit
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Compatibility
Designed for Claude Code; live Adobe actions require network access, appropriate entitlement and authentication, and explicit approval
From compatibility in the SKILL.md frontmatter.
Context cost
Adobe Advanced Troubleshooting loads about 1.1k tokens when it runs, and up to ~1.9k if it reads all its reference files. Until then it costs about 86 tokens; SKILL.md has 435 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from jeremylongshore/tons-of-skills-marketplace at commit cfae287, republished under its MIT licence (© jeremylongshore). 435 words, ~1,070 tokens.
Download SKILL.mdSave it as
.claude/skills/adobe-advanced-troubleshooting/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- adobe-advanced-troubleshooting
- description
- Isolate complex Adobe failures across DNS/TLS, auth, entitlement, schema, async state, storage, Runtime, and downstream layers without leaking credentials or content. Use when the task requires adobe layered failure isolation. Trigger with "deep debug Adobe", "Adobe job stuck", or "Adobe intermittent failure".
- allowed-tools
- Read, Glob, Grep, Write, Edit
- compatibility
- Designed for Claude Code; live Adobe actions require network access, appropriate entitlement and authentication, and explicit approval
- argument-hint
- <service> <operation> <incident-evidence>
- version
- 1.8.0
- license
- MIT
- author
- Jeremy Longshore <jeremy@intentsolutions.io>
- tags
- saas, adobe, troubleshooting
- model
- inherit
- effort
- high
Adobe Layered Failure Isolation
Overview
Isolate complex Adobe failures across DNS/TLS, auth, entitlement, schema, async state, storage, Runtime, and downstream layers without leaking credentials or content. This workflow produces a reviewable artifact and evidence before any live side effect.
Prerequisites
- Current first-party Adobe documentation for every selected service, API version, auth flow, limit, and lifecycle.
- Named product, identity, security, data, budget, release, and operations owners appropriate to the scope.
- Synthetic or approved non-production fixtures with secret and content canaries.
Current Contract
Troubleshooting proceeds from sanitized wire facts and known control boundaries. Decoding a bearer token locally is not authoritative proof of entitlement and raw verbose traces are unsafe defaults; use token response metadata, Console assignments, and request/job IDs. Recheck the dated evidence map before relying on mutable product behavior.
Authentication
Collect aliases, scope/profile names, expiry class, last rotation/use evidence, and correlation IDs. Never expose token payloads, Authorization, signed URLs, prompts, documents, images, or event bodies.
Instructions
- Freeze speculative retries and capture one redacted failure envelope, topology, time window, and expected contract.
- Check DNS/TLS/egress and service status without sending customer data or credentials to unapproved tools.
- Verify credential type, organization/project/workspace, entitlement, scopes, profiles, host, method, version, and schema.
- Trace submission, returned status URL, polling, terminal state, storage access, webhook/activation, and downstream acknowledgement.
- Compare a synthetic control and the failing path one layer at a time while preserving request/job/activation IDs.
- State the isolated layer, falsified hypotheses, minimal remediation, verification, and Adobe escalation evidence.
Show full SKILL.md (188 more words)Show less
Tool Discipline
Use Read, Glob, and Grep to inspect current documentation, configuration, code, fixtures, and evidence. Use Write and Edit only for approved repository artifacts. Skill invocation alone does not authorize network access, credentials, Adobe content, consent, uploads, generation, spend, deployment, registration changes, replay, cancellation, or deletion.
Approval Boundaries
Incident/data/security owners approve production diagnostics. Any token introspection, content sample, external support upload, replay, cancellation, or deletion needs explicit approval.
Error Handling
- Do not paste a token into an online decoder.
- Do not run curl -v with secrets into shared logs.
- Do not create new jobs while the original completion state is unknown.
Output
Return the layer map, redacted evidence, hypotheses/tests, isolated fault, smallest fix, verification, and escalation packet. Mark assumptions, observed environment behavior, owners, evidence dates, and unresolved gaps explicitly.
Examples
- Differentiate storage URL expiry from Adobe job failure.
- Differentiate missing product profile from malformed OAuth request.
Validation
Exercise and record expected and observed results for:
- network
- auth
- entitlement
- schema
- unknown job
- downstream
Resources
- Current first-party evidence map — recheck dated Adobe sources before execution.
- Treat observed tenant or product behavior as environment-specific evidence, never a universal Adobe guarantee.
© jeremylongshore, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 1 other file (references) in skills/.curated/adobe-advanced-troubleshooting of jeremylongshore/tons-of-skills-marketplace.
- SKILL.md
- references/official-docs.md
Open the folder on GitHubat commit cfae287
Compare with similar skills
Adobe Advanced Troubleshooting next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Adobe Advanced Troubleshooting this skilljeremylongshore/tons-of-skills-marketplace | 2.8k | — | ~1.1k | Automated safety check: Pass | MIT | |
| Swig Testswig/swig | 6.3k | — | ~2.3k | Automated safety check: Pass | Custom licence | |
| Triage CI FailureDataDog/datadog-agent | 3.8k | — | ~2.3k | Automated safety check: Pass | Apache-2.0 | |
| Dynamo Jira TicketDynamoDS/Dynamo | 2k | — | ~1.1k | Automated safety check: Pass | Apache-2.0 | |
| Fix Ready PRsfastrepl/anarlog | 9.5k | — | ~1.4k | Automated safety check: Pass | MIT | |
| Trx Analysismicrosoft/vstest | 969 | — | ~1.8k | Automated safety check: Pass | MIT |
Similar skills
- Official
Triage CI Failure
DataDog/datadog-agent
Classify a failed CI as either caused by an active incident, flakiness, or a true code regression.
Dynamo Jira Ticket
DynamoDS/Dynamo
Create structured Jira tickets for Dynamo from bug reports, failing tests, or feature requests.
Fix Ready PRs
fastrepl/anarlog
Inspect every open non-draft PR for CI failures and unresolved Cursor Bugbot findings, then fix them on the existing PR branches.
- Official
Trx Analysis
microsoft/vstest
Parse and analyze Visual Studio TRX test result files. An agent skill from microsoft/vstest.
Wio
workersio/skills
Testing workflow skill for finding high-value test candidates, writing focused tests, generating realistic workloads, reviewing test value, and diagnosing test-suite health.
More from jeremylongshore/tons-of-skills-marketplace
All 3,342 skills in this repoPerforming Security Code Review
jeremylongshore/tons-of-skills-marketplace
Execute this skill enables AI assistant to conduct a security-focused code review using the security-agent plugin.
Adapting Transfer Learning Models
jeremylongshore/tons-of-skills-marketplace
Build this skill automates the adaptation of pre-trained machine learning models using transfer learning techniques.
Agent Context Loader
jeremylongshore/tons-of-skills-marketplace
Execute proactive auto-loading: automatically detects and loads agents.md files.
Aggregating Performance Metrics
jeremylongshore/tons-of-skills-marketplace
Aggregate and centralize performance metrics from applications, systems, databases, caches, and services.
Analyzing Capacity Planning
jeremylongshore/tons-of-skills-marketplace
Execute this skill enables AI assistant to analyze capacity requirements and plan for future growth.
Analyzing Database Indexes
jeremylongshore/tons-of-skills-marketplace
Process use when you need to work with database indexing. An agent skill from jeremylongshore/tons-of-skills-marketplace.
Related
Categories
Questions about Adobe Advanced Troubleshooting
What does Adobe Advanced Troubleshooting do?
Isolate complex Adobe failures across DNS/TLS, auth, entitlement, schema, async state, storage, Runtime, and downstream layers without leaking credentials or content. Adobe Advanced Troubleshooting is an agent skill from jeremylongshore/tons-of-skills-marketplace. Isolate complex Adobe failures across DNS/TLS, auth, entitlement, schema, async state, storage, Runtime, and downstream layers without leaking credentials or content.
When should I use Adobe Advanced Troubleshooting?
Adobe Advanced Troubleshooting fits situations like: the task requires adobe layered failure isolation; with deep debug Adobe; adobe job stuck; adobe intermittent failure.
How do I install Adobe Advanced Troubleshooting in Claude Code?
Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill adobe-advanced-troubleshooting -a claude-code`. Or copy the skill folder (skills/.curated/adobe-advanced-troubleshooting in jeremylongshore/tons-of-skills-marketplace) into .claude/skills/adobe-advanced-troubleshooting in your project. Claude Code loads it when a task matches its description.
How do I install Adobe Advanced Troubleshooting in Codex?
Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill adobe-advanced-troubleshooting -a codex`. Or copy the skill folder (skills/.curated/adobe-advanced-troubleshooting in jeremylongshore/tons-of-skills-marketplace) into .agents/skills/adobe-advanced-troubleshooting in your project. Codex loads it when a task matches its description.
Can I use Adobe Advanced Troubleshooting in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill adobe-advanced-troubleshooting -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/adobe-advanced-troubleshooting, .gemini/skills/adobe-advanced-troubleshooting, .github/skills/adobe-advanced-troubleshooting and .opencode/skills/adobe-advanced-troubleshooting in your project.
What does Adobe Advanced Troubleshooting need to run?
SKILL.md names no scripts, command-line tools or credentials: Adobe Advanced Troubleshooting is instructions for the agent only. Its frontmatter pre-approves these tools: Read, Glob, Grep, Write, Edit. Compatibility (from SKILL.md): Designed for Claude Code; live Adobe actions require network access, appropriate entitlement and authentication, and explicit approval.
Does Adobe Advanced Troubleshooting access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Adobe Advanced Troubleshooting safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Adobe Advanced Troubleshooting use?
Adobe Advanced Troubleshooting is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Adobe Advanced Troubleshooting use?
About 1.1k tokens (SKILL.md is roughly 4.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 812 tokens, read only when the agent opens those files.
What are the alternatives to Adobe Advanced Troubleshooting?
Skills that share tags, products or a category with Adobe Advanced Troubleshooting: Swig Test (swig/swig, 6.3k stars), Triage CI Failure (DataDog/datadog-agent, 3.8k stars), Dynamo Jira Ticket (DynamoDS/Dynamo, 2k stars) and Fix Ready PRs (fastrepl/anarlog, 9.5k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Adobe Advanced Troubleshooting?
jeremylongshore (a GitHub user) maintains it in jeremylongshore/tons-of-skills-marketplace, which has 2,827 GitHub stars. The repository holds 3,342 skills in this directory. The repository was last updated on October 10, 2026.
Source: jeremylongshore/tons-of-skills-marketplace on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.