PR Design Doc
OpenHands/OpenHands
For a non-trivial pull request, write a self-contained HTML design doc under the temporary .pr/ directory and link a visibility-appropriate preview in the PR description, so maintainers grasp the…
A skill your agent uses when reviewing, designing, or modifying Java enterprise systems and need a structured, repeatable ISO/IEC 25010:2023 quality-attribute review covering Functional Suitability…
Install 814 Regulations Iso 25010
$ npx skills add jabrena/plinth --skill 814-regulations-iso-25010 -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install jabrena/plinth 814-regulations-iso-25010 --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/jabrena/plinth.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/814-regulations-iso-25010 .claude/skills/814-regulations-iso-25010 && 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 "814-regulations-iso-25010" agent skill from https://github.com/jabrena/plinth/tree/main/skills/814-regulations-iso-25010 into .claude/skills/814-regulations-iso-25010/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "814-regulations-iso-25010", 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/jabrena/plinth/tree/main/skills/814-regulations-iso-25010Type 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 jabrena/plinth --skill 814-regulations-iso-25010 -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install jabrena/plinth 814-regulations-iso-25010 --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jabrena/plinth.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/814-regulations-iso-25010 .agents/skills/814-regulations-iso-25010 && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "814-regulations-iso-25010" agent skill from https://github.com/jabrena/plinth/tree/main/skills/814-regulations-iso-25010 into .agents/skills/814-regulations-iso-25010/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "814-regulations-iso-25010", 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 jabrena/plinth --skill 814-regulations-iso-25010 -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install jabrena/plinth 814-regulations-iso-25010 --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jabrena/plinth.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/814-regulations-iso-25010 .cursor/skills/814-regulations-iso-25010 && 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 "814-regulations-iso-25010" agent skill from https://github.com/jabrena/plinth/tree/main/skills/814-regulations-iso-25010 into .cursor/skills/814-regulations-iso-25010/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "814-regulations-iso-25010", 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/jabrena/plinth.git --path skills/814-regulations-iso-25010--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 jabrena/plinth --skill 814-regulations-iso-25010 -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install jabrena/plinth 814-regulations-iso-25010 --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jabrena/plinth.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/814-regulations-iso-25010 .gemini/skills/814-regulations-iso-25010 && 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 "814-regulations-iso-25010" agent skill from https://github.com/jabrena/plinth/tree/main/skills/814-regulations-iso-25010 into .gemini/skills/814-regulations-iso-25010/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "814-regulations-iso-25010", 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 jabrena/plinth 814-regulations-iso-25010Installs 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 jabrena/plinth --skill 814-regulations-iso-25010 -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/jabrena/plinth.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/814-regulations-iso-25010 .github/skills/814-regulations-iso-25010 && 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 "814-regulations-iso-25010" agent skill from https://github.com/jabrena/plinth/tree/main/skills/814-regulations-iso-25010 into .github/skills/814-regulations-iso-25010/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "814-regulations-iso-25010", 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 jabrena/plinth --skill 814-regulations-iso-25010 -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install jabrena/plinth 814-regulations-iso-25010 --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jabrena/plinth.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/814-regulations-iso-25010 .opencode/skills/814-regulations-iso-25010 && 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 "814-regulations-iso-25010" agent skill from https://github.com/jabrena/plinth/tree/main/skills/814-regulations-iso-25010 into .opencode/skills/814-regulations-iso-25010/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "814-regulations-iso-25010", 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
814-regulations-iso-25010- GitHub stars
- 447
- Token cost
- ~2.8k tokens
- SKILL.md length
- 1,152 words
- Files
- 5 (incl. references, assets)
- Skills in repo
- 124
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
A skill your agent uses when reviewing, designing, or modifying Java enterprise systems and need a structured, repeatable ISO/IEC 25010:2023 quality-attribute review covering Functional Suitability…
- Modifying Java enterprise systems and need a structured
- SKILL.md covers Scope, ISO/IEC 25010:2023 Engineering…, Constraints and When to use this skill, plus 2 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Repeatable ISO/IEC 25010:2023 quality-attribute review covering Functional Suitability
What it does
814 Regulations Iso 25010 is an agent skill from jabrena/plinth. Use when reviewing, designing, or modifying Java enterprise systems and need a structured, repeatable ISO/IEC 25010:2023 quality-attribute review covering Functional Suitability, Performance Efficiency, Compatibility, Interaction Capability, Reliability, Security, Maintainability, Flexibility, and Safety, producing an engineering review report rather than an interactive ADR discovery. Part of Plinth Toolkit
Its SKILL.md is about 2.8k tokens, which your agent loads only when the skill is triggered. The skill folder holds 8 other files, including reference files and assets (for example `assets/questions/814-iso-25010-engineering-review-questionnaire.md`, `assets/reports/814-iso-25010-engineering-review-report-template.md` and `references/814-regulations-iso-25010-chapters-summary.md`).
It sits in Development, covering Architecture decision records. It works with Java. The repository describes itself as: Plinth is an AI-native engineering toolkit for modern Java enterprise SDLC, built around reusable Commands, Agents, Skills, and MCP Servers. The licence is Apache-2.0.
When your agent uses it
- Modifying Java enterprise systems and need a structured
- Repeatable ISO/IEC 25010:2023 quality-attribute review covering Functional Suitability
- Performance Efficiency
- Interaction Capability
Example prompts
- “/814-regulations-iso-25010”
What it can do on your machine
Read from SKILL.md and the folder at commit dca88dc. 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
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
Links to these hosts (documentation or services it may open):
iso.orgiso25000.com
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
814 Regulations Iso 25010 loads about 2.8k tokens when it runs, and up to ~8.2k if it reads all its reference files. Until then it costs about 109 tokens; SKILL.md has 1,152 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 jabrena/plinth at commit dca88dc, republished under its Apache-2.0 licence (© jabrena). 1,152 words, ~2,766 tokens.
Download SKILL.mdSave it as
.claude/skills/814-regulations-iso-25010/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.- name
- 814-regulations-iso-25010
- description
- Use when reviewing, designing, or modifying Java enterprise systems and need a structured, repeatable ISO/IEC 25010:2023 quality-attribute review covering Functional Suitability, Performance Efficiency, Compatibility, Interaction Capability, Reliability, Security, Maintainability, Flexibility, and Safety, producing an engineering review report rather than an interactive ADR discovery. Part of Plinth Toolkit
- license
- Apache-2.0
- metadata.author
- Juan Antonio Breña Moral
- metadata.version
- 0.19.0
ISO/IEC 25010:2023 Quality Model Guidance for Java Enterprise Engineering
Use this Skill to run a structured, repeatable ISO/IEC 25010:2023 product-quality review of a Java enterprise system, covering all nine quality characteristics: Functional Suitability, Performance Efficiency, Compatibility, Interaction Capability, Reliability, Security, Maintainability, Flexibility, and Safety.
Apply this Skill to determine what practical Java engineering evidence, review actions, and owner handoffs are needed before a Java enterprise system, feature, or delivery pipeline is considered quality-reviewed against the ISO/IEC 25010:2023 product quality model.
This Skill is not certification advice, compliance advice, conformity advice, an audit conclusion, or a final conformity decision. It helps Java architects, tech leads, and reviewers identify how each ISO/IEC 25010:2023 quality characteristic applies to the system under review and translate it into concrete engineering evidence, findings, and action items for qualified owners.
The purpose of this Skill is to increase awareness of potential quality-attribute gaps in a Java enterprise system and create reviewable engineering evidence for qualified owners. The response produced by this Skill does not represent ISO/IEC 25010:2023 certification readiness, compliance approval, audit findings, or final conformity with ISO/IEC 25010:2023.
The main question is:
What should a Java team review, document, and escalate so a Java enterprise system demonstrably meets each ISO/IEC 25010:2023 quality characteristic, with reviewable evidence rather than assumed quality?
Source provenance: the ISO/IEC 25010:2023 public standard summary was reviewed while authoring the bundled references. Official source references include:
- ISO/IEC 25010:2023 standard page: https://www.iso.org/standard/78176.html
- ISO/IEC 25000 SQuaRE series overview: https://iso25000.com/index.php/en/iso-25000-standards/iso-25010
Do not fetch or ingest external standard, certification, or audit web pages at runtime. Use the bundled references and escalate certification, compliance, conformity, and audit questions to qualified owners.
ISO/IEC 25010:2023 summary reference: ISO/IEC 25010:2023 product quality model summary.
Java engineering examples reference: ISO/IEC 25010:2023 Java Enterprise engineering examples.
Questionnaire asset: ISO/IEC 25010:2023 engineering review questionnaire.
Report template asset: ISO/IEC 25010:2023 engineering review report template.
Scope
This Skill applies to:
- Java enterprise systems, services, modules, APIs, and delivery pipelines under structured quality-attribute review
- Spring Boot, Quarkus, Micronaut, and framework-agnostic Java systems
- All nine ISO/IEC 25010:2023 product-quality characteristics: Functional Suitability, Performance Efficiency, Compatibility, Interaction Capability, Reliability, Security, Maintainability, Flexibility, and Safety
- Java-focused engineering evidence such as tests, static analysis, load/soak test results, circuit breakers and retries, authentication and authorization implementation, module boundaries, configuration externalization, and operational guardrails
- Owner handoffs to architecture, product, security, platform, operations, and accountable business owners when a finding requires a decision beyond engineering review
ISO/IEC 25010:2023 Engineering Review
Treat certification, compliance, and conformity determinations as qualified owner decisions.
Engineering teams should still create evidence that makes those decisions reviewable:
- Which Java system, module, service, or delivery pipeline is in scope for the quality-attribute review
- Which of the nine ISO/IEC 25010:2023 quality characteristics are most relevant to the system under review, and why
- Which concrete Java engineering evidence supports or contradicts each characteristic: tests, code review notes, load-test results, static-analysis output, configuration, operational runbooks, and monitoring signals
- Which findings represent confirmed gaps, potential gaps, or no identified concern for each characteristic
- Which owners must review or act on each finding, and what the recommended action item is
Constraints
Translate ISO/IEC 25010:2023 quality characteristics into structured, repeatable Java engineering review evidence and action items. Do not provide certification, compliance, conformity, or audit conclusions, and do not turn the review into an interactive ADR-discovery workflow.
- NOT CERTIFICATION, COMPLIANCE, OR CONFORMITY ADVICE: Frame findings as engineering review evidence and action items; never claim ISO/IEC 25010:2023 certification readiness, compliance approval, audit pass/fail status, or final conformity
- BUNDLED REFERENCES FIRST: Read the bundled ISO/IEC 25010:2023 chapters-summary and engineering-examples references, the questionnaire, and the report template before implementation review; do not fetch external standard, certification, or audit pages at runtime
- NINE-CHARACTERISTIC COVERAGE: Address all nine ISO/IEC 25010:2023 quality characteristics — Functional Suitability, Performance Efficiency, Compatibility, Interaction Capability, Reliability, Security, Maintainability, Flexibility, and Safety — for every review, even when a characteristic's finding is "no identified concern"
- STRUCTURED REVIEW, NOT INTERACTIVE ADR DISCOVERY: Use this Skill for a structured, repeatable, questionnaire-driven quality-attribute review that produces a fixed engineering review report rather than an interactive, conversational Architectural Decision Record discovery session
- EVIDENCE FIRST: Prefer reviewable Java engineering evidence over claims that a quality characteristic is satisfied
- JAVA ENGINEERING FOCUS: Translate each quality characteristic into concrete Java Enterprise review guidance: code-level, architecture-level, and operational signals a reviewer can check
- OWNER HANDOFFS: Include architecture, product, security, platform, operations, and accountable business owners when a finding requires a decision, prioritization, or risk acceptance beyond engineering review
Show full SKILL.md (413 more words)Show less
When to use this skill
- Run a structured ISO/IEC 25010:2023 quality-attribute review of a Java enterprise system
- Review a Java system for functional suitability, performance efficiency, compatibility, interaction capability, reliability, security, maintainability, flexibility, or safety
- Produce an ISO/IEC 25010:2023 engineering review report with findings and action items for a Java system
- Disambiguate a structured quality review from interactive ADR discovery for non-functional requirements
- Escalate quality-attribute findings to qualified architecture, product, security, or business owners
Workflow
- Read ISO/IEC 25010:2023 references, questionnaire, and report template
Read references/814-regulations-iso-25010-chapters-summary.md, references/814-regulations-iso-25010-engineering-examples.md, assets/questions/814-iso-25010-engineering-review-questionnaire.md, and assets/reports/814-iso-25010-engineering-review-report-template.md in that order. Use the summary for the nine ISO/IEC 25010:2023 quality characteristics, their sub-characteristics, and their Java Enterprise engineering review impact. Use the engineering examples for worked Java control patterns per characteristic. Use the questionnaire to classify system scope and evidence per characteristic before producing the report. Do not start implementation review until the summary, examples reference, questionnaire, and report template are understood.
- Complete questionnaire and classify system scope
Use assets/questions/814-iso-25010-engineering-review-questionnaire.md as a checklist against trusted local project evidence and maintainer-approved sanitized facts. Identify the Java system, module, service, or delivery pipeline under review; its architecture, users, environments, and lifecycle stage; and the owners accountable for architecture, product, security, platform, operations, and business decisions. Mark unknowns as evidence gaps and escalate missing ownership before release recommendations.
- Review implementation evidence per quality characteristic
Review Java code, configuration, tests, build files, load/soak test results, static-analysis output, circuit breakers and retries, authentication and authorization implementation, module and package boundaries, configuration externalization, operational runbooks, and monitoring evidence against each of the nine ISO/IEC 25010:2023 quality characteristics. Check for gaps between claimed quality attributes and reviewable evidence.
- Map quality characteristics to Java engineering controls
Map each of the nine characteristics — Functional Suitability, Performance Efficiency, Compatibility, Interaction Capability, Reliability, Security, Maintainability, Flexibility, and Safety — to concrete Java engineering controls and evidence: acceptance-criteria traceability, load/capacity testing, API versioning review, error-message and API-documentation review, resilience patterns, authn/authz and dependency-vulnerability review, module-coupling and test-pyramid review, horizontal-scaling and configuration-externalization review, and operational-guardrail review where the system has real-world safety effects.
- Generate review report and owner handoffs
Use assets/reports/814-iso-25010-engineering-review-report-template.md to produce a concise engineering review with scope, evidence reviewed, per-characteristic findings across all nine ISO/IEC 25010:2023 quality characteristics, evidence gaps, recommended controls, owner handoffs, residual risks, release readiness notes, and an action plan. State explicitly that certification advice, compliance advice, conformity decisions, and audit conclusions require qualified owner review.
Reference
For detailed guidance, examples, and constraints, see:
© jabrena, 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 4 other files (references, assets) in skills/814-regulations-iso-25010 of jabrena/plinth.
- SKILL.md
- assets/questions/814-iso-25010-engineering-review-questionnaire.md
- assets/reports/814-iso-25010-engineering-review-report-template.md
- references/814-regulations-iso-25010-chapters-summary.md
- references/814-regulations-iso-25010-engineering-examples.md
Open the folder on GitHubat commit dca88dc
Compare with similar skills
814 Regulations Iso 25010 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 |
|---|---|---|---|---|---|---|
| 814 Regulations Iso 25010 this skilljabrena/plinth | 447 | — | ~2.8k | Automated safety check: Pass | Apache-2.0 | |
| PR Design DocOpenHands/OpenHands | 91k | — | ~2.4k | Automated safety check: Pass | MIT | |
| Creating Description For Gh PRredis/jedis | 12k | — | ~838 | Automated safety check: Pass | MIT | |
| Cto AdvisorIbrahim-3d/orchestrator-supaconductor | 381 | 4 repos | ~2.4k | Automated safety check: Pass | MIT | |
| Code Review Skillawesome-skills/code-review-skill | 2.1k | — | ~2.8k | Automated safety check: Notes | MIT | |
| Caffeine Cache Optimization Experimentsben-manes/caffeine | 18k | — | ~2.6k | Automated safety check: Notes | Apache-2.0 |
Similar skills
- Official
Creating Description For Gh PR
redis/jedis
Generate a clear, concise GitHub PR title and description from the diff between two local git branches, and save it to prDescription.md in the repo root.
Cto Advisor
Ibrahim-3d/orchestrator-supaconductor
Technical leadership guidance for engineering teams, architecture decisions, and technology strategy.
Code Review Skill
awesome-skills/code-review-skill
Provides comprehensive code review guidance for React 19, Vue 3, Angular 17+, Svelte 5, Rust, TypeScript, Java, Java 8, PHP, Ruby, Rails, Python, Django, FastAPI, Go, C/.NET, Kotlin, Swift, Dart…
Caffeine Cache Optimization Experiments
ben-manes/caffeine
Runs controlled JMH experiments on the Caffeine cache to find shared contention and hot-path waste, then reviews correctness and returns a reviewable patch.
Domain Modeling
brim-borium/spotify_sdk
Build and sharpen a project's domain model. An agent skill from brim-borium/spotify_sdk.
More from jabrena/plinth
All 124 skills in this repo703 Technologies Fuzzing Testing
jabrena/plinth
A skill your agent uses when you need to add or review fuzz testing for Java APIs with CATS — including contract-driven negative testing, malformed payload validation, boundary input exploration, CI…
033 Architecture Diagrams
jabrena/plinth
A skill your agent uses when you need to generate Java project diagrams — including UML sequence diagrams, UML class diagrams, C4 model diagrams, UML state machine diagrams, UML Deployment Diagrams…
112 Java Maven Plugins
jabrena/plinth
A skill your agent uses when you need to add or configure Maven plugins in your pom.xml — including quality tools (enforcer, surefire, failsafe, jacoco, pitest, spotbugs, pmd), security scanning…
151 Java Performance Jmeter
jabrena/plinth
A skill your agent uses when you need to set up JMeter performance testing for a Java project — including creating the run-jmeter.sh script from the exact template, configuring load tests with…
161 Java Profiling Detect
jabrena/plinth
A skill your agent uses when you need to set up Java application profiling to detect and measure performance issues — including trusted preinstalled async-profiler v4.x setup, problem-driven…
001 Commands Inventory
jabrena/plinth
A skill your agent uses when you need to generate a checklist document with embedded commands inventory, following the embedded template exactly and producing INVENTORY-COMMANDS-JAVA.md in the…
Related
Works with
Categories
Questions about 814 Regulations Iso 25010
What does 814 Regulations Iso 25010 do?
A skill your agent uses when reviewing, designing, or modifying Java enterprise systems and need a structured, repeatable ISO/IEC 25010:2023 quality-attribute review covering Functional Suitability…. 814 Regulations Iso 25010 is an agent skill from jabrena/plinth. Use when reviewing, designing, or modifying Java enterprise systems and need a structured, repeatable ISO/IEC 25010:2023 quality-attribute review covering Functional Suitability, Performance Efficiency, Compatibility, Interaction Capability, Reliability, Security, Maintainability, Flexibility, and Safety, producing an engineering review report rather than an interactive ADR discovery.
When should I use 814 Regulations Iso 25010?
814 Regulations Iso 25010 fits situations like: modifying Java enterprise systems and need a structured; repeatable ISO/IEC 25010:2023 quality-attribute review covering Functional Suitability; performance Efficiency; interaction Capability.
How do I install 814 Regulations Iso 25010 in Claude Code?
Run `npx skills add jabrena/plinth --skill 814-regulations-iso-25010 -a claude-code`. Or copy the skill folder (skills/814-regulations-iso-25010 in jabrena/plinth) into .claude/skills/814-regulations-iso-25010 in your project. Claude Code loads it when a task matches its description.
How do I install 814 Regulations Iso 25010 in Codex?
Run `npx skills add jabrena/plinth --skill 814-regulations-iso-25010 -a codex`. Or copy the skill folder (skills/814-regulations-iso-25010 in jabrena/plinth) into .agents/skills/814-regulations-iso-25010 in your project. Codex loads it when a task matches its description.
Can I use 814 Regulations Iso 25010 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 jabrena/plinth --skill 814-regulations-iso-25010 -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/814-regulations-iso-25010, .gemini/skills/814-regulations-iso-25010, .github/skills/814-regulations-iso-25010 and .opencode/skills/814-regulations-iso-25010 in your project.
What does 814 Regulations Iso 25010 need to run?
SKILL.md names no scripts, command-line tools or credentials: 814 Regulations Iso 25010 is instructions for the agent only.
Does 814 Regulations Iso 25010 access the network?
SKILL.md names 2 domains. As links in the text: iso.org and iso25000.com. This is read from the text; nothing was executed.
Is 814 Regulations Iso 25010 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 814 Regulations Iso 25010 use?
814 Regulations Iso 25010 is published under the Apache-2.0 licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does 814 Regulations Iso 25010 use?
About 2.8k tokens (SKILL.md is roughly 11k 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 5.4k tokens, read only when the agent opens those files.
What are the alternatives to 814 Regulations Iso 25010?
Skills that share tags, products or a category with 814 Regulations Iso 25010: PR Design Doc (OpenHands/OpenHands, 91k stars), Creating Description For Gh PR (redis/jedis, 12k stars), Cto Advisor (Ibrahim-3d/orchestrator-supaconductor, 381 stars) and Code Review Skill (awesome-skills/code-review-skill, 2.1k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains 814 Regulations Iso 25010?
jabrena (a GitHub user) maintains it in jabrena/plinth, which has 447 GitHub stars. The repository holds 124 skills in this directory. The repository was last updated on October 7, 2026.
Source: jabrena/plinth on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.