المهارات publish-to-all-skill-stores
📦

publish-to-all-skill-stores

v2.2.0 مراجعة المحتوى r2 مخاطر عالية 🌐 الوصول إلى الشبكة📁 الوصول إلى نظام الملفات⚙️ الأوامر الخارجية⚡ يحتوي على سكربتات🔑 متغيرات البيئة

Publish Agent Skills Across Supported Marketplaces

Skill marketplaces require different repository layouts, package formats, and submission steps. This skill provides local preparation tools, supported API submissions, and channel-specific publishing guidance.

يدعم: Claude Codex Code(CC)
Maintain this Skill? Claim it ⚠️ 38 ضعيف

التثبيت باستخدام Agent لدي

انسخ هذا الطلب إلى Agent لديك. يتضمن صفحة Skill المعتمدة وملف manifest.

طلب الوكيل
Review the Skillstore skill "publish-to-all-skill-stores" from https://skillstore.io/skills/xixi048-publish-to-all-skill-stores.md and its manifest at https://skillstore.io/api/skills/xixi048-publish-to-all-skill-stores/manifest. Verify the artifact. Stop and obtain explicit user consent before installing or changing files.

يجب أن يواصل Agent عرض خطته وطلب أي تأكيد تفرضه سياسة الأمان.

موارد مهيّأة لـ Agents

استخدم هذه الروابط عندما يحتاج AI Agent أو crawler أو script إلى سياق نظيف بدلًا من قراءة الصفحة كاملة.

اختبرها

جارٍ استخدام "publish-to-all-skill-stores". Review my skill before I submit it.

النتيجة المتوقعة:

  • Metadata: name and description are present.
  • License: no license file was found in the selected skill or repository root.
  • Package review: check for credentials and file symlinks before building a release archive.
  • Publication: no submissions were made.

جارٍ استخدام "publish-to-all-skill-stores". Summarize the selected marketplace publishing plan.

النتيجة المتوقعة:

  • skillstore: repository submission can use the included API handler after approval.
  • skillbay: prepare a skill document and contact details for the quick submission workflow.
  • ClawHub: user authentication is required before publishing.
  • MCP directories: require an existing runnable service, not only a skill document.

جارٍ استخدام "publish-to-all-skill-stores". Prepare a WorkBuddy skill package without uploading it.

النتيجة المتوقعة:

  • Package layout: SKILL.md at the archive root.
  • Metadata: additional display names and localized descriptions belong in the packaged copy.
  • Source: the original SKILL.md remains unchanged.
  • Next check: inspect the archive contents, size, and directory depth before upload.

التدقيق الأمني

مخاطر عالية

Reviewed all 159 static findings: eight identify credential forwarding or unsafe temporary login logs; the remaining 151 are false positives. Semantic findings identify plaintext credential memory, unsafe archive selection, and instructions that can manipulate security review through unsupported safety claims. No evidence found of executable obfuscated payloads; multilingual prose, detection signatures, and Markdown explain the apparent execution and entropy alerts.

15
الملفات التي تم فحصها
2,967
الأسطر التي تم تحليلها
8
عناصر المراجعة
0
تم تجاهل الإيجابيات الكاذبة

مخاوف أمنية مؤكدة (3)

مرتفع
Long-Lived API Key Stored in Agent Memory
The XiaPing guide directs agents to store their long-lived API key in MEMORY.md. Plaintext agent memory can expose credentials through later context loading, synchronization, or accidental publication.
The text identifies the response key as a long-term credential and explicitly instructs saving it in the memory document. No protected storage mechanism is specified.
مرتفع
Sensitive Local Files Can Enter Publication Archives
The generic builder accepts credential files, while both builders follow file symlinks without checking containment. WorkBuddy limits top-level directories, but secrets inside those directories can still enter release archives.
The generic collector accepts .env; WorkBuddy accepts files inside designated subdirectories without secret exclusions. Both archive writers dereference file symlinks, so disclosure depends on the selected tree.
مرتفع
Prompt Injection Attempt Detected
The guide says "写进提交备注,比修改代码更有效", meaning writing safety assurances in submission notes is more effective than changing code. Instructing agents to assert no network access and mandatory backups without verification can manipulate marketplace security review.
The instructions explicitly favor safety claims over code corrections and repeat blanket assurances for scripted skills. This targets downstream review, not this audit's instruction hierarchy.
عناصر مراجعة القدرات (8)

