fcli-common skill
✓ VerifiedProvides a unified command-line interface for managing Fortify products including FoD, SSC, and ScanCentral SAST/DAST.
- GitHub stars
- 25
- Files
- 8
- Last commit
- Oct 23, 2026
- License
- MIT
- Allowed tools
- —
What does the fcli-common skill do?
fcli-common provides a unified command-line interface for managing Fortify products including FoD, SSC, and ScanCentral SAST/DAST.
Summary generated from the skill's SKILL.md.
About the fcli-common skill
Managing security scanning workflows across different Fortify products is what this skill enables for DevOps engineers and security professionals. It provides a unified interface to interact with Fortify on Demand, Software Security Center, and ScanCentral SAST or DAST. An agent should load this skill when it needs to perform administrative tasks like installing tools, managing user sessions, or configuring proxy settings and trust stores.
This skill focuses on cross-product functionality rather than deep vulnerability auditing. It provides tools for session management, output formatting using JSON, and advanced filtering through SpEL query syntax. Developers can use variable chaining with the --store flag to pass data between commands without manual shell parsing. It also supports the creation and execution of automated workflows through the custom action framework and built-in actions for CI/CD integration.
What an agent can do with it
- 1Automate multi-step security workflowsUse the variable chaining feature to capture a scan ID and wait for its completion.
- 2Filter security records with complex logicApply SpEL expressions to filter results by specific severity levels.
- 3Manage Fortify tool installationsHandle the installation and version management of the Fortify CLI and related tools.
- 4Execute automated CI/CD actionsRun pre-defined automation tasks like exporting vulnerabilities or checking security policies.
Written from the skill's SKILL.md. Every use case is checked against a quote from it.
How to install the fcli-common skill
Each command copies the skill folder into the client's skills directory. Restart the client or start a new session to load it.Install the fcli-common skill in Plugin
/plugin marketplace add fortify/skills /plugin install fortify-skills@fortify
Install the fcli-common skill in Claude Code
~/.claude/skills/fcli-common/SKILL.md
$ npx degit fortify/skills/skills/fcli-common ~/.claude/skills/fcli-commonInstall the fcli-common skill in Claude Code (project)
.claude/skills/fcli-common/SKILL.md
$ npx degit fortify/skills/skills/fcli-common .claude/skills/fcli-commonInstall the fcli-common skill in Codex
~/.agents/skills/fcli-common/SKILL.md
$ npx degit fortify/skills/skills/fcli-common ~/.agents/skills/fcli-commonInstall the fcli-common skill in Gemini CLI
~/.gemini/skills/fcli-common/SKILL.md
$ npx degit fortify/skills/skills/fcli-common ~/.gemini/skills/fcli-commonInstall the fcli-common skill in Claude.ai
npx degit fortify/skills/skills/fcli-common fcli-common && zip -r fcli-common.zip fcli-common # claude.ai → Customize → Skills → + → Create skill → Upload a skill → fcli-common.zip
Automated checks
Ran Nov 15, 2026Full report →Passed our automated checks. That is not a security audit: read the scripts before you let an agent run them. How checks work · What to fix for more points
- Source repository linked and reachablefortify/skills/skills/fcli-common is public and reachablegithub.com/fortify/skills/tree/HEAD/skills/fcli-common ↗Pass
- Open source license (OSI)MITspdx.org/licenses/MIT.html ↗Pass
- Commit or release in the last yearLast commit 2026-10-23github.com/fortify/skills/commits ↗Pass
- No download-and-run or credential theft in scriptsNo scripts in the skill folderPass
- No hidden instructions in SKILL.mdNo override phrases, safeguard switches, credential requests or hidden charactersgithub.com/fortify/skills/blob/HEAD/skills/fcli-common/SKILL ↗Pass
- Pre-approved tools are scopedNo pre-approved tools; the agent asks before using onegithub.com/fortify/skills/blob/HEAD/skills/fcli-common/SKILL ↗Pass
- SKILL.md follows the Agent Skills formatthe description does not say when to use the skillgithub.com/fortify/skills/blob/HEAD/skills/fcli-common/SKILL ↗Finding
SKILL.md
View on GitHubfcli (Fortify CLI) is the unified command-line interface for all Fortify products: Fortify on Demand (FoD), Software Security Center (SSC), ScanCentral SAST, and ScanCentral DAST.
Docs: https://fortify.github.io/fcli/latest/ | Source: https://github.com/fortify/fcli | Skill content reflects fcli v3.23.
This skill covers cross-product fcli functionality: installation, session management, output formatting, SpEL queries, variable chaining, custom action development, and ScanCentral management operations. For product-specific operations (querying issues, managing scans, auditing vulnerabilities), defer to the fortify-fod or fortify-ssc skills — they provide deeper coverage of product-specific commands, API fields, and workflows.
Top-Level Command Tree
| Module | Purpose |
|---|---|
fcli fod |
Fortify on Demand (SaaS) |
fcli ssc |
Software Security Center (on-premise) |
fcli sc-sast |
ScanCentral SAST scan management |
fcli sc-dast |
ScanCentral DAST scan management |
fcli action |
Cross-product automation actions |
fcli tool |
Install/manage fcli and other Fortify tools |
fcli config |
Proxy, trust store, public key settings |
fcli util |
Utilities (variables, command listing, etc.) |
Use fcli --help to list all top-level commands, and fcli <module> -h to drill down.
Verifying Commands and Flags
When uncertain whether a flag or subcommand exists, run fcli <command> --help before using it. FCLI is fully self-documenting — every module, subcommand, and flag is discoverable at runtime. This is the authoritative source; do not invent flags or subcommands based on patterns from other CLIs.
fcli fod issue list --help # verify available flags before constructing a command
fcli fod release --help # list all release subcommands
fcli util all-commands list # list every command available in the installed version
Version Compatibility
Skill content reflects fcli v3.23 (see tested-with in frontmatter). If a command fails with "unknown subcommand", "unrecognized option", or a 404/405 REST error, check versions first: run fcli --version and, for product-specific failures, ask the user for their SSC or FoD version. Older installs may lack a command; newer installs are generally backward compatible — use fcli util all-commands list or --help to discover available commands. Do not silently retry with guessed syntax.
Installation & Upgrade
See references/fcli-install.md for full procedures. Do NOT silently download or execute anything without user confirmation. Verify: fcli --version
Session Management
Most fcli product modules require a login session before use:
fcli fod session login --url "https://api.ams.fortify.com" --user <user> --password <PAT> --tenant <tenantCode>
fcli ssc session login --url "https://my-ssc.com" --user <user> --password <pass>
Always run session logout when finished. Never output passwords or tokens in logs or chat. All Fortify API access must go through fcli — the escape hatch for endpoints not covered by a named command is fcli fod rest call / fcli ssc rest call. For credential best practices, named sessions, CI/CD setup, and the --validate flag, see references/fcli-session.md.
Output Formats
Prefer -o json for programmatic work. Parse JSON and summarize rather than relying on table output, which omits fields and truncates values.
For extended format options and JSON processing patterns, see references/output-formats.md. For --style options and SpEL query syntax, see references/fcli-query-output.md.
Filtering Quick Reference
-q / --query evaluates a SpEL expression per record:
-q "name=='MyApp'" # equality
-q "{'Critical','High'}.contains(severity)" # multi-value match (preferred over ||)
For full syntax (date functions, null safety, regex, server-side filtering), see references/fcli-query-output.md.
Variable Chaining (--store)
Store output from one command for use in the next, avoiding shell parsing of JSON:
fcli ssc appversion get MyApp:main --store myAV
fcli ssc artifact upload -f scan.fpr --appversion ::myAV::
fcli fod sast-scan start --rel MyApp:main -f pkg.zip --store myScan
fcli fod sast-scan wait-for ::myScan::
Actions
Built-in actions automate common workflows (CI/CD pipeline runs, SARIF/GitHub/GitLab vulnerability export, policy checks, PR comments):
fcli fod action list # list available FoD actions
fcli ssc action list # list available SSC actions
fcli fod action help <action> # view action usage/options
fcli fod action run <action> ... # run an action
Documentation: https://fortify.github.io/fcli/latest/fod-actions.html and https://fortify.github.io/fcli/latest/ssc-actions.html
Custom Action Development
Fcli actions are YAML files that define custom automation workflows. Use them to export vulnerabilities, enforce security policy, generate reports, integrate with external systems, etc.
See references/fcli-custom-actions.md for the full development workflow (scaffold, CLI options, step patterns, SpEL expressions, testing, signing).
Environment Variables
| Variable | Purpose |
|---|---|
FCLI_DEFAULT_FOD_URL |
Default FoD URL for all fod commands |
FCLI_DEFAULT_SSC_URL |
Default SSC URL for all ssc commands |
FCLI_DEFAULT_<CMD>_<OPT> |
Default for any option — see docs |
FCLI_STATE_DIR |
Override fcli session/variable storage location |
HTTPS_PROXY / HTTP_PROXY |
Proxy for fcli network requests |
FCLI_ENCRYPT_KEY |
Custom encryption key for session data |
Command-prefixed defaults walk the command tree, e.g. FCLI_DEFAULT_FOD_RELEASE_LIST_APP sets the default --app for fcli fod release list.
Reference Files
Load these only when needed for the specific task at hand:
| File | When to load |
|---|---|
references/fcli-install.md |
Installing, upgrading, or troubleshooting fcli setup |
references/fcli-session.md |
Session best practices, named sessions, CI/CD token guidance, --validate |
references/fcli-query-output.md |
Complex queries, SpEL syntax, null safety, date functions, server-side filtering |
references/output-formats.md |
Extended format options (json-properties, --fetch=1) and JSON processing scripting patterns |
references/mutating-operations.md |
Full safety rules for delete, create/update, access control, and REST mutations |
references/fcli-custom-actions.md |
Creating or editing custom fcli action YAML files |
references/action-yaml-reference.md |
Full YAML instruction set or SpEL function reference |
Files in this skill
8fcli-common skill questions
How do I install the fcli-common skill in Claude Code?
Run npx degit fortify/skills/skills/fcli-common ~/.claude/skills/fcli-common. Claude Code loads skills from ~/.claude/skills (all projects) or .claude/skills (one project) and uses a skill when its description matches the task.
Which clients can use the fcli-common skill?
Any client that reads the Agent Skills format: Claude Code, Codex, Gemini CLI and claude.ai (upload as a ZIP). Scripts in the skill run only where the client allows code execution.
How can I verify which flags or subcommands are available for a specific command?
You should run the command followed by the --help flag, such as fcli <command> --help, as the CLI is fully self-documenting.
What is the best output format for programmatic processing?
It is recommended to use the -o json flag for programmatic work to allow for easier parsing and summarization.
How do I store the output of one command to use in a subsequent command?
You can use the --store flag to save output into a variable, which can then be referenced using the ::variable_name:: syntax.
Can I create my own automation workflows in fcli?
Yes, you can develop custom actions using YAML files to define workflows like exporting vulnerabilities or enforcing security policies.