Навыки jira-safe
📦
jira-safe
Ревизия содержимого r1 Высокий риск ⚙️ Внешние команды🌐 Доступ к сети🔑 Переменные окружения📁 Доступ к файловой системе
Организация рабочих процессов SAFe в Jira
Планирование SAFe в Jira сложно поддерживать согласованным между эпиками, историями и подзадачами. Этот навык предоставляет структурированные шаблоны и скрипты для создания задач Jira и обновления рабочих процессов.
Поддерживает: Claude Codex Code(CC)
Остановитесь и запросите подтверждение перед установкой.
Проверьте план и получите явное согласие пользователя перед изменением файлов.
Установить с помощью моего Агента
Скопируйте этот запрос в своего Агента. Он содержит каноническую страницу Skill и манифест.
Запрос агента
Review the Skillstore skill "jira-safe" from https://skillstore.io/skills/01000001-01001110-jira-safe.md and its manifest at https://skillstore.io/api/skills/01000001-01001110-jira-safe/manifest. Verify the artifact. Stop and obtain explicit user consent before installing or changing files.Ваш Агент по-прежнему должен показать план и запросить все подтверждения, требуемые политикой безопасности.
Ресурсы для AI-агентов
Используйте эти ссылки, когда AI-агенту, crawler или script нужен чистый контекст вместо полной страницы.
Протестировать
Использование «jira-safe». Создайте историю для сброса пароля в проекте Jira, управляемом командой.
Ожидаемый результат:
История SAFe с persona, goal, benefit, критериями Given-When-Then, definition of done и предложенными подзадачами.
Использование «jira-safe». Спланируйте MVP-бэклог для продукта маркетингового ассистента.
Ожидаемый результат:
Схема эпика с бизнес-результатами, метриками успеха, сгруппированными историями, подзадачами реализации и рекомендациями по связыванию в Jira.
Использование «jira-safe». Переместите SCRUM-100 из To Do в Done после реализации.
Ожидаемый результат:
Чеклист перехода, который запрашивает доступные переходы Jira, выбирает соответствующее состояние, добавляет заметки о завершении и подтверждает обновление.
Аудит безопасности
Высокий рискv11 • 07.07.2026 Открыть версионный отчет
The many command-execution and certificate findings are mostly false positives caused by Markdown backticks, JavaScript template literals, and Jira issue key fields. Real risks remain because the skill and scripts use Jira credentials, perform authenticated network writes, and include destructive bulk-delete guidance.
8
Просканировано файлов
4,225
Проанализировано строк
78
Пункты проверки
0
Ложные срабатывания проигнорированы
Подтверждённые проблемы безопасности (16)
Высокий
Environment file access
const JIRA_EMAIL = process.env.JIRA_EMAIL;
The code reads JIRA_EMAIL as part of the Basic authentication credential pair. It is expected but still sensitive account-identifying data.
Высокий
Environment file access
const JIRA_API_TOKEN = process.env.JIRA_API_TOKEN;
The code reads JIRA_API_TOKEN, a secret used to build Basic authentication for Jira API calls. Exposure or misuse of this token would affect the Jira account.
Высокий
Environment file access
const JIRA_EMAIL = process.env.JIRA_EMAIL;
The code reads JIRA_EMAIL as part of the Basic authentication credential pair. It is expected but still sensitive account-identifying data.
Высокий
Environment file access
const JIRA_API_TOKEN = process.env.JIRA_API_TOKEN;
The code reads JIRA_API_TOKEN, a secret used to build Basic authentication for Jira API calls. Exposure or misuse of this token would affect the Jira account.
Высокий
Environment file access
# Load .env file from jira root (two levels up from scripts/)
The Python helper loads a parent .env file that can contain Jira credentials. Reading local environment files is a real sensitive-file access pattern.
Высокий
Environment file access
env_path = Path(__file__).parent.parent.parent / '.env'
The Python helper loads a parent .env file that can contain Jira credentials. Reading local environment files is a real sensitive-file access pattern.
Высокий
Environment file access
const JIRA_EMAIL = process.env.JIRA_EMAIL;
The code reads JIRA_EMAIL as part of the Basic authentication credential pair. It is expected but still sensitive account-identifying data.
Высокий
Environment file access
const JIRA_API_TOKEN = process.env.JIRA_API_TOKEN;
The code reads JIRA_API_TOKEN, a secret used to build Basic authentication for Jira API calls. Exposure or misuse of this token would affect the Jira account.
Показать все подтверждённые находки (16)
Высокий
Environment file access
# Load .env file from jira root (two levels up from scripts/)
The Python helper loads a parent .env file that can contain Jira credentials. Reading local environment files is a real sensitive-file access pattern.
Высокий
Environment file access
env_path = Path(__file__).parent.parent.parent / '.env'
The Python helper loads a parent .env file that can contain Jira credentials. Reading local environment files is a real sensitive-file access pattern.
Высокий
Environment file access
const JIRA_EMAIL = process.env.JIRA_EMAIL;
The code reads JIRA_EMAIL as part of the Basic authentication credential pair. It is expected but still sensitive account-identifying data.
Высокий
Environment file access
const JIRA_API_TOKEN = process.env.JIRA_API_TOKEN;
The code reads JIRA_API_TOKEN, a secret used to build Basic authentication for Jira API calls. Exposure or misuse of this token would affect the Jira account.
Высокий
Environment file access
# Load .env file from jira root (two levels up from scripts/)
The Python helper loads a parent .env file that can contain Jira credentials. Reading local environment files is a real sensitive-file access pattern.
Высокий
Environment file access
env_path = Path(__file__).parent.parent.parent / '.env'
The Python helper loads a parent .env file that can contain Jira credentials. Reading local environment files is a real sensitive-file access pattern.
Высокий
Destructive Jira Bulk Delete Helper
The skill documents a helper that searches all issues in a project and deletes each issue with deleteSubtasks=true. This can remove a large Jira backlog if copied or executed with a privileged token.
Lines 341-355 show a bulk delete routine that searches Jira issues and sends DELETE requests. The behavior is explicit and destructive, though it is documented rather than hidden.
Средний
Bulk Jira Issue Creation Without Interactive Confirmation
Executable scripts create epics, stories, and subtasks directly when run. They do not implement a dry-run or interactive confirmation step before writing to Jira.
The cited code calls createIssue for epics, stories, and subtasks in loops. No confirmation gate or dry-run branch is present in those execution paths.
Пункты проверки возможностей (78)
Это реальные локальные возможности, которые могут ожидаться для этого навыка, поэтому они требуют проверки, но не считаются подтверждённым вредоносным поведением.
Высокий
Fetch API call
await fetch(`${JIRA_URL}/rest/api/3/issue/${issue.key}?deleteSubtasks=true`, {
This Jira API request performs DELETE against issue URLs with deleteSubtasks=true. It can remove project issues if executed with a privileged token.
Средний
Environment variable access (dot notation)
const JIRA_EMAIL = process.env.JIRA_EMAIL;
The code reads Jira credential values from the environment for Basic authentication. This is expected, but it handles sensitive account access material.
Средний
Environment variable access (dot notation)
const JIRA_API_TOKEN = process.env.JIRA_API_TOKEN;
The code reads Jira credential values from the environment for Basic authentication. This is expected, but it handles sensitive account access material.
Средний
Environment variable object
const JIRA_EMAIL = process.env.JIRA_EMAIL;
The code reads Jira credential values from the environment for Basic authentication. This is expected, but it handles sensitive account access material.
Средний
Environment variable object
const JIRA_API_TOKEN = process.env.JIRA_API_TOKEN;
The code reads Jira credential values from the environment for Basic authentication. This is expected, but it handles sensitive account access material.
Средний
Fetch API call
const response = await fetch(url, {
The executable script uses HTTP requests to Jira with an Authorization header. This is intended automation, but it can create or inspect remote Jira data.
Средний
Fetch API call
const response = await fetch(url, {
The executable script uses HTTP requests to Jira with an Authorization header. This is intended automation, but it can create or inspect remote Jira data.
Средний
Fetch API call
const response = await fetch(url, { headers });
The executable script uses HTTP requests to Jira with an Authorization header. This is intended automation, but it can create or inspect remote Jira data.
Средний
Environment variable access (dot notation)
const JIRA_EMAIL = process.env.JIRA_EMAIL;
The code reads Jira credential values from the environment for Basic authentication. This is expected, but it handles sensitive account access material.
Средний
Environment variable access (dot notation)
const JIRA_API_TOKEN = process.env.JIRA_API_TOKEN;
The code reads Jira credential values from the environment for Basic authentication. This is expected, but it handles sensitive account access material.
Средний
Environment variable object
const JIRA_EMAIL = process.env.JIRA_EMAIL;
The code reads Jira credential values from the environment for Basic authentication. This is expected, but it handles sensitive account access material.
Средний
Environment variable object
const JIRA_API_TOKEN = process.env.JIRA_API_TOKEN;
The code reads Jira credential values from the environment for Basic authentication. This is expected, but it handles sensitive account access material.
Средний
HTTP client library
def make_request(method, path, data=None):
The executable script uses HTTP requests to Jira with an Authorization header. This is intended automation, but it can create or inspect remote Jira data.
Средний
HTTP client library
return make_request('POST', '/issue', {'fields': fields})
The executable script uses HTTP requests to Jira with an Authorization header. This is intended automation, but it can create or inspect remote Jira data.
Средний
HTTP client library
return make_request('POST', '/issue', {'fields': fields})
The executable script uses HTTP requests to Jira with an Authorization header. This is intended automation, but it can create or inspect remote Jira data.
Средний
HTTP client library
return make_request('GET', f'/issue/{issue_key}?fields=summary,issuetype')
The executable script uses HTTP requests to Jira with an Authorization header. This is intended automation, but it can create or inspect remote Jira data.
Средний
Python HTTP libraries
from urllib.request import Request, urlopen
The executable script uses HTTP requests to Jira with an Authorization header. This is intended automation, but it can create or inspect remote Jira data.
Средний
Python environment access
os.environ.setdefault(key.strip(), value.strip())
This line loads values from a .env file into process environment variables. The surrounding block is used to provide Jira credentials to API calls.
Средний
Python environment access
JIRA_EMAIL = os.environ.get('JIRA_EMAIL')
The code reads Jira credential values from the environment for Basic authentication. This is expected, but it handles sensitive account access material.
Средний
Python environment access
JIRA_API_TOKEN = os.environ.get('JIRA_API_TOKEN')
The code reads Jira credential values from the environment for Basic authentication. This is expected, but it handles sensitive account access material.
Средний
Fetch API call
const response = await fetch(url, { ...options, headers });
The executable script uses HTTP requests to Jira with an Authorization header. This is intended automation, but it can create or inspect remote Jira data.
Средний
Environment variable access (dot notation)
const JIRA_EMAIL = process.env.JIRA_EMAIL;
The code reads Jira credential values from the environment for Basic authentication. This is expected, but it handles sensitive account access material.
Средний
Environment variable access (dot notation)
const JIRA_API_TOKEN = process.env.JIRA_API_TOKEN;
The code reads Jira credential values from the environment for Basic authentication. This is expected, but it handles sensitive account access material.
Средний
Environment variable object
const JIRA_EMAIL = process.env.JIRA_EMAIL;
The code reads Jira credential values from the environment for Basic authentication. This is expected, but it handles sensitive account access material.
Средний
Environment variable object
const JIRA_API_TOKEN = process.env.JIRA_API_TOKEN;
The code reads Jira credential values from the environment for Basic authentication. This is expected, but it handles sensitive account access material.
Средний
HTTP client library
def jira_request(path, method='GET', data=None):
The executable script uses HTTP requests to Jira with an Authorization header. This is intended automation, but it can create or inspect remote Jira data.
Средний
HTTP client library
return jira_request('/issue', method='POST', data={'fields': fields})
The executable script uses HTTP requests to Jira with an Authorization header. This is intended automation, but it can create or inspect remote Jira data.
Средний
Python HTTP libraries
from urllib.request import Request, urlopen
The executable script uses HTTP requests to Jira with an Authorization header. This is intended automation, but it can create or inspect remote Jira data.
Средний
Python environment access
os.environ.setdefault(key.strip(), value.strip())
This line loads values from a .env file into process environment variables. The surrounding block is used to provide Jira credentials to API calls.
Средний
Python environment access
JIRA_EMAIL = os.environ.get('JIRA_EMAIL')
The code reads Jira credential values from the environment for Basic authentication. This is expected, but it handles sensitive account access material.
Средний
Python environment access
JIRA_API_TOKEN = os.environ.get('JIRA_API_TOKEN')
The code reads Jira credential values from the environment for Basic authentication. This is expected, but it handles sensitive account access material.
Средний
Fetch API call
const response = await fetch(`${JIRA_BASE_URL}/rest/api/3/issue`, {
The executable script uses HTTP requests to Jira with an Authorization header. This is intended automation, but it can create or inspect remote Jira data.
Средний
Environment variable access (dot notation)
const JIRA_EMAIL = process.env.JIRA_EMAIL;
The code reads Jira credential values from the environment for Basic authentication. This is expected, but it handles sensitive account access material.
Средний
Environment variable access (dot notation)
const JIRA_API_TOKEN = process.env.JIRA_API_TOKEN;
The code reads Jira credential values from the environment for Basic authentication. This is expected, but it handles sensitive account access material.
Средний
Environment variable object
const JIRA_EMAIL = process.env.JIRA_EMAIL;
The code reads Jira credential values from the environment for Basic authentication. This is expected, but it handles sensitive account access material.
Средний
Environment variable object
const JIRA_API_TOKEN = process.env.JIRA_API_TOKEN;
The code reads Jira credential values from the environment for Basic authentication. This is expected, but it handles sensitive account access material.
Средний
HTTP client library
def make_request(method, path, data=None):
The executable script uses HTTP requests to Jira with an Authorization header. This is intended automation, but it can create or inspect remote Jira data.
Средний
HTTP client library
return make_request('POST', '/issue', {'fields': fields})
The executable script uses HTTP requests to Jira with an Authorization header. This is intended automation, but it can create or inspect remote Jira data.
Средний
Python HTTP libraries
from urllib.request import Request, urlopen
The executable script uses HTTP requests to Jira with an Authorization header. This is intended automation, but it can create or inspect remote Jira data.
Средний
Python environment access
os.environ.setdefault(key.strip(), value.strip())
This line loads values from a .env file into process environment variables. The surrounding block is used to provide Jira credentials to API calls.
Средний
Python environment access
JIRA_EMAIL = os.environ.get('JIRA_EMAIL')
The code reads Jira credential values from the environment for Basic authentication. This is expected, but it handles sensitive account access material.
Средний
Python environment access
JIRA_API_TOKEN = os.environ.get('JIRA_API_TOKEN')
The code reads Jira credential values from the environment for Basic authentication. This is expected, but it handles sensitive account access material.
Низкий
Fetch API call
const response = await fetch(`${JIRA_BASE_URL}/rest/api/3/issue`, {
The skill documents authenticated Jira REST calls as part of its intended workflow. This is legitimate functionality but still a real external network side effect.
Низкий
Fetch API call
const response = await fetch(`${JIRA_BASE_URL}/rest/api/3/issue`, {
The skill documents authenticated Jira REST calls as part of its intended workflow. This is legitimate functionality but still a real external network side effect.
Низкий
Fetch API call
const response = await fetch(
The skill documents authenticated Jira REST calls as part of its intended workflow. This is legitimate functionality but still a real external network side effect.
Низкий
Fetch API call
const response = await fetch(
The skill documents authenticated Jira REST calls as part of its intended workflow. This is legitimate functionality but still a real external network side effect.
Низкий
Fetch API call
const response = await fetch(
The skill documents authenticated Jira REST calls as part of its intended workflow. This is legitimate functionality but still a real external network side effect.
Низкий
Fetch API call
const response = await fetch(
The skill documents authenticated Jira REST calls as part of its intended workflow. This is legitimate functionality but still a real external network side effect.
Низкий
Environment variable access (dot notation)
const JIRA_BASE_URL = process.env.JIRA_BASE_URL;
The code reads the Jira base URL from the environment and later sends authenticated requests to that destination. This is configuration, but it affects credential exposure boundaries.
Низкий
Environment variable access (dot notation)
const PROJECT_KEY = process.env.JIRA_PROJECT_KEY;
The project key is not secret, but it controls which Jira project receives write operations. Misconfiguration can direct automation to the wrong project.
Низкий
Environment variable object
const JIRA_BASE_URL = process.env.JIRA_BASE_URL;
The code reads the Jira base URL from the environment and later sends authenticated requests to that destination. This is configuration, but it affects credential exposure boundaries.
Низкий
Environment variable object
const PROJECT_KEY = process.env.JIRA_PROJECT_KEY;
The project key is not secret, but it controls which Jira project receives write operations. Misconfiguration can direct automation to the wrong project.
Низкий
Environment variable access (dot notation)
const JIRA_BASE_URL = process.env.JIRA_BASE_URL;
The code reads the Jira base URL from the environment and later sends authenticated requests to that destination. This is configuration, but it affects credential exposure boundaries.
Низкий
Environment variable access (dot notation)
const PROJECT_KEY = process.env.JIRA_PROJECT_KEY || 'SCRUM';
The project key is not secret, but it controls which Jira project receives write operations. Misconfiguration can direct automation to the wrong project.
Низкий
Environment variable object
const JIRA_BASE_URL = process.env.JIRA_BASE_URL;
The code reads the Jira base URL from the environment and later sends authenticated requests to that destination. This is configuration, but it affects credential exposure boundaries.
Низкий
Environment variable object
const PROJECT_KEY = process.env.JIRA_PROJECT_KEY || 'SCRUM';
The project key is not secret, but it controls which Jira project receives write operations. Misconfiguration can direct automation to the wrong project.
Низкий
Python environment access
JIRA_BASE_URL = os.environ.get('JIRA_BASE_URL')
The code reads the Jira base URL from the environment and later sends authenticated requests to that destination. This is configuration, but it affects credential exposure boundaries.
Низкий
Python environment access
PROJECT_KEY = os.environ.get('JIRA_PROJECT_KEY', 'SCRUM')
The project key is not secret, but it controls which Jira project receives write operations. Misconfiguration can direct automation to the wrong project.
Низкий
Environment variable access (dot notation)
const JIRA_BASE_URL = process.env.JIRA_BASE_URL;
The code reads the Jira base URL from the environment and later sends authenticated requests to that destination. This is configuration, but it affects credential exposure boundaries.
Низкий
Environment variable access (dot notation)
const PROJECT_KEY = process.env.JIRA_PROJECT_KEY || 'SCRUM';
The project key is not secret, but it controls which Jira project receives write operations. Misconfiguration can direct automation to the wrong project.
Низкий
Environment variable object
const JIRA_BASE_URL = process.env.JIRA_BASE_URL;
The code reads the Jira base URL from the environment and later sends authenticated requests to that destination. This is configuration, but it affects credential exposure boundaries.
Низкий
Environment variable object
const PROJECT_KEY = process.env.JIRA_PROJECT_KEY || 'SCRUM';
The project key is not secret, but it controls which Jira project receives write operations. Misconfiguration can direct automation to the wrong project.
Низкий
Python environment access
JIRA_BASE_URL = os.environ.get('JIRA_BASE_URL')
The code reads the Jira base URL from the environment and later sends authenticated requests to that destination. This is configuration, but it affects credential exposure boundaries.
Низкий
Python environment access
PROJECT_KEY = os.environ.get('JIRA_PROJECT_KEY', 'SCRUM')
The project key is not secret, but it controls which Jira project receives write operations. Misconfiguration can direct automation to the wrong project.
Низкий
Environment variable access (dot notation)
const JIRA_BASE_URL = process.env.JIRA_BASE_URL;
The code reads the Jira base URL from the environment and later sends authenticated requests to that destination. This is configuration, but it affects credential exposure boundaries.
Низкий
Environment variable access (dot notation)
const PROJECT_KEY = process.env.JIRA_PROJECT_KEY || 'SCRUM';
The project key is not secret, but it controls which Jira project receives write operations. Misconfiguration can direct automation to the wrong project.
Низкий
Environment variable object
const JIRA_BASE_URL = process.env.JIRA_BASE_URL;
The code reads the Jira base URL from the environment and later sends authenticated requests to that destination. This is configuration, but it affects credential exposure boundaries.
Низкий
Environment variable object
const PROJECT_KEY = process.env.JIRA_PROJECT_KEY || 'SCRUM';
The project key is not secret, but it controls which Jira project receives write operations. Misconfiguration can direct automation to the wrong project.
Низкий
Python environment access
JIRA_BASE_URL = os.environ.get('JIRA_BASE_URL')
The code reads the Jira base URL from the environment and later sends authenticated requests to that destination. This is configuration, but it affects credential exposure boundaries.
Низкий
Python environment access
PROJECT_KEY = os.environ.get('JIRA_PROJECT_KEY', 'SCRUM')
The project key is not secret, but it controls which Jira project receives write operations. Misconfiguration can direct automation to the wrong project.
Низкий
Fetch API call
const projectInfo = await fetch(`${JIRA_URL}/rest/api/3/project/${PROJECT_KEY}`, { headers });
The skill documents authenticated Jira REST calls as part of its intended workflow. This is legitimate functionality but still a real external network side effect.
Низкий
Fetch API call
const epicResponse = await fetch(`${JIRA_URL}/rest/api/3/issue`, {
The skill documents authenticated Jira REST calls as part of its intended workflow. This is legitimate functionality but still a real external network side effect.
Низкий
Fetch API call
const storyResponse = await fetch(`${JIRA_URL}/rest/api/3/issue`, {
The skill documents authenticated Jira REST calls as part of its intended workflow. This is legitimate functionality but still a real external network side effect.
Низкий
Fetch API call
const storyResponse = await fetch(`${JIRA_URL}/rest/api/3/issue`, {
The skill documents authenticated Jira REST calls as part of its intended workflow. This is legitimate functionality but still a real external network side effect.
Низкий
Fetch API call
const subtaskResponse = await fetch(`${JIRA_URL}/rest/api/3/issue`, {
The skill documents authenticated Jira REST calls as part of its intended workflow. This is legitimate functionality but still a real external network side effect.
Низкий
Fetch API call
const response = await fetch(`${JIRA_URL}/rest/api/3/field`, { headers });
The skill documents authenticated Jira REST calls as part of its intended workflow. This is legitimate functionality but still a real external network side effect.
Низкий
Fetch API call
const searchResponse = await fetch(
The skill documents authenticated Jira REST calls as part of its intended workflow. This is legitimate functionality but still a real external network side effect.
Низкий
Fetch API call
const response = await fetch(url, { ...options, headers });
The skill documents authenticated Jira REST calls as part of its intended workflow. This is legitimate functionality but still a real external network side effect.
Факторы риска
⚙️ Внешние команды (207)
jira-workflow/SKILL.md:11 jira-workflow/SKILL.md:12 jira-workflow/SKILL.md:13 jira-workflow/SKILL.md:14 jira-workflow/SKILL.md:15 jira-workflow/SKILL.md:17 jira-workflow/SKILL.md:31-37 jira-workflow/SKILL.md:37-41 jira-workflow/SKILL.md:41-42 jira-workflow/SKILL.md:42-50 jira-workflow/SKILL.md:50-64 jira-workflow/SKILL.md:64-74 jira-workflow/SKILL.md:74-77 jira-workflow/SKILL.md:77-79 jira-workflow/SKILL.md:79-101 jira-workflow/SKILL.md:101-109 jira-workflow/SKILL.md:109-137 jira-workflow/SKILL.md:137-145 jira-workflow/SKILL.md:145-151 jira-workflow/SKILL.md:151-153 jira-workflow/SKILL.md:153-174 jira-workflow/SKILL.md:174-182 jira-workflow/SKILL.md:182-186 jira-workflow/SKILL.md:186-209 jira-workflow/SKILL.md:209-217 jira-workflow/SKILL.md:217-226 jira-workflow/SKILL.md:226-230 jira-workflow/SKILL.md:230-256 jira-workflow/SKILL.md:256-261 jira-workflow/SKILL.md:261-262 jira-workflow/SKILL.md:262-263 jira-workflow/SKILL.md:263-278 jira-workflow/SKILL.md:278-300 jira-workflow/SKILL.md:300-308 jira-workflow/SKILL.md:308-311 jira-workflow/SKILL.md:311-316 jira-workflow/SKILL.md:316-322 jira-workflow/SKILL.md:322-326 jira-workflow/SKILL.md:326-338 jira-workflow/SKILL.md:338-339 jira-workflow/SKILL.md:339-340 jira-workflow/SKILL.md:340-345 jira-workflow/SKILL.md:345-355 jira-workflow/SKILL.md:355-358 jira-workflow/SKILL.md:358-361 jira-workflow/SKILL.md:361-365 jira-workflow/SKILL.md:365-369 jira-workflow/SKILL.md:369-375 jira-workflow/SKILL.md:375-381 jira-workflow/SKILL.md:381-387 jira-workflow/SKILL.md:387-389 jira-workflow/SKILL.md:389-397 jira-workflow/SKILL.md:397-413 jira-workflow/SKILL.md:413-422 jira-workflow/SKILL.md:422-425 jira-workflow/SKILL.md:425-428 jira-workflow/SKILL.md:428-432 jira-workflow/SKILL.md:432-436 jira-workflow/SKILL.md:436-475 jira-workflow/SKILL.md:475-485 jira-workflow/SKILL.md:485-493 jira-workflow/SKILL.md:493-508 jira-workflow/SKILL.md:508-528 jira-workflow/SKILL.md:528-538 jira-workflow/SKILL.md:538-551 jira-workflow/SKILL.md:551-555 jira-workflow/SKILL.md:555-580 jira-workflow/SKILL.md:580-604 jira-workflow/SKILL.md:604-605 jira-workflow/SKILL.md:605-606 jira-workflow/SKILL.md:606-607 jira-workflow/SKILL.md:607-608 jira-workflow/SKILL.md:608-609 jira-workflow/SKILL.md:609-610 jira-workflow/SKILL.md:610-611 jira-workflow/SKILL.md:611-623 jira-workflow/SKILL.md:623-628 jira-workflow/SKILL.md:628-647 jira-workflow/SKILL.md:647-657 jira-workflow/SKILL.md:657-665 jira-workflow/SKILL.md:665-669 jira-workflow/SKILL.md:669-683 jira-workflow/SKILL.md:683-689 jira-workflow/SKILL.md:689 jira-workflow/SKILL.md:690 jira-workflow/SKILL.md:691 jira-workflow/SKILL.md:692 scripts/add-subtasks.mjs:20 scripts/add-subtasks.mjs:23 scripts/add-subtasks.mjs:34 scripts/add-subtasks.mjs:52 scripts/add-subtasks.mjs:60 scripts/add-subtasks.mjs:80 scripts/add-subtasks.mjs:88 scripts/add-subtasks.mjs:108 scripts/add-subtasks.mjs:119 scripts/add-subtasks.mjs:125 scripts/add-subtasks.mjs:128 scripts/add-subtasks.mjs:137 scripts/add-subtasks.mjs:138 scripts/add-subtasks.mjs:139 scripts/add-subtasks.mjs:140 scripts/add-subtasks.mjs:152 scripts/add-subtasks.mjs:156 scripts/add-subtasks.mjs:160 scripts/add-subtasks.mjs:161 scripts/add-subtasks.mjs:165 scripts/add-subtasks.mjs:169 scripts/add-subtasks.mjs:172 scripts/add-subtasks.mjs:181 scripts/add-subtasks.mjs:182 scripts/add-subtasks.mjs:183 scripts/add-subtasks.mjs:184 scripts/create-mvp.mjs:18 scripts/create-mvp.mjs:21 scripts/create-mvp.mjs:31 scripts/create-mvp.mjs:36 scripts/create-mvp.mjs:729 scripts/create-mvp.mjs:730 scripts/create-mvp.mjs:732 scripts/create-mvp.mjs:760 scripts/create-mvp.mjs:761 scripts/create-mvp.mjs:776 scripts/create-mvp.mjs:780 scripts/create-mvp.mjs:789 scripts/create-mvp.mjs:790 scripts/create-mvp.mjs:799 scripts/create-mvp.mjs:800 scripts/create-mvp.mjs:801 scripts/create-mvp.mjs:804 scripts/create-mvp.mjs:805 scripts/create-mvp.mjs:816 scripts/create-mvp.mjs:822 scripts/create-mvp.mjs:823 scripts/create-mvp.mjs:824 scripts/create-two-level.mjs:19 scripts/create-two-level.mjs:21 scripts/create-two-level.mjs:61 scripts/create-two-level.mjs:69 scripts/create-two-level.mjs:486 scripts/create-two-level.mjs:497 scripts/create-two-level.mjs:514 scripts/create-two-level.mjs:530 scripts/create-two-level.mjs:533 scripts/create-two-level.mjs:541 scripts/create-two-level.mjs:547 scripts/create-two-level.mjs:555 scripts/create-two-level.mjs:556 scripts/create-two-level.mjs:557 scripts/create-two-level.mjs:561 scripts/create-two-level.mjs:563 scripts/create-two-level.mjs:567 scripts/create-two-level.mjs:568 SKILL.md:24 SKILL.md:25 SKILL.md:26 SKILL.md:27 SKILL.md:30-31 SKILL.md:31-34 SKILL.md:34-38 SKILL.md:38-44 SKILL.md:44-50 SKILL.md:50-98 SKILL.md:98-102 SKILL.md:102-189 SKILL.md:189-193 SKILL.md:193-205 SKILL.md:205-211 SKILL.md:211-214 SKILL.md:214 SKILL.md:220-228 SKILL.md:228-232 SKILL.md:232-242 SKILL.md:242-250 SKILL.md:250-256 SKILL.md:256-264 SKILL.md:264-268 SKILL.md:268-271 SKILL.md:271 SKILL.md:284-291 SKILL.md:291-299 SKILL.md:299-321 SKILL.md:321-327 SKILL.md:327-329 SKILL.md:329-339 SKILL.md:339-343 SKILL.md:343-346 SKILL.md:346-348 SKILL.md:348-355 SKILL.md:355-359 SKILL.md:359-365 SKILL.md:365-370 SKILL.md:370-371 SKILL.md:371-382 SKILL.md:382-386 SKILL.md:386-389 SKILL.md:389-395 SKILL.md:395-401 SKILL.md:401-402 SKILL.md:402-409 SKILL.md:409-410 SKILL.md:410-417 SKILL.md:417-418 SKILL.md:418-419 SKILL.md:419-431 SKILL.md:431-437 SKILL.md:437-443
🌐 Доступ к сети (39)
jira-workflow/SKILL.md:174 jira-workflow/SKILL.md:209 jira-workflow/SKILL.md:310 jira-workflow/SKILL.md:344 jira-workflow/SKILL.md:412 jira-workflow/SKILL.md:474 jira-workflow/SKILL.md:34 jira-workflow/SKILL.md:698 jira-workflow/SKILL.md:699 jira-workflow/SKILL.md:700 jira-workflow/SKILL.md:701 scripts/add-subtasks.mjs:44 scripts/add-subtasks.mjs:72 scripts/add-subtasks.mjs:89 scripts/add-subtasks.py:61 scripts/add-subtasks.py:86 scripts/add-subtasks.py:100 scripts/add-subtasks.py:106 scripts/add-subtasks.py:21 scripts/create-mvp.mjs:32 scripts/create-mvp.py:62 scripts/create-mvp.py:122 scripts/create-mvp.py:18 scripts/create-two-level.mjs:61 scripts/create-two-level.py:54 scripts/create-two-level.py:110 scripts/create-two-level.py:14 SKILL.md:31 SKILL.md:220 SKILL.md:242 SKILL.md:284 SKILL.md:299 SKILL.md:329 SKILL.md:347 SKILL.md:355 SKILL.md:433 SKILL.md:447 SKILL.md:448 SKILL.md:449
🔑 Переменные окружения (47)
jira-workflow/SKILL.md:146 jira-workflow/SKILL.md:147 jira-workflow/SKILL.md:148 jira-workflow/SKILL.md:149 jira-workflow/SKILL.md:146 jira-workflow/SKILL.md:147 jira-workflow/SKILL.md:148 jira-workflow/SKILL.md:149 scripts/add-subtasks.mjs:7 scripts/add-subtasks.mjs:8 scripts/add-subtasks.mjs:9 scripts/add-subtasks.mjs:10 scripts/add-subtasks.mjs:7 scripts/add-subtasks.mjs:8 scripts/add-subtasks.mjs:9 scripts/add-subtasks.mjs:10 scripts/add-subtasks.py:33 scripts/add-subtasks.py:38 scripts/add-subtasks.py:39 scripts/add-subtasks.py:40 scripts/add-subtasks.py:41 scripts/create-mvp.mjs:5 scripts/create-mvp.mjs:6 scripts/create-mvp.mjs:7 scripts/create-mvp.mjs:8 scripts/create-mvp.mjs:5 scripts/create-mvp.mjs:6 scripts/create-mvp.mjs:7 scripts/create-mvp.mjs:8 scripts/create-mvp.py:30 scripts/create-mvp.py:35 scripts/create-mvp.py:36 scripts/create-mvp.py:37 scripts/create-mvp.py:38 scripts/create-two-level.mjs:6 scripts/create-two-level.mjs:7 scripts/create-two-level.mjs:8 scripts/create-two-level.mjs:9 scripts/create-two-level.mjs:6 scripts/create-two-level.mjs:7 scripts/create-two-level.mjs:8 scripts/create-two-level.mjs:9 scripts/create-two-level.py:26 scripts/create-two-level.py:31 scripts/create-two-level.py:32 scripts/create-two-level.py:33 scripts/create-two-level.py:34
Аудитор:: codex Посмотреть историю аудитов →
Поделиться и цитировать этот отчет
Делитесь версионным отчетом об оценке, нейтральным значком, встраиваемой карточкой и цитатами. Skillstore публикует доказательства, не решая, безопасен ли этот Skill.
Копировать ссылку на отчёт
https://skillstore.io/skills/01000001-01001110-jira-safe/audits/11?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportЗначок Markdown
[](https://skillstore.io/skills/01000001-01001110-jira-safe?utm_source=security_passport_badge)Значок HTML
<a href="https://skillstore.io/skills/01000001-01001110-jira-safe?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/01000001-01001110-jira-safe/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Встраиваемая карточка
<iframe src="https://skillstore.io/embed/skills/01000001-01001110-jira-safe.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Академические ссылки (APA · BibTeX · CFF)
Цитата APA
01000001-01001110. (2026). jira-safe security audit report (audit version 11) [Author version unspecified]. Skillstore. https://skillstore.io/skills/01000001-01001110-jira-safe/audits/11Цитата BibTeX
@techreport{01000001-01001110-01000001-01001110-jira-safe-2026,
author = {01000001-01001110},
title = {jira-safe security audit report (audit version 11)},
institution = {Skillstore},
year = {2026},
number = {11},
url = {https://skillstore.io/skills/01000001-01001110-jira-safe/audits/11},
note = {Author version unspecified}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "jira-safe security audit report (audit version 11)"
version: "unspecified"
type: report
authors:
- name: "01000001-01001110"
date-released: "2026-07-07"
url: "https://skillstore.io/skills/01000001-01001110-jira-safe/audits/11"
identifiers:
- type: other
value: "skillstore:01000001-01001110-jira-safe:audit:11"
description: "Skillstore immutable audit report identifier"
Оценка Skillstore
Почему такая оценка Достоверность доказательств: Средний 45
Архитектура
85
Сопровождаемость
87
Контент
73
Сообщество
83
Соответствие спецификации
Что вы можете построить
Создать бэклог SAFe
Преобразуйте продуктовые требования в эпики Jira, истории, критерии приемки и подзадачи.
Подготовить работу для спринта
Разбейте утвержденные возможности на истории реализации и технические подзадачи перед планированием спринта.
Синхронизировать статус работы
Используйте шаблоны переходов рабочего процесса Jira, чтобы перемещать задачи через состояния Progressing, review и Done.
Попробуйте эти промпты
Создать черновик одной истории
Создайте одну пользовательскую историю SAFe для этой возможности. Включите summary, persona, goal, benefit, acceptance criteria и subtasks.
Создать план эпика
Преобразуйте эту продуктовую цель в один эпик Jira с бизнес-результатом, метриками успеха, историями и подзадачами реализации.
Подготовить шаги создания в Jira
Подготовьте план создания задач Jira для проекта, управляемого командой. Покажите parent links и запросите подтверждение перед любой операцией записи.
Проверить автоматизацию рабочего процесса
Проверьте этот план автоматизации рабочего процесса Jira на безопасность, совместимость с полями проекта, ограничения скорости и шаги отката перед выполнением.
Лучшие практики
- Подтверждайте тип проекта и доступные переходы перед созданием или перемещением задач Jira.
- Используйте Jira API tokens с минимально необходимыми правами и сначала тестируйте скрипты в sandbox-проекте.
- Запрашивайте одобрение пользователя перед любой операцией записи, удаления или массовой операцией в Jira.
Избегать
- Запуск демонстрационных скриптов в production Jira без проверки сгенерированного бэклога.
- Предположение, что custom field IDs идентичны во всех проектах Jira.
- Использование помощников массового удаления без dry run, allowlist и типизированного подтверждения.
Часто задаваемые вопросы
Работает ли этот навык с проектами Jira, управляемыми командой?
Да. Примеры сосредоточены на проектах, управляемых командой, и используют поле parent для иерархии эпиков и историй.
Требуются ли учетные данные Jira?
Да. Скриптам и примерам API требуются Jira email, API token, base URL и значения project key.
Может ли он создавать реальные задачи Jira?
Да. Включенные скрипты могут создавать эпики, истории и подзадачи при выполнении с действительными учетными данными.
Может ли он обновлять состояния рабочего процесса?
Да. Руководство по рабочим процессам показывает, как запрашивать переходы и перемещать задачи между настроенными состояниями Jira.
Безопасно ли это для production-проектов Jira?
С осторожностью. Проверяйте сгенерированную работу, используйте tokens с минимально необходимыми правами и предпочитайте dry-run или тестирование в sandbox перед записями в production.
Обрабатывает ли он пользовательские поля Jira автоматически?
Частично. Он объясняет распространенные поля и включает рекомендации по поиску, но каждый экземпляр Jira может требовать проверки.
Сведения для разработчиков
Автор
01000001-01001110Лицензия
MIT
Ревизия Skillstore
r1
Примечание о версии
Автор не указал версию.
Ссылка
7ed2830f0283f3a8900137d8dc893e54072206f3
Актуальность поддержки
18.07.2026
Использование
83 загрузок · 405 просмотров
Структура файлов