返回提示词目录第 1157 页

软件包平台搜索展示优化

检查软件包在注册表与市场中的搜索展示,提供元数据修改片段、入驻条件核查与下载量跟踪方法。

完整提示词

<context>
Many developers find tools inside the registry or package manager they already use, and each one ranks and renders listings from manifest metadata: npm search uses the name, description and keywords; PyPI shows the summary and the long description from the README, with classifiers and project URLs in the sidebar; crates.io uses description, keywords (up to five) and categories from a fixed list; editor marketplaces use the display name, description, categories, keywords (capped) and icon. Package managers that curate have entry bars: Homebrew's acceptance policy sets notability thresholds (higher for a submission by the project's own author) and a minimum repository age, casks must pass macOS security checks, Flathub rejects command-line tools and asks for meaningful history, and classic-confinement snaps need manual review. A listing whose README images break, links point nowhere or description says nothing concrete loses the people who already found it. Registry rules change; current documentation wins over this summary.
</context>

<task>
<listings>
{{listings}}
</listings>
{{#project}}
Project:
{{project}}
{{/project}}
Registries: {{registries}}.

If no manifest or listing is given, ask for it and stop.

1. **Search terms.** List the six to ten words people would type in a registry search for this, from the category noun and the job, and say which ones the current metadata misses.
2. **Audit each listing** in {{registries}}: name and display name, description or summary (concrete, starts with what it is, within the registry's length norms), keywords, topics or categories (only from the registry's allowed set where it has one), README rendering on the registry (relative image paths and links that break off GitHub, badges that fail, missing install command for that registry), license field, repository, homepage, documentation and issue URLs, version and release notes link, icon or logo, deprecation of old package names.
3. **Metadata changes.** Write the corrected fields as diffs or snippets for each manifest. Use absolute URLs for images in READMEs that registries render. Do not stuff keywords; every keyword must describe the project.
4. **Eligibility for new registries.** For registries the project is not in yet, list the requirements from their documentation (age, popularity thresholds, signing, sandboxing, review time) and whether the project meets them, marking anything you could not check as UNVERIFIED.
5. **Measuring.** Name the public download or install statistics for each registry (download APIs, install analytics, release asset counts) and how to record them weekly.
</task>

<constraints>
- Do not invent registry rules, limits or category names; mark them UNVERIFIED if unsure and point to the documentation to check.
- No keyword stuffing, competitor names as keywords, or misleading names that imitate another package.
- Keep the license field exactly as the project's real license.
{{> output/uncertainty}}
</constraints>

<output_format>
## Search terms
## Listing audit
| Registry | Field | Current | Problem | Fix |
## Metadata changes
Snippets or diffs per manifest.
## Eligibility for new registries
| Registry | Requirement | Met? | Source |
## Measuring
</output_format>

可替换内容

  • {{listings}}
  • {{#project}}
  • {{project}}
  • {{/project}}
  • {{registries}}
  • {{> output/uncertainty}}

分类与标签

商业营销、软件包推广、平台搜索优化、元数据优化、下载量跟踪

前往 AI 图片创作