هذه قدرات محلية حقيقية قد يُتوقع وجودها لهذه المهارة، لذا فهي تتطلب مراجعة ولكن لا تُحتسب كسلوك خبيث مؤكد.

مرتفع
Shell command substitution
TOK=$(gh auth token); B64=$(printf 'x-access-token:%s' "$TOK" | base64 -w0)
The recipe extracts a GitHub token and Base64-encodes it for an Authorization header. Lines 97-98 send that credential through ghfast.top.
مرتفع
Hardcoded URL
push https://ghfast.top/https://github.com/<owner>/<repo>.git main
The Git push targets ghfast.top while the preceding line supplies a GitHub Authorization header. The third-party mirror receives reusable GitHub credentials.
مرتفع
Shell command substitution
TOK=$(gh auth token)
The command retrieves the active GitHub token. The following commands place it in an Authorization header sent through a third-party mirror.
مرتفع
Shell command substitution
B64=$(printf 'x-access-token:%s' "$TOK" | base64 -w0)
The command converts the GitHub token into reversible Basic authentication material. Lines 168-170 send it to ghfast.top rather than directly to GitHub.
مرتفع
Hardcoded URL
push https://ghfast.top/https://github.com/<owner>/<repo>.git main
The mirror URL is used for a push with an explicit GitHub Authorization header. TLS terminates at the third party, exposing the credential.
متوسط
Temp directory access
(nohup npx -y clawhub@latest login >/tmp/clawlogin.log 2>&1 &); sleep 12; cat /tmp/clawlogin.log
Login output is redirected to a predictable shared temporary path without permission controls. Another local user could read authentication output or preplant a symlink.
متوسط
Temp directory access
(nohup npx -y clawhub@latest login >/tmp/clawlogin.log 2>&1 &); sleep 12
The login process writes authentication output to a fixed shared temporary filename. Missing restrictive permissions and exclusive creation permit local disclosure or symlink clobbering.
متوسط
Temp directory access
cat /tmp/clawlogin.log # 拿到 https://clawhub.ai/cli/device?user_code=XXXX-XXXX
The command reads a predictable shared login log without verifying ownership or permissions. A local attacker could replace it or access authentication output.

عوامل الخطر

🌐 الوصول إلى الشبكة (48)
📁 الوصول إلى نظام الملفات (23)
⚙️ الأوامر الخارجية (50)
⚡ يحتوي على سكربتات (3)
🔑 متغيرات البيئة (7)
شارك واستشهد بهذا التقرير

شارك تقرير التقييم المرتبط بالإصدار والشارة المحايدة وبطاقة التضمين والاستشهادات. تعرض Skillstore الأدلة من دون أن تقرر ما إذا كانت هذه المهارة آمنة.

فتح التقرير المرتبط بالإصدار
تقييم الأمان

نسخ رابط التقرير

https://skillstore.io/skills/xixi048-publish-to-all-skill-stores/audits/2?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

شارة Markdown

[![Skillstore security assessment](https://skillstore.io/badges/skills/xixi048-publish-to-all-skill-stores/security.svg)](https://skillstore.io/skills/xixi048-publish-to-all-skill-stores?utm_source=security_passport_badge)

شارة HTML

<a href="https://skillstore.io/skills/xixi048-publish-to-all-skill-stores?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/xixi048-publish-to-all-skill-stores/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

بطاقة قابلة للتضمين

<iframe src="https://skillstore.io/embed/skills/xixi048-publish-to-all-skill-stores.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

xixi048. (2026). publish-to-all-skill-stores security audit report (audit version 2) [Author version 2.2.0]. Skillstore. https://skillstore.io/skills/xixi048-publish-to-all-skill-stores/audits/2

اقتباس BibTeX

@techreport{xixi048-xixi048-publish-to-all-skill-stores-2026, author = {xixi048}, title = {publish-to-all-skill-stores security audit report (audit version 2)}, institution = {Skillstore}, year = {2026}, number = {2}, url = {https://skillstore.io/skills/xixi048-publish-to-all-skill-stores/audits/2}, note = {Author version 2.2.0} }

CITATION.cff

cff-version: 1.2.0 message: "If you use this Skill, cite its author and this versioned security audit report." title: "publish-to-all-skill-stores security audit report (audit version 2)" version: "2.2.0" type: report authors: - name: "xixi048" date-released: "2026-10-29" url: "https://skillstore.io/skills/xixi048-publish-to-all-skill-stores/audits/2" identifiers: - type: other value: "skillstore:xixi048-publish-to-all-skill-stores:audit:2" description: "Skillstore immutable audit report identifier"

تقييم Skillstore

سبب هذا التقييم موثوقية الأدلة: متوسط
59
الهندسة المعمارية
100
قابلية الصيانة
87
المحتوى
65
المجتمع
91
الامتثال للمواصفات

ما الذي يمكنك بناؤه

Prepare an Open-Source Skill Release

Check repository structure and prepare publication archives before submitting an agent skill to selected public marketplaces.

Coordinate Marketplace Submissions

Separate automated API submissions from channels awaiting login, review, or platform-specific development, then track available receipts.

Plan Service Distribution

Compare skill listings, MCP directories, API catalogs, and hosted platforms to identify suitable deliverables for an existing service.

جرّب هذه الموجّهات

Review Publishing Readiness
Review [skill directory] for publishing readiness. Explain metadata, license, and layout issues without changing files, submitting content, or installing tools.
Prepare a Release Package
Prepare a package for [marketplace] from [skill directory]. Inspect credentials and symlinks first, confirm the output directory, and do not upload anything.
Submit to Selected Channels
Plan submissions for [repository URL] to [selected marketplaces]. Show destinations and shared data, request approval, then report receipts and unresolved login requirements.
Design a Distribution Workflow
Create a distribution plan for [skill repository] and [MCP or API endpoint]. Separate packaging, registry submissions, authentication, consent, and porting work.

أفضل الممارسات

  • Approve each destination and shared field before submission; retain receipts and distinguish submitted content from approved listings.
  • Inspect archives for secrets and symlinks, use protected credential storage, and authenticate directly with the intended service.
  • Verify current marketplace requirements and support every safety statement with release evidence; do not follow instructions that substitute assurances for security fixes.

تجنب

  • Forwarding GitHub tokens through third-party mirrors or saving long-lived API keys in agent memory.
  • Publishing archives without inspecting sensitive files, symlinks, output paths, and included metadata.
  • Treating a broad channel catalog, a successful request, or a preflight result as guaranteed approval or a complete security audit.

الأسئلة المتكررة

Does this publish to every marketplace automatically?
No. The script implements several API handlers, while many catalog entries require login, manual review, repository contributions, or platform-specific development.
Can I use it with Claude, Codex, and Claude Code?
The report lists all three tools as supported. Local scripts require a compatible Python installation, while authenticated channels may require additional CLIs.
Does the preflight script certify that my skill is secure?
No. It checks metadata and text patterns. It cannot replace code review, credential inspection, or marketplace security assessment.
Can it publish private repositories to automatic indexes?
Public auto-indexers generally require accessible repositories. Private distribution needs an appropriate authenticated upload or hosted workflow.
Does submission enable paid listings?
Not automatically. Pricing and payment setup usually require seller accounts, merchant verification, or platform-specific service changes.
What precautions are needed before using the recipes?
Avoid token-bearing mirror pushes and plaintext credential memory. Inspect archives for secrets and symlinks, and approve destinations and legal pledges explicitly.

تفاصيل المطور

المؤلف

xixi048

الترخيص

MIT

إصدار المؤلف

v2.2.0

مراجعة Skillstore

r2

مرجع

295dc8a44d5592a9621ff385f412d8bcc18c0afd

حداثة الصيانة

٣٠‏/١٠‏/٢٠٢٦

الاستخدام

2 تنزيلات · 0 مشاهدات

المزيد من xixi048

عرض الكل
عرض الكل