Using Superpowers
farm-fe/farm
A skill your agent uses when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions
Translate natural-language requirements or structured specification documents into formal temporal logic properties (LTL, CTL, safety/liveness properties).
Install Specification To Temporal Logic Generator
$ npx skills add ArabelaTso/Skills-4-SE --skill specification-to-temporal-logic-generator -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install ArabelaTso/Skills-4-SE specification-to-temporal-logic-generator --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/ArabelaTso/Skills-4-SE.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/specification-to-temporal-logic-generator .claude/skills/specification-to-temporal-logic-generator && 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 "specification-to-temporal-logic-generator" agent skill from https://github.com/ArabelaTso/Skills-4-SE/tree/main/skills/specification-to-temporal-logic-generator into .claude/skills/specification-to-temporal-logic-generator/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "specification-to-temporal-logic-generator", 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/ArabelaTso/Skills-4-SE/tree/main/skills/specification-to-temporal-logic-generatorType 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 ArabelaTso/Skills-4-SE --skill specification-to-temporal-logic-generator -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install ArabelaTso/Skills-4-SE specification-to-temporal-logic-generator --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ArabelaTso/Skills-4-SE.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/specification-to-temporal-logic-generator .agents/skills/specification-to-temporal-logic-generator && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "specification-to-temporal-logic-generator" agent skill from https://github.com/ArabelaTso/Skills-4-SE/tree/main/skills/specification-to-temporal-logic-generator into .agents/skills/specification-to-temporal-logic-generator/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "specification-to-temporal-logic-generator", 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 ArabelaTso/Skills-4-SE --skill specification-to-temporal-logic-generator -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install ArabelaTso/Skills-4-SE specification-to-temporal-logic-generator --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ArabelaTso/Skills-4-SE.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/specification-to-temporal-logic-generator .cursor/skills/specification-to-temporal-logic-generator && 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 "specification-to-temporal-logic-generator" agent skill from https://github.com/ArabelaTso/Skills-4-SE/tree/main/skills/specification-to-temporal-logic-generator into .cursor/skills/specification-to-temporal-logic-generator/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "specification-to-temporal-logic-generator", 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/ArabelaTso/Skills-4-SE.git --path skills/specification-to-temporal-logic-generator--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 ArabelaTso/Skills-4-SE --skill specification-to-temporal-logic-generator -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install ArabelaTso/Skills-4-SE specification-to-temporal-logic-generator --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ArabelaTso/Skills-4-SE.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/specification-to-temporal-logic-generator .gemini/skills/specification-to-temporal-logic-generator && 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 "specification-to-temporal-logic-generator" agent skill from https://github.com/ArabelaTso/Skills-4-SE/tree/main/skills/specification-to-temporal-logic-generator into .gemini/skills/specification-to-temporal-logic-generator/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "specification-to-temporal-logic-generator", 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 ArabelaTso/Skills-4-SE specification-to-temporal-logic-generatorInstalls 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 ArabelaTso/Skills-4-SE --skill specification-to-temporal-logic-generator -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/ArabelaTso/Skills-4-SE.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/specification-to-temporal-logic-generator .github/skills/specification-to-temporal-logic-generator && 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 "specification-to-temporal-logic-generator" agent skill from https://github.com/ArabelaTso/Skills-4-SE/tree/main/skills/specification-to-temporal-logic-generator into .github/skills/specification-to-temporal-logic-generator/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "specification-to-temporal-logic-generator", 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 ArabelaTso/Skills-4-SE --skill specification-to-temporal-logic-generator -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install ArabelaTso/Skills-4-SE specification-to-temporal-logic-generator --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ArabelaTso/Skills-4-SE.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/specification-to-temporal-logic-generator .opencode/skills/specification-to-temporal-logic-generator && 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 "specification-to-temporal-logic-generator" agent skill from https://github.com/ArabelaTso/Skills-4-SE/tree/main/skills/specification-to-temporal-logic-generator into .opencode/skills/specification-to-temporal-logic-generator/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "specification-to-temporal-logic-generator", 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
specification-to-temporal-logic-generator- GitHub stars
- 253
- Token cost
- ~1.5k tokens
- SKILL.md length
- 318 words
- Files
- 7 (incl. scripts, references)
- Skills in repo
- 170
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Translate natural-language requirements or structured specification documents into formal temporal logic properties (LTL, CTL, safety/liveness properties).
- Works in 6 steps: Parse Input Requirements → Identify Property Type → Handle Ambiguities → …
- Users need to formalize requirements for model checking
- SKILL.md covers Workflow, Output Format, Examples and Resources
- Runs Python scripts from its folder; calls python
What it does
Specification To Temporal Logic Generator is an agent skill from ArabelaTso/Skills-4-SE. Translate natural-language requirements or structured specification documents into formal temporal logic properties (LTL, CTL, safety/liveness properties). Use when users need to formalize requirements for model checking, formal verification, or property specification. Handles embedded/real-time systems, hardware verification, concurrent systems, and reactive systems. Resolves ambiguities, asks clarifying questions when needed, and outputs machine-checkable formulas with explanations. Supports multiple output…
Its SKILL.md is about 1.5k tokens, which your agent loads only when the skill is triggered. The skill folder holds 8 other files, including scripts and reference files (for example `references/ambiguity_resolution.md`, `references/ctl_patterns.md` and `references/ltl_patterns.md`).
It sits in Agent Workflows, covering Requirements gathering. The repository describes itself as: A curated list of 180+ useful Claude Skills for Software Engineering and resources for customizing AI for SE workflows. The licence is Apache-2.0.
When your agent uses it
- Users need to formalize requirements for model checking
- Formal verification
- Property specification
Example prompts
- “/specification-to-temporal-logic-generator”
Requirements
- Python 3
Workflow steps
6 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 4f38503. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Ships 2 files in scripts/ (Python), which the agent can run.
Shell commands in SKILL.md call:
python
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.
Context cost
Specification To Temporal Logic Generator loads about 1.5k tokens when it runs, and up to ~6.4k if it reads all its reference files. Until then it costs about 150 tokens; SKILL.md has 318 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); the scripts in this folder are not scanned.
SKILL.md
The full file from ArabelaTso/Skills-4-SE at commit 4f38503, republished under its Apache-2.0 licence (© ArabelaTso). 318 words, ~1,531 tokens.
Download SKILL.mdSave it as
.claude/skills/specification-to-temporal-logic-generator/SKILL.md (or your agent's skills folder). This skill also uses 6 other files; get the full folder from GitHub.- name
- specification-to-temporal-logic-generator
- description
- Translate natural-language requirements or structured specification documents into formal temporal logic properties (LTL, CTL, safety/liveness properties). Use when users need to formalize requirements for model checking, formal verification, or property specification. Handles embedded/real-time systems, hardware verification, concurrent systems, and reactive systems. Resolves ambiguities, asks clarifying questions when needed, and outputs machine-checkable formulas with explanations. Supports multiple output formats (SPIN, NuSMV, Uppaal, TLA+, Maude).
Specification-to-Temporal-Logic Generator
Translate natural-language requirements into formal temporal logic properties for model checking and formal verification.
Workflow
1. Parse Input Requirements
Extract requirements from natural language text, structured documents, or semi-formal notations.
Identify key elements:
- Events/Actions: What happens (e.g., "request", "response", "button_press")
- States/Conditions: System states (e.g., "authenticated", "locked", "idle")
- Temporal relationships: When things happen (e.g., "always", "eventually", "before")
- Quantification: Scope (e.g., "every", "some", "at least once")
2. Identify Property Type
Classify requirements:
Safety (something bad never happens): Keywords "never", "always not", "must not" → G(!bad_event)
Liveness (something good eventually happens): Keywords "eventually", "will", "guaranteed" → F(good_event)
Response (if X then eventually Y): Keywords "whenever", "if...then", "leads to" → G(X -> F Y)
Precedence (X before Y): Keywords "before", "precedes", "only after" → (!Y) U X
Fairness (repeated opportunities): Keywords "infinitely often", "repeatedly" → G F X
3. Handle Ambiguities
When requirements are ambiguous:
Check common ambiguities: temporal scope, quantification, ordering, duration
Ask clarifying questions:
"The system responds to requests" could mean:
1. Every request eventually gets a response: G(request -> F response)
2. Some requests get responses: EF(request && response)
Which interpretation matches your intent?State assumptions explicitly:
Formula: G(request -> F response)
Assumptions:
- "Every request" means all requests (universal quantification)
- "Responds" means eventually, with no time boundSee ambiguity_resolution.md for detailed patterns.
4. Select Appropriate Logic
Use LTL for single execution paths, "infinitely often" (G F), "eventually forever" (F G)
Use CTL for branching time, "on all paths" (A) vs "on some path" (E), reachability
5. Generate Formulas
Match to pattern: See ltl_patterns.md and ctl_patterns.md
Instantiate pattern:
Pattern: G(p -> F q)
Requirement: "Every request gets a response"
Formula: G(request -> F response)Validate syntax:
python scripts/validate_formula.py "G(request -> F response)" LTLAdd explanations: Plain English, formal semantics, assumptions, counterexamples
6. Convert to Tool-Specific Syntax
Generate formulas for target tools using conversion script:
python scripts/convert_format.py "G(request -> F response)" LTL SPINSee tool_syntax.md for complete syntax reference.
Output Format
For each requirement:
Requirement: [Original requirement]
Formula (LTL): [LTL formula]
Formula (CTL): [CTL formula, if applicable]
Property Type: [Safety/Liveness/Response/Precedence/Fairness]
Explanation:
- Plain English: [What it means]
- Formal Semantics: [Technical interpretation]
- Assumptions: [List of assumptions]
- Violation Example: [What would violate this]
Tool-Specific Syntax:
- SPIN: [Promela syntax]
- NuSMV: [NuSMV syntax]
- Uppaal: [Uppaal syntax]
Validation: [Result from validate_formula.py]Examples
Safety Property
Requirement: "The system never enters a deadlock state"
Output:
Formula (LTL): G(!deadlock)
Formula (CTL): AG(!deadlock)
Property Type: Safety (Invariant)
Explanation:
- Plain English: The system never reaches a deadlock state
- Formal Semantics: At all time points, deadlock does not hold
- Assumptions: "deadlock" is a well-defined state predicate
- Violation: System reaches a state where no process can progress
Tool-Specific Syntax:
- SPIN: [] (!deadlock)
- NuSMV: SPEC AG(!deadlock)
- Uppaal: A[] not deadlockResponse Property
Requirement: "Whenever a button is pressed, the light turns on within 3 time units"
Output:
Formula (TCTL): G(button_press -> F[<=3] light_on)
Property Type: Bounded Response (Liveness)
Explanation:
- Plain English: Every button press is followed by light turning on within 3 time units
- Assumptions: Time is discrete, light can turn on multiple times
- Violation: Button pressed but light doesn't turn on within 3 time units
Tool-Specific Syntax:
- Uppaal: A[] (button_press imply A<> light_on[<=3])Precedence Property
Requirement: "Users must authenticate before accessing the system"
Output:
Formula (LTL): (!access) U authenticated
Formula (CTL): A[(!access) U authenticated]
Property Type: Precedence (Safety)
Explanation:
- Plain English: No access occurs until authentication happens
- Assumptions: Authentication is one-time, access can occur multiple times after
- Violation: Access occurs before authentication
Tool-Specific Syntax:
- SPIN: ((!access) U authenticated)
- NuSMV: SPEC A[(!access) U authenticated]Resources
scripts/
validate_formula.py- Validate temporal logic syntax (LTL, CTL, SPIN)convert_format.py- Convert between tool formats (SPIN, NuSMV, Uppaal, TLA+, Maude)
references/
ltl_patterns.md- LTL property patterns and templatesctl_patterns.md- CTL property patternsambiguity_resolution.md- Guidelines for handling ambiguous requirementstool_syntax.md- Syntax for different model checkers
© ArabelaTso, Apache-2.0. 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 6 other files (scripts, references) in skills/specification-to-temporal-logic-generator of ArabelaTso/Skills-4-SE.
- SKILL.md
- references/ambiguity_resolution.md
- references/ctl_patterns.md
- references/ltl_patterns.md
- references/tool_syntax.md
- scripts/convert_format.py
- scripts/validate_formula.py
Open the folder on GitHubat commit 4f38503
Compare with similar skills
Specification To Temporal Logic Generator 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 |
|---|---|---|---|---|---|---|
| Specification To Temporal Logic Generator this skillArabelaTso/Skills-4-SE | 253 | — | ~1.5k | Automated safety check: Pass | Apache-2.0 | |
| Using Superpowersfarm-fe/farm | 5.6k | 35 repos | ~1.4k | Automated safety check: Pass | MIT | |
| Interview Meaddyosmani/agent-skills | 103k | 6 repos | ~3.8k | Automated safety check: Pass | MIT | |
| Grillingpietheinstrengholt/rssmonster | 564 | 31 repos | ~510 | Automated safety check: Pass | MIT | |
| Agentic Workflow Designerdotnet/Open-XML-SDK | 4.6k | 2 repos | ~3.5k | Automated safety check: Pass | MIT | |
| Ask User QuestionMemTensor/MemOS | 12k | — | ~1k | Automated safety check: Pass | Apache-2.0 |
Similar skills
Interview Me
addyosmani/agent-skills
Asks one question at a time, each with a best guess attached, until the agent is about 95 percent sure what you really want, before any plan, spec or code.
Grilling
pietheinstrengholt/rssmonster
Grill the user relentlessly about a plan, decision, or idea.
- Official
Agentic Workflow Designer
dotnet/Open-XML-SDK
Interviews you one question at a time about goal, trigger, permissions and data needs, then drafts a single agentic workflow markdown file.
Ask User Question
MemTensor/MemOS
Shows a question as a modal in the interface to clarify a task, collect a preference or get approval, since the user cannot see terminal output.
Brainstorming Before Building
jnMetaCode/superpowers-zh
Turns a rough idea into an approved design before any code is written, sorting the request into spike, bounded or architectural and enforcing an approval gate.
More from ArabelaTso/Skills-4-SE
All 170 skills in this repoCve Watchlist Action Recommendation Generator
ArabelaTso/Skills-4-SE
Generate prioritized CVE watchlists and actionable security recommendations for repositories.
Framework Migration Assistant
ArabelaTso/Skills-4-SE
Automatically migrate Python web applications between frameworks (Flask → FastAPI, Django → FastAPI).
Metamorphic Test Generator
ArabelaTso/Skills-4-SE
Generate test cases using metamorphic testing by applying transformations based on metamorphic properties.
Reproduction Trace Instrumenter
ArabelaTso/Skills-4-SE
Instruments programs to capture execution traces specifically for reproducing reported bugs, enabling consistent replay and diagnosis of failures.
Spring Mvc To Boot Migrator
ArabelaTso/Skills-4-SE
Automatically migrate Spring MVC applications to Spring Boot.
State Snapshot Instrumenter
ArabelaTso/Skills-4-SE
Instrument programs (Python, C/C++, Java) to capture snapshots of key program states at runtime, including variables, memory, and call stacks.
Related
Categories
Questions about Specification To Temporal Logic Generator
What does Specification To Temporal Logic Generator do?
Translate natural-language requirements or structured specification documents into formal temporal logic properties (LTL, CTL, safety/liveness properties). Specification To Temporal Logic Generator is an agent skill from ArabelaTso/Skills-4-SE. Translate natural-language requirements or structured specification documents into formal temporal logic properties (LTL, CTL, safety/liveness properties).
When should I use Specification To Temporal Logic Generator?
Specification To Temporal Logic Generator fits situations like: users need to formalize requirements for model checking; formal verification; property specification.
How do I install Specification To Temporal Logic Generator in Claude Code?
Run `npx skills add ArabelaTso/Skills-4-SE --skill specification-to-temporal-logic-generator -a claude-code`. Or copy the skill folder (skills/specification-to-temporal-logic-generator in ArabelaTso/Skills-4-SE) into .claude/skills/specification-to-temporal-logic-generator in your project. Claude Code loads it when a task matches its description.
How do I install Specification To Temporal Logic Generator in Codex?
Run `npx skills add ArabelaTso/Skills-4-SE --skill specification-to-temporal-logic-generator -a codex`. Or copy the skill folder (skills/specification-to-temporal-logic-generator in ArabelaTso/Skills-4-SE) into .agents/skills/specification-to-temporal-logic-generator in your project. Codex loads it when a task matches its description.
Can I use Specification To Temporal Logic Generator 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 ArabelaTso/Skills-4-SE --skill specification-to-temporal-logic-generator -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/specification-to-temporal-logic-generator, .gemini/skills/specification-to-temporal-logic-generator, .github/skills/specification-to-temporal-logic-generator and .opencode/skills/specification-to-temporal-logic-generator in your project.
What does Specification To Temporal Logic Generator need to run?
Going by SKILL.md and its folder, Specification To Temporal Logic Generator needs Python for the scripts in its folder and the command-line tools its instructions call (python). Our summary lists: Python 3.
Does Specification To Temporal Logic Generator 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 Specification To Temporal Logic Generator 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. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.
What licence does Specification To Temporal Logic Generator use?
Specification To Temporal Logic Generator is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Specification To Temporal Logic Generator use?
About 1.5k tokens (SKILL.md is roughly 6.1k 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 4.9k tokens, read only when the agent opens those files.
What are the alternatives to Specification To Temporal Logic Generator?
Skills that share tags, products or a category with Specification To Temporal Logic Generator: Using Superpowers (farm-fe/farm, 5.6k stars), Interview Me (addyosmani/agent-skills, 103k stars), Grilling (pietheinstrengholt/rssmonster, 564 stars) and Agentic Workflow Designer (dotnet/Open-XML-SDK, 4.6k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Specification To Temporal Logic Generator?
ArabelaTso (a GitHub user) maintains it in ArabelaTso/Skills-4-SE, which has 253 GitHub stars. The repository holds 170 skills in this directory. The repository was last updated on August 21, 2026.
Source: ArabelaTso/Skills-4-SE on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